Hello! After a recent transactional-update, whenever I launch Discover, I get the following error.
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer ‘org.freedesktop.fwupd’: startup job failed
It works perfectly fine but the message is annoying.
Is it already a known bug?
Many thanks in advance!
I’m not seeing that error, where are you seeing it?
I’m seeing it whenever I launch Discover and fetch for updates. the error must be related to updates.
Is discover6-backend-fwupd installed?
A window is popping up with an error message when you click the Discover icon?
A window is popping up with an error message when launching from Krunner?
You’re launching it from the terminal, and seeing it?
Where are you seeing it?
I kind of need to know where if I want any chance of reproducing it and telling you how to fix it, because at the moment, I can’t reproduce.
Hello, sorry for the late response. For another reason I hade to reinstall the OS. And the issue is recurring even from a fresh reinstall using the latest iso from kalpa desktop website.
So I believe you can replicate by doing a fresh install in VM and launching Discover
Yes a window is popping up as soon as I open Discover from the application launcher and the program is fetching from updates. As well as, if you go on the “Update” section of Discover and click on “Refresh”.
If it can help, yesterday I had to change the value for “GRUB_CMDLINE_LINUX_DEFAULT” in my grub.cfg leaving the following value: “iomem=relaxed quiet splash”. The error ceased to show up. FYI I was tweaking grub.cfg for another matter which has nothing to do with Discover.
Thank you, I will look into it, although I can’t test so much for every possible hardware configuration. fwupd is really well supported on some hardware, and less so on others (Lenovo Thinkpads, for example are fairly well supported)
How the kernel cmdline may or may not interact in ways that foul up fwupd is something I’ll have to look into
So, do you get positive results if you execute these two commands at a command line … actual example below:
( sidenote: simply answer ‘N’ to both questions to not commit ).
machine:~ # fwupdmgr refresh <====== first command
Updating lvfs
Downloading… [ \ ]
Successfully downloaded new metadata: 3 local devices supported
machine :~ #
.
... and now, the second command ...
machine :~ # fwupdmgr get-updates <====== second command
Devices with no available firmware updates:
• Thunderbolt host controller
• Internal SPI Controller
Devices with the latest available firmware version:
• KBGxxZN00000 NVMe KIOXIA 256GB
• UEFI dbx
────────────────
Devices that have been updated successfully:
• UEFI dbx (371 → 20241101)
• System Firmware (1.39.2 → 1.41.1)
Uploading firmware reports helps hardware vendors to quickly identify failing and successful updates on real devices.
Review and upload report now? (Requires internet connection) [Y|n]: n
Do you want to disable this feature for future updates? [y|N]: n
Declined upload
machine:~ #
@myswtest this is the result of the first and second command:
Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer ‘org.freedesktop.fwupd’: startup job failed
@sfalken Thank you very much! I really appreciate all the work you do for the project. My machine is a Thinkpad t480 =)
Please always show commands + output in preformatted text.
Also please show systemctl status fwupd
@knurpht here it is
paolo@localhost:~> systemctl status fwupd
× fwupd.service - Firmware update daemon
Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static)
Active: failed (Result: exit-code) since Mon 2025-12-08 01:33:49 CET; 10h ago
Invocation: 4bd4df2284dc4233a6e02feed174293d
Docs: https://fwupd.org/
Process: 21863 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE)
Main PID: 21863 (code=exited, status=1/FAILURE)
CPU: 288ms
See, that is a problem. Discover needs that service to run, to get firmware updates (if they even exist). But the service needs to run.