This article highlights a few noteworthy changes in the latest release of Fedora Workstation that we think you will love. Upgrade today from the official website, or upgrade your existing install using GNOME Software or through the terminal with dnf system-upgrade.
GNOME 50
Fedora Linux 44 Workstation ships with the latest GNOME release, GNOME 50. This comes with a long list of refinements to your desktop, including everything from accessibility, to color management and remote desktop.
As part of the Digital Wellbeing initiative, new native Parental Controls let you set screen time limits and bedtimes directly from Settings.
Many of the applications that are installed by default on the Fedora Workstation have also seen improvements, from the Document Viewer to the File Manager and the Calendar.
To learn more about these and other changes, you can read the GNOME 50 release notes.
Wrap-up
Be sure to check out the Fedora Linux 44 Change Set wiki for even more details about all the features and changes that went into Fedora Linux 44. Use the Fedora Discussion forum or Fedora’s Matrix chat server if you want to converse with the Fedora community about this new release!
Mark Lesti
its still buggy . and there are still blockers. hmmmm
could not even update the system. after fresh install
its just does not work ! pls check !
Richard England
You might ask specific questions about your “blockers” and update issues on ask.fedoraproject.org.
Amar
Fedora 43 → 44 upgrade conflict:
vs
What’s happening
The upgrade is trying to install
alongside your existing
package. Both packages ship the same D‑Bus service files for the
interface (
and
), which is why DNF/RPM aborts the transaction — RPM refuses to let two packages own the same files.
This is a known design conflict. tuned-ppd is intended as a direct replacement of power-profiles-daemon[1], and it works by registering and listening on the same DBUS events the power-profiles-daemon does, so it can serve the same DBUS services (power profiles) which are already in use and offered by KDE and GNOME control centers or other UI[2]. TLP ships those same interface files (because TLP “stands in” for PPD on systems that use it), so they collide.
Note also that the service unit
declares a conflict with
, causing
to be effectively disabled[3] — the same applies to
. So even if you forced both to coexist, only one would actually run.
You need to pick one of these tools. Two clean options:
Option A — Keep TLP, skip
(recommended if TLP is working for you)
Tell the system upgrade to exclude
:
sudo dnf system-upgrade reboot
If you launched the upgrade from GNOME Software / Discover, drop to a terminal and use the
command above instead — the GUI doesn’t give you an exclude option.
If
complains that
is being pulled in by another package (e.g., a desktop meta-package), you can also try:
After the upgrade, verify TLP is active and PPD/tuned-ppd are not:
systemctl status tuned-ppd power-profiles-daemon 2>/dev/null
sudo tlp-stat -s
Option B — Switch to
(the new Fedora default)
If you’d rather adopt the Fedora default power management stack, remove TLP first, then run the upgrade:
sudo systemctl disable tlp
sudo dnf remove tlp tlp-rdw
sudo dnf system-upgrade download --releasever=44
sudo dnf system-upgrade reboot
After reboot,
and
will provide the Power Profile slider in GNOME/KDE.
Which should you choose?
TLP generally tunes more knobs out of the box. Anecdotally, when using tlp, powertop usually shows that every tunable is good, while with ppd or tuned-ppd the result is different — tlp may be more efficient in some areas[4].
tuned-ppd integrates natively with the GNOME/KDE Power Profile selector and is what Fedora ships by default going forward, and tuned allows configuring various aspects of the sys/hw and not just the cpu states[5].
If you’ve intentionally installed TLP and tuned it, go with Option A. If you don’t remember why TLP is installed and you just want the stock Fedora experience, go with Option B.
Why
/
won’t help here
This is a file conflict at the RPM level (two packages claiming the same path), not a dependency-resolution problem. So flags like
,
, or
alone won’t bypass it unless they actually result in one of the two packages being removed from the transaction. You must explicitly exclude or remove one side.
Mario
Danke für die Einführung, finde ich echt gut verstehe aber leider nur Bahnhof bin kein Nerd. Benutze Fedora seid Version 43 funktioniert echt gut aber wie gesagt das was ihr da schreibt ist für mich echt zu hoch, bitte denkt vielleicht etwas an normale User. Ansonnsten versteht mich nicht falsch, aber Linux wird sich nie durchsetzen wenn es nur für Insider gemacht wird.
Jonas Zürcher
Lieber Mario
Die Community ist offen für jedes Skill-Level. Der Unterschied zu den WIndows 11 ist, dass hier der Code offen vorliegt und entsprechend darüber diskutiert wird. Der Post von Amar ist hier nicht ganz richtig platziert und wäre im Forum wohl besser angesiedelt. Es ist aber spannend ihn zu lesen.
Wenn ein Bug, wie ihn Amar beschreibt, in Windows drin wäre, würden wir nur merken, dass Windows 11 nicht mehr so schnell läuft.
Ob das dazu führt, dass weniger Leute auf eine Linux distro umsteigen? Ich weiss nicht. Vielleicht schon, aber Microsoft liefert in letzter Zeit ganz schön viel Slop. Du bist ja auch hier angekommen seit einem halben Jahr…
Stefan
Keine Sorge, wenn dich das interessiert was da steht kannst du im Forum nachfragen und auch eine KI nutzen ist keine Schande:
Das ist eine sehr saubere und detaillierte Antwort auf ein klassisches Fedora-Upgrade-Problem! Hier die Zusammenfassung:
Das Problem: Beim Upgrade von Fedora 43 → 44 gibt es einen Konflikt zwischen tuned-ppd (neu, Fedora-Standard ab F44) und tlp (bereits installiert). Beide Pakete beanspruchen dieselben D-Bus Service-Dateien für das PowerProfiles-Interface — RPM verweigert das kategorisch.
Die Kernaussage: Man muss sich für eines entscheiden, weil sie sich gegenseitig aktiv deaktivieren würden, selbst wenn man den Konflikt irgendwie umgehen könnte.
Die zwei Optionen:
Option A – TLP behalten: –exclude=tuned-ppd beim Upgrade-Befehl mitgeben
Option B – Auf tuned-ppd wechseln: TLP vorher sauber entfernen, dann upgraden
Empfehlung des Autors: Wer TLP bewusst installiert und konfiguriert hat → Option A. Wer nicht mehr weiß warum TLP da ist → Option B (Stock-Fedora-Erfahrung).
Bonus-Info: –skip-broken oder –nobest helfen hier nicht, weil es kein Dependency-Problem ist, sondern ein echter RPM-Dateikonflikt.
Was ist TLP und
TLP ist ein ausgereiftes Power-Management-Tool für Linux, das schon sehr lange existiert. Es ist quasi ein “Set it and forget it”-Optimierer — beim Start greift es tief ins System ein und stellt dutzende Parameter ein:
CPU-Governor, Frequenzlimits
USB Autosuspend
SATA Link Power Management
PCIe ASPM
WiFi-Powersave
Festplatten-Spindown
…und noch viel mehr
Es ist besonders beliebt auf Laptops, weil es ohne großes Zutun des Users einfach Akku spart. Kein GUI, pure Konfigdatei.
tuned-ppd ist neueren Ursprungs und ein anderer Ansatz. Es ist ein Aufsatz auf tuned (einem Red Hat/Fedora-Projekt zur Systemoptimierung) und implementiert das Power Profiles Daemon-Interface — das ist der Mechanismus hinter dem bekannten Energiesparmodus-Schieberegler in GNOME und KDE:
🔋 Power Saver
⚖️ Balanced
⚡ Performance
Der Vorteil: nahtlose Desktop-Integration, der User schaltet einfach per GUI um.
Ich weiß manche Leser wir das jetzt Sauer machen aber die ChatBots können solche Geschichten gut erklären und sind ein guter Anfang in die “tiefere” Linux Welt.
Mario
Danke für die Erklährung, heißt das jetzt das es passieren kann, wenn ich upgrade das dann nichts mehr funktioniert und ich ein neues System installieren muss. Habe leider das Problem das mein Internet nicht unlimitiert ist und daher moechte ich nicht wieder alles neu installieren müssen. Was ehrlich gesagt ein Alptraum ist und ausserdem hab ich einfach nicht die Zeit um mich einen oder zwei Tage hin zu setzten und alles neu einzurichten.
Stefan
Thank you @Amar for this great explanation including the issue, background, the options forward and the impact!
Tarakshraj
Thank you so much for your help. I have had issues with Fedora not liking my laptop’s garbage old Nvidia GPU and I had to drop Fedora for a while, and so I was kinda worried that this might be a similar issue. Really glad it’s not a device specific issue and now the update is working. Appreciate the help 🙂
James
Tried to update to Fedora 44 but by the time I put my long password in a window said timeout has been reached. Same thing happened when I tried to update from 42 to 43. we are supposed to use long passwords, right? i e entually got 43 now frustration again.
Richard England
More people will be available to help you address your issue if you ask for assistance at ask.fedoraproject.org
hacker10
You don’t need a long password for a Linux account password, the main reason for the password is to authenticate and stop an application from making changes to the system without making sure you authorised it.
jackson
i have been trying to upgrade to 44 fedora from 43 todat around 6 pm til now 8 pm, it keeps saying upgrade failed. my internet is okay and yes its just eating my internet data now 4gb gone but the upgrade wont finish, ending at 55% sometimes 45%. Whats the problem here
Gregory Bartholomew
You should probably ask on ask.fedoraproject.org. Personally, I prefer using the CLI (dnf update ‐‐releasever=44) that gives a little more feedback, but doing that “right” is a bit more involved. The CLI update should be done while in the CLI-only multi-user target, not the normal graphical target. If the CLI update fails, you should get a notification about what package failed and why (not available from the mirror, conflicts with another installed package, etc.).
Andrew
Fedora Workstation, as always, is top-notch, the best and most polished OS. Yesterday I upgraded from version 43 to Fedora Workstation 44: everything works perfectly. I’ll reinstall it from scratch in a few days.
Maybe this information will help someone: I have an NVIDIA 1030, and after the update, the driver crashed. I need to completely uninstall everything related to the NVIDIA driver and reinstall version 580 of the driver using RPM Fusion. The correct instructions are available online. After these steps, everything worked perfectly, no errors.
Thank you so much for creating a perfect OS like Fedora Workstation. I wish you success in the future development of the company and the project!
frantisek
Thanks guys for again very good job!
Aleks
why gnome update requires entire new os version?
Gregory Bartholomew
mainly because the developers do not want to test and maintain it for older operating system versions. doing that would be a lot more work for the developers.
Mark Lesti
active inhibitors blocking reboot when i update/install packages
also noticed that i cant install updates from software centre too!
what is this exactly? i used 43 inba but worked perfectly. its a fresh install btw. pls help thx 🙂
Richard England
You should probably ask on ask.fedoraproject.org. More people watch that than the comments on Magazine articles.
Stephen Drinkwater
Failed – sat at Black screen for 10 mins. On restart dnf won’t load the plugins:
Cannot load dnf5 plugin: /usr/lib64/dnf5/plugins/builddep_cmd_plugin.so
Cannot load shared library “/usr/lib64/dnf5/plugins/builddep_cmd_plugin.so”: /usr/lib64/dnf5/plugins/builddep_cmd_plugin.so: undefined symbol: _ZN4dnf511match_specsERNS_7ContextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEbbbbPKc
so can’t roll back. Any thought as to how to install the relevant *.so files to match the build?
Gregory Bartholomew
It sounds like you killed the update when it was half way through. Sometimes you can recover from that sort of thing by booting a Live image, using it to mount the root filesystem of your failed upgrade in a chroot (with the required bind mounts), and then running dnf distro-sync. This comment area is not a good place to try to guide someone through that though. Use ask.fedoraproject.org if you need assistance with that process.
Georg
Cannot upgrade from f43 (fully updated). As root user I did a
dnf system-upgrade download –releasever=44
The error message is:
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f44&arch=x86_64”) for repository “updates-modular”: Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f44&arch=x86_64 (IP: 2001:4178:2:1269::fed2)
Gregory Bartholomew
I’m not sure. A 404 when trying to connect to mirrors.fedoraproject.org sounds like something that should be reported to the fedora infrastructure team. You might file a report here: https://forge.fedoraproject.org/infra/tickets/issues or just ask if there are known issues with the mirror manager in their Matrix chat room here: https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org
Stephen Drinkwater
Thanks. After a bit more digging I replaced the plug-ins by extracting using rpm2cpio and copying into the target plug-ins directory. This seems to have done the trick and dnf is operating correctly. Clean up is OK. All other checks seem to imply that Fed 44 has installed correctly and appears to be functioning OK.
Dian Ribut
I’ll wait 1 or 2 months before upgrading to 44. Last time I upgrade right away after release was from fedora 40 to 41, and it cause a lot of problem on my side. Just play it safe
David Millar
I’am Multi-Booting on my ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401QM_GA401QM. I run 5 Linux OS and Windows 11. The Grub menu is on the Fedora and works Flawlessly. Fedora 43, Ubuntu 25.10, Debian 13, Zorin 18.1, and Linux Mint Zara 22.2 are the Linux OS.
After upgrading Fedora 43 to 44 Workstation grub selection for Ubuntu 25.10 was wipped out. Luckally I had a Rescuezilla back up of Fedora 43. The grub has been restored.
rbhawks2
Intel I9-12900HK, Nvidia 3080Ti discrete GPU, 64G 3200Mhz ram, 4Tb nvme SSD. I love Fedora 43 Workstation, but a fresh install of Fedora 44 Workstation had too many issuers. Grub errors, no dual boot, and no difference with or without Secure Boot is enabled. Extereme issues trying to get drivers installed for the Nvidia GPU.
Unforunately I beleive it’s not ready for Primetime yet.
Richard England
You should probably ask about specific issues on ask.fedoraproject.org. More people watch that than the comments on Magazine articles.
Luiz
The screen share doesn’t work anymore!! pls fix this!
Lachlan
I am on 43. I am using a few gnome extensions and tweaks, will there be any brakage if I upgrade now?
Jim
You can check at https://extensions.gnome.org if each of the extensions you care about have released updates to Gnome 50.
Tony Rawkings
I use the Fedora based Ultramarine-Gnome. They are still on 43. They will upgrade when they fixed all the wrinkles.
Manux
Great news! Thanks for the update, will wait few days just in case! Can’t wait to test the new features!
jonathan sierra o
buenas tardes.
Cuando voy a descargar la actuzalizacion de Fedora Linux 44, termina la descarga, pero no deja actualizar el equipo y me sale lo siguiente;
Error al ejecutar la transacción: conflicto del archivo /usr/share/dbus-1/system-services/net.hadess.PowerProfiles.service entre instalaciones intentadas de tlp-1.9.0-7.fc44.noarch y tuned-ppd-2.27.0-1.fc44.noarch
conflicto del archivo /usr/share/dbus-1/system-services/org.freedesktop.UPower.PowerProfiles.service entre instalaciones intentadas de tlp-1.9.0-7.fc44.noarch y tuned-ppd-2.27.0-1.fc44.noarch
conflicto del archivo /usr/share/dbus-1/system.d/net.hadess.PowerProfiles.conf entre instalaciones intentadas de tlp-1.9.0-7.fc44.noarch y tuned-ppd-2.27.0-1.fc44.noarch
conflicto del archivo /usr/share/dbus-1/system.d/org.freedesktop.UPower.PowerProfiles.conf entre in.stalaciones intentadas de tlp-1.9.0-7.fc44.noarch y tuned-ppd-2.27.0-1.fc44.noarch.
quedo atento si me pueden colaborar.
muchas gracias
Gregory Bartholomew
https://discussion.fedoraproject.org/t/43-to-44-upgrade-error-because-of-powerprofiles-service-tuned-ppd-tlp/190357