NetworkManager-initrd.service Error same bus name

plrigaux · 2025-09-21 21:47:56

Hello,

I was scanning my services and I found that the service NetworkManager-initrd.service is not loaded and has errors. I don't what are the consequences of this errors beside the logs.

I want to know how to find what services are competing for the same bus name and how to solve it.

Thank you

Sep 21 17:29:36 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:36 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:36 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:36 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:29 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:29 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:29 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:29 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:24 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:29:21 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:09:07 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:09:07 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:09:07 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:09:07 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:08:05 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:08:01 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:07:47 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Sep 21 17:07:45 systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

Here the display of my `tree /etc/systemd/`

/etc/systemd/
├── coredump.conf
├── homed.conf
├── journald.conf
├── journal-remote.conf
├── journal-upload.conf
├── logind.conf
├── logind.conf.pacnew
├── network
├── networkd.conf
├── oomd.conf
├── pstore.conf
├── resolved.conf
├── sleep.conf
├── system
│   ├── bluetooth.target.wants
│   │   └── bluetooth.service -> /usr/lib/systemd/system/bluetooth.service
│   ├── dbus-org.bluez.service -> /usr/lib/systemd/system/bluetooth.service
│   ├── dbus-org.freedesktop.nm-dispatcher.service -> /usr/lib/systemd/system/NetworkManager-dispatcher.service
│   ├── dbus-org.freedesktop.timesync1.service -> /usr/lib/systemd/system/systemd-timesyncd.service
│   ├── display-manager.service -> /usr/lib/systemd/system/gdm.service
│   ├── getty.target.wants
│   │   └── getty@tty1.service -> /usr/lib/systemd/system/getty@.service
│   ├── httpd.service.d
│   │   └── hardening.conf
│   ├── jackett.service
│   ├── multi-user.target.wants
│   │   ├── cups.path -> /usr/lib/systemd/system/cups.path
│   │   ├── cups.service -> /usr/lib/systemd/system/cups.service
│   │   ├── jackett.service -> /etc/systemd/system/jackett.service
│   │   ├── NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
│   │   ├── remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
│   │   └── tiny_daemon.service -> /usr/lib/systemd/system/tiny_daemon.service
│   ├── network-online.target.wants
│   │   └── NetworkManager-wait-online.service -> /usr/lib/systemd/system/NetworkManager-wait-online.service
│   ├── printer.target.wants
│   │   └── cups.service -> /usr/lib/systemd/system/cups.service
│   ├── sockets.target.wants
│   │   ├── cups.socket -> /usr/lib/systemd/system/cups.socket
│   │   └── systemd-userdbd.socket -> /usr/lib/systemd/system/systemd-userdbd.socket
│   ├── sysinit.target.wants
│   │   └── systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service
│   ├── systemd-hibernate.service.wants
│   │   ├── nvidia-hibernate.service -> /usr/lib/systemd/system/nvidia-hibernate.service
│   │   └── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   ├── systemd-suspend.service.wants
│   │   ├── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   │   └── nvidia-suspend.service -> /usr/lib/systemd/system/nvidia-suspend.service
│   └── timers.target.wants
│       ├── fstrim.timer -> /usr/lib/systemd/system/fstrim.timer
│       └── paccache.timer -> /usr/lib/systemd/system/paccache.timer
├── system.conf
├── timesyncd.conf
├── user
│   ├── default.target.wants
│   │   └── xdg-user-dirs-update.service -> /usr/lib/systemd/user/xdg-user-dirs-update.service
│   ├── pipewire.service.wants
│   │   └── wireplumber.service -> /usr/lib/systemd/user/wireplumber.service
│   ├── pipewire-session-manager.service -> /usr/lib/systemd/user/wireplumber.service
│   └── sockets.target.wants
│       ├── gnome-keyring-daemon.socket -> /usr/lib/systemd/user/gnome-keyring-daemon.socket
│       ├── p11-kit-server.socket -> /usr/lib/systemd/user/p11-kit-server.socket
│       ├── pipewire-pulse.socket -> /usr/lib/systemd/user/pipewire-pulse.socket
│       ├── pipewire.socket -> /usr/lib/systemd/user/pipewire.socket
│       └── speech-dispatcher.socket -> /usr/lib/systemd/user/speech-dispatcher.socket
├── user.conf
└── zram-generator.conf

18 directories, 49 files

PS

I post a new topic because I didn't (or not able) to find an answer in this post https://bbs.archlinux.org/viewtopic.php?id=307879

PPS

Is there any other information needed?

Last edited by plrigaux (2025-09-25 00:53:50)

seth · 2025-09-21 22:00:12

Fuck, I wanted to link you https://bbs.archlinux.org/viewtopic.php?id=307879 …
But the thread went off the rails a bit, so https://bbs.archlinux.org/viewtopic.php … 9#p2260119

plrigaux · 2025-09-25 01:05:28

Ok I will take a look and come back

Is there a way to pin point witch services are allocated with the same name? Is it NetworkManager-initrd.service?

seth · 2025-09-25 06:57:16

Yup. From what I can tell this is however just noise? And to be addressed upstream anyway.
You can mask the service or edit the dbus interface of NetworkManager-initrd.service to something else

Arch Linux

#1 2025-09-21 21:47:56

NetworkManager-initrd.service Error same bus name

PS

PPS

#2 2025-09-21 22:00:12

Re: NetworkManager-initrd.service Error same bus name

#3 2025-09-25 01:05:28

Re: NetworkManager-initrd.service Error same bus name

#4 2025-09-25 06:57:16

Re: NetworkManager-initrd.service Error same bus name

Board footer