can I ignore this?
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.2
Kernel Version: 7.1.13-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX Vega
What command did you run that reported that error?
AI overview:
What is
00-systemd-inhibit.conf?
I suspect a conflict with some change to libdnf5. Gnome doesn’t seem to have it. What does dnf5 provides /lib/dnf/libdnf5-plugins/00-systemd-inhibit.conf show? Maybe reinstall the package using dnf5 will get a working version.
Looks like it was added by https://src.fedoraproject.org/rpms/dnf5/c/0b5b7119f282e61421dd6a32cfed5f439b0b3b81?branch=f44
If you can’t get updates to work on the command line you should be able to disable plugins by doing: DNF5_PLUGINS_DIR=/dev/null sudo dnf upgrade --refresh
ref: 2521321 – DNF5 undefined symbol occurs with latest release of DNF5.
As far as I’m seeing here on Fedora 44 KDE, the problem is the persistence of the “Failed Offline Update” message, which appears on every boot, and I can’t find any way to clear it. The libdnf5 and libdnf5-plugin-systemd-inhibit packages seem to be installed fine. Reinstalling them generates no errors, and all dnf commands seem to report all is well.
I had this error happen on four Fedora 44 KDE installations. Of the four, two eventually stopped popping up the error every boot, though I couldn’t tell you why. The other two stubbornly display the message every boot no matter what I try.
Have you compared the currently installed versions of libdnf5?
It’s the same version on all systems (5.4.4.0-1.fc44). Interestingly, when I booted up one of the affected systems just now to double-check the dnf5 version, it now no longer is popping up the “Failed Offline Update” message. I did no action that should have contributed to this change, so I wonder if its presence is timing-based, e.g., the message shows up every boot for x number of hours after its first displayed, and then it goes away? I have no clue.
My guess is that the packagekitd rebuilt the list of packages needing updates. I update early and often (so if there is an issue I only have a few packages to investigate) from the command-line. I consider packagekitd not yet fully baked, so Fedora users who do use packagekitd can expect some rough edges, but are contributing to efforts to polish the thing so it can be reliable for users who never resort to command-line tools.
