Failed to Subscribe to NameOwnerChanged Signal?

Is it “normal” or expected to occasionally get “Failed to subscribe to NameOwnerChanged signal” messages? I thought I’d ask here before adding this into Github.

If I do:

journalctl -g "NameOwnerChanged"

I get variations on the following for any given boot. Sometimes there’s none, sometimes there’s a different selection:

Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.hostname1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.import1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.UPower': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.resolve1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.UDisks2': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.projectatomic.rpmostree1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'net.hadess.PowerProfiles': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.intel_lpmd': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.opengamingcollective.cardwire': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'fi.w1.wpa_supplicant1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.Accounts': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.PolicyKit1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.home1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.ModemManager1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.login1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.bolt': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.thermald': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.machine1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.RealtimeKit1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.oom1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.NetworkManager': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'inputremapper.Control': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.timesync1': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.Avahi': Device or resource busy
Nov 17 04:38:50 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'com.redhat.tuned': Device or resource busy

EDIT: I’ve never found anything in the logs saying a NameOwnerChanged was successful. But, that could very well be a knowledge problem on my part. So, I don’t know if the system tried again later and successfully did whatever it’s trying to do with those.

EDIT2: Sorry. I keep forgetting to add my system information. I’m on Bazzite version 45.20261115 (KDE Desktop).

Operating System: Bazzite 45
KDE Plasma Version: 6.8.2
KDE Frameworks Version: 6.31.0
Qt Version: 6.11.2
Kernel Version: 7.3.4-ogc6.1.fc45.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 9070 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550 VISION D-P
System Version: -CF

There was a Bazzite update queued up for me. I’m now on 45.20261117. Those errors go back to at least 01 October (6 weeks or so ago). And, after the update, the current boot has this:

Nov 17 08:03:31 bazzite systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'fi.w1.wpa_supplicant1': Device or resource busy

But, as I said earlier. Those errors change (or disappear) with each boot.

TLDR nothing related to Bazzite, its just systemd which for somereason sometimes just spams the log with things.

In any case, these look like harmless busy messages, which usually means that its already running or has been started.

“Device or resource busy” (EBUSY) here means the D-Bus subscription is already in place, not that it failed. EBUSY means “this unit already has a match or a pending GetNameOwner call.”

Is something broken or how did you even decide to look just for these? Or are you just looking at journal logs and see if something stick up, which in general is waste of time.

You can of course report these to systemd if you want but i wouldn’t really bother.

Thanks for the response. Nothing broken that I know of. Sometimes with a new Bazzite version, I’ll open the journald Browser app and see if anything looks odd. That struck me, so I thought I’d ask.