NetworkManager-initrd tries starts despite NetworkManager running

jl2 · 2025-08-27 15:18:14

I continuously get this error over larger time intervals:

Aug 27 07:38:25 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:38:25 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:38:25 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:38:25 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:38:25 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:50:55 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:58:00 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:58:01 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:58:01 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:58:01 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:58:01 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 08:01:30 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 08:01:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 16:47:56 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 16:47:57 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 16:47:57 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 16:47:58 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 16:47:58 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 17:09:29 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 17:12:27 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 17:12:27 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 17:12:30 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

The computer has started up at around 7:35, with GUI and everything. The GUI was idle after 8:30 and crashed at around 10:25 and restarted somewhere around 4:40, So it must be somehow correlated to the GUI.

It is accompanied by this error:

Aug 27 07:38:25 PC systemd[1]: Failed to put bus name to hashmap: File exists
Aug 27 07:38:25 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 27 07:38:25 PC systemd[1]: Failed to put bus name to hashmap: File exists
Aug 27 07:38:25 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

What could be starting the second NetworkManager instance? All my scripts run way more often and on more regular intervals than the service is started.

Scimmia · 2025-08-27 16:01:35

Let's start with the basics, what does `tree /etc/systemd/` show?

jl2 · 2025-08-27 16:54:43

'tree /etc/systemd/':

/etc/systemd/
├── coredump.conf
├── homed.conf
├── journald.conf
├── journal-remote.conf
├── journal-upload.conf
├── logind.conf
├── network
├── networkd.conf
├── oomd.conf
├── pstore.conf
├── resolved.conf
├── sleep.conf
├── system
│   ├── bluetooth.target.wants
│   │   └── bluetooth.service -> /usr/lib/systemd/system/bluetooth.service
│   ├── cpu_gov.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.resolve1.service -> /usr/lib/systemd/system/systemd-resolved.service
│   ├── dbus-org.freedesktop.timesync1.service -> /usr/lib/systemd/system/systemd-timesyncd.service
│   ├── default.target.wants
│   │   ├── pacman-cacheserver.service -> /etc/systemd/system/pacman-cacheserver.service
│   │   └── pacman-reposerver.service -> /etc/systemd/system/pacman-reposerver.service
│   ├── display-manager.service -> /usr/lib/systemd/system/greetd.service
│   ├── getty.target.wants
│   │   └── getty@tty1.service -> /usr/lib/systemd/system/getty@.service
│   ├── getty@tty1.service.d
│   │   └── autologin.conf
│   ├── gpu_oc.service
│   ├── iwd.service.d
│   │   └── 90-networkmanager.conf
│   ├── monitor_brightness.service
│   ├── multi-user.target.wants
│   │   ├── cpu_gov.service -> /etc/systemd/system/cpu_gov.service
│   │   ├── dhcpcd.service -> /usr/lib/systemd/system/dhcpcd.service
│   │   ├── earlyoom.service -> /usr/lib/systemd/system/earlyoom.service
│   │   ├── gpu_oc.service -> /etc/systemd/system/gpu_oc.service
│   │   ├── lm_sensors.service -> /usr/lib/systemd/system/lm_sensors.service
│   │   ├── monitor_brightness.service -> /etc/systemd/system/monitor_brightness.service
│   │   ├── NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
│   │   ├── powercap_perm.service -> /etc/systemd/system/powercap_perm.service
│   │   ├── remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
│   │   ├── rfkill-block@bluetooth.service -> /usr/lib/systemd/system/rfkill-block@.service
│   │   ├── rfkill-block@wlan.service -> /usr/lib/systemd/system/rfkill-block@.service
│   │   ├── rfkill-unblock@wlan.service -> /usr/lib/systemd/system/rfkill-unblock@.service
│   │   └── sshd.service -> /usr/lib/systemd/system/sshd.service
│   ├── network-online.target.wants
│   │   ├── NetworkManager-wait-online.service -> /usr/lib/systemd/system/NetworkManager-wait-online.service
│   │   ├── pacman-cacheserver.service -> /etc/systemd/system/pacman-cacheserver.service
│   │   └── pacman-reposerver.service -> /etc/systemd/system/pacman-reposerver.service
│   ├── pacman-cacheserver.service
│   ├── pacman-reposerver.service
│   ├── powercap_perm.service
│   ├── sheepit-client.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-resolved.service -> /usr/lib/systemd/system/systemd-resolved.service
│   │   └── systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service
│   ├── timers.target.wants
│   │   └── reflector.timer -> /usr/lib/systemd/system/reflector.timer
│   ├── train_ai.service
│   └── train_ai.target
├── 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
└── user.conf

17 directories, 62 files

Scimmia · 2025-08-27 17:01:37

I see 2 potential issues. 1st, you have dhcpcd and NetworkManager both enabled, they will both be fighting for control of the interfaces. Don't do that. 2nd:

│   │   ├── rfkill-block@wlan.service -> /usr/lib/systemd/system/rfkill-block@.service
│   │   ├── rfkill-unblock@wlan.service -> /usr/lib/systemd/system/rfkill-unblock@.service

What is this supposed to do?

jl2 · 2025-08-27 17:45:23

you have dhcpcd and NetworkManager both enabled

Right, a leftover of my old networking config. dhcpcd isn't installed though.

What is this supposed to do?

It changes nothing though, NetworkManager overrides rfkill later on in the boot process (took me quite some google searches to find out).

I removed all 3 of them anyways.

Last edited by jl2 (2025-08-27 17:45:49)

seth · 2025-08-27 17:54:12

You also have
│ │ ├── dhcpcd.service -> /usr/lib/systemd/system/dhcpcd.service

Why is "NetworkManager-initrd.service" enabled itfp? This is for the initramfs, https://networkmanager.dev/blog/networkmanager-1-54/ - are you using dracut?
https://man.archlinux.org/man/nm-initrd-generator.8

Last edited by seth (2025-08-27 17:55:06)

Succulent of your garden · 2025-08-28 01:41:48

Jan wrote:

│ ├── iwd.service.d
│ │ └── 90-networkmanager.conf

Are you running iwd to get wifi ? check this https://wiki.archlinux.org/title/Iwd

Arch wiki wrote:

iwd can work in standalone mode or in combination with comprehensive network managers like ConnMan, systemd-networkd and NetworkManager.
Do not follow the instructions on this page when using iwd via a network manager unless it is explicitly stated otherwise in that network manager's article.

It could be that you had setup the iwd backend as standalone an need to attach it to networkmanager.

But probably just follow tomorrow uncle Seth advice, since both of you are in neighbor countries your sleep time are pretty much the same . The pot plant here is sleeping while both of you are awakening in the morning. Now like tears in rain, time to sleep. Gute Nacht! zzzz zzzz zzzz.... error 404: succulent container not found.

Last edited by Succulent of your garden (2025-08-28 01:47:58)

jl2 · 2025-08-28 13:38:31

It could be that you had setup the iwd backend as standalone an need to attach it to networkmanager.

Yessir, networkmanager-iwd it is.
https://bbs.archlinux.org/viewtopic.php?id=305388

Why is "NetworkManager-initrd.service" enabled itfp?

I have no idea. I'm also not trying to start it. But it's somehow linked to the GUI for some reason.
I ran the nm-initrd-generator, it does not trigger the error nor output anything.

Perhaps I should just mask it. Or do you have other ideas @seth?

Last edited by jl2 (2025-08-28 13:39:07)

seth · 2025-08-28 14:56:36

seth wrote:

are you using dracut?

The NM-initrd.service is likely (only) in your initramfs, so we'll have to take a look at its configuration (and pot. output when regenerating it)

jl2 · 2025-08-28 18:24:09

are you using dracut?

no.

The NM-initrd.service is likely (only) in your initramfs, so we'll have to take a look at its configuration (and pot. output when regenerating it)

Umm, I'm pretty sure you know how to get the configs ...

I ran the nm-initrd-generator, it does not trigger the error nor output anything.

Another point: The nm-initrd is never started. The only output from systemctl status is the error messages from OP.
(currently not on linux, if you want I can get the systemctl status output later)

Succulent of your garden · 2025-08-28 19:16:13

Another thing to check is to search for the processes that are called network-manager, and find which ones are the master and which ones are the workers. Probably you will have two, If you saw one master and one worker then probably a good idea is to kill the worker and see what happen. If there are two masters, then try to guess which one to kill so the other one can do the job well.

I need to do a remembering, but in a couple of hours probably I'm going to send that command for it, I don't just want to LLM that and send the output without trying it, but this could be also a good idea to troubleshoot the issue.

Last edited by Succulent of your garden (2025-08-28 19:18:01)

seth · 2025-08-28 19:36:05

Umm, I'm pretty sure you know how to get the configs ...

Probably https://wiki.archlinux.org/title/Mkinitcpio ?
/etc/mkinitcpio.conf, mkinicpio -P, lsinitcpio /boot/initramfs*.img | grep NetworkManager

jl2 · 2025-08-28 19:37:48

Another thing to check is to search for the processes that are called network-manager, and find which ones are the master and which ones are the workers. Probably you will have two, If you saw one master and one worker then probably a good idea is to kill the worker and see what happen. If there are two masters, then try to guess which one to kill so the other one can do the job well.

That's not relevant. We're trying to find out why nm-initrd is started, because it obviously should not start because it conflicts with the normal networkmanager (luckily systemd takes care of this). Also, it has "initrd" in it's name, so it is designed to be started very early in the boot process, which IMO I do not need because the regular nm does a good job.

Succulent of your garden · 2025-08-29 00:16:57

Jan wrote:

That's not relevant. We're trying to find out why nm-initrd is started

My bad, sorry. I didn't read well the thread and I was thinking about that. Tomorrow I'm going to read it well in the morning, and if I found something useful to say, obviously I'm going to share it. Sadly today I wasn't able to do it, Today I felt very tired and in the end I just rest, but probably tomorrow I will be okey [I'm still with the damn flue, but now only very little in my lungs]

Last edited by Succulent of your garden (2025-08-29 00:18:10)

Succulent of your garden · 2025-08-29 14:28:05

Jan wrote:

I have no idea. I'm also not trying to start it. But it's somehow linked to the GUI for some reason.

If you really think is that, then just try to connect using iwctl without the gui. First check that you have iwctl in your machine, you should just open a terminal and write iwctl, then a shell session will appear to you. Check that before you uninstall the gui. Then in the following order enter:

device list // to check if you can saw you wifi card.
station <wlan> get-networks // to get nearby networks
station <wlan> connect <"network name">  //to connect to networks.
station <wlan> connect-hidden <"network name">  //to connect to hidden named networks. The ones that does not broadcast their name publicly 
quit

Where <wlan> is your internet interface, probably is wlan0 but you need to check it with the get-networks command. And <"network name"> is obviously the name of the network that you are going to connect. You don't need to put the < > and the " " could be if your net name have spaces.

If you really think is the gui that you are using making the issue, then that is going to tell us very quickly. If you are able to connect with iwctl then is the gui, but if that's not the case, then is not your gui.

If the problem is the gui, maybe you can code a pretty nice looking one using eww https://github.com/elkowar/eww and start it every time in the .xinitrc. It doesn't need to be a bar, you can create standalone widgets with eww. Also probably you can just git clone someone wifi widget already made from github .

But do that if you are pretty sure that is the gui, if not go for route seth:

seth wrote:

/etc/mkinitcpio.conf, mkinicpio -P, lsinitcpio /boot/initramfs*.img | grep NetworkManager

Last edited by Succulent of your garden (2025-08-29 14:29:35)

jl2 · 2025-08-29 16:36:00

If you really think is that, then just try to connect using iwctl without the gui.

Connecting to already known networks doesn't need any interaction from my side ... Also, the WiFi module is rfkill'd anyway, because I have ethernet.

If you really think is the gui that you are using making the issue, then that is going to tell us very quickly. If you are able to connect with iwctl then is the gui, but if that's not the case, then is not your gui.

You know, the point is that it's only the error message that appears, I might have been unclear about that. The connection itself works completely as expected.

If the problem is the gui, maybe you can code a pretty nice looking one using eww https://github.com/elkowar/eww and start it every time in the .xinitrc. It doesn't need to be a bar, you can create standalone widgets with eww. Also probably you can just git clone someone wifi widget already made from github lol.

You know me far too well https://www.reddit.com/r/unixporn/comme … uite_nice/
(It uses a rust networkmanager dbus thingy to get the wifi info)

@seth
/etc/mkinitcpio.conf (Shortened out commented lines)

MODULES=(amdgpu xfs fat)
BINARIES=(/usr/bin/ntfsfix)
FILES=()
HOOKS=(base udev autodetect modconf kms keyboard keymap block filesystems fsck)
COMPRESSION="cat"

'mkinitcpio -P --verbose | grep NetworkManager' shows nothing, full output: https://paste.c-net.org/ScrawnyNursing
'lsinitcpio /boot/efi/EFI/Linux/arch-linux.efi | grep NetworkManager' doesn't output anything either.

Succulent of your garden · 2025-08-29 17:18:30

Oh okey, I was thinking that you had connection issues, it was unclear at least for me.

Jan wrote:

You know me far too well lol https://www.reddit.com/r/unixporn/comme … uite_nice/
(It uses a rust networkmanager dbus thingy to get the wifi info)

I'm going to do my owns widgets this summer , I'm going to try to be simple and beautiful .

btw, your mkinitcpio.conf seems fine for me. but the generated one I'm not so sure, seems fine to me, at least the system is able to generate it, not sure why it should have networkmanager on it, sure seth does have a better understanding on it, now I'm here in a hurry writing

But the main question since you are probably on a RJ-45 cable using ethernet: Are you able to use your internet card without the cable ? I'm mean first I'm going to ask: Do you have some kind of wifi card available in your setup ? or you are just plugin the thing to the mobo directly and you don't have any internet card in a pci slot ? If you are currently using the pci card and does have wifi: are you able to connect using the wifi one ? If your mobo does have wifi and you want to try on it: It is possible to have a connection using wifi instead of ethernet ?

What is the whole reason of having network manager in your case [you have an dhcp service right ? I'm not sure] ? since you are on ethernet your are in someway just working on a switch level to your main router, and the main router makes all the job, in practice you are just working like in level 2-3 of OSI model between your computer and router, the connection in someway is direct, I'm not sure why you should need also a dhcp service in your case, since if I'm not wrong your ip should be assigned directly by the router, since you are operating more like on a "switch" level, than in a "router" level to establish the connection to your router. EDIT: OKey I forget the last part of the post were previously had been asked about the dchp thing , my bad again, sorry ]

Had you ever updated your eww package ? maybe that could be the case, If I'm not wrong eww is not in arch linux and you need to use cargo to compile it, maybe your eww version is starting to get outdated and other dependencies are starting to complain about it. But I don't think that's is your case, but nevertheless just in case.

Edit: Do you have two cards using the same ip ? I'm not sure if Linux is able to do that but you can check that also using ip a command, and saw the ip address of every card you have [it could be a virtual one also].

Last edited by Succulent of your garden (2025-08-29 17:27:24)

jl2 · 2025-08-29 17:42:18

But the main question since you are probably on a RJ-45 cable using ethernet: Are you able to use your internet card without the cable ? I'm mean first I'm going to ask: Do you have some kind of wifi card available in your setup ? or you are just plugin the thing to the mobo directly and you don't have any internet card in a pci slot ? If you are currently using the pci card and does have wifi: are you able to connect using the wifi one ? If your mobo does have wifi and you want to try on it: It is possible to have a connection using wifi instead of ethernet ?
What is the whole reason of having network manager in your case [you have an dhcp service right ? I'm not sure] ? since you are on ethernet your are in someway just working on a switch level to your main router, and the main router makes all the job, in practice you are just working like in level 2-3 of OSI model between your computer and router, the connection in someway is direct, I'm not sure why you should need also a dhcp service in your case, since if I'm not wrong your ip should be assigned directly by the router, since you are operating more like on a "switch" level, than in a "router" level to establish the connection to your router. EDIT: OKey I forget the last part of the post were previously had been asked about the dchp thing lol, my bad again, sorry tongue]
Had you ever updated your eww package ? maybe that could be the case, If I'm not wrong eww is not in arch linux and you need to use cargo to compile it, maybe your eww version is starting to get outdated and other dependencies are starting to complain about it. But I don't think that's is your case, but nevertheless just in case.
Edit: Do you have two cards using the same ip ? I'm not sure if Linux is able to do that but you can check that also using ip a command, and saw the ip address of every card you have [it could be a virtual one also].

Appreciate the efforts, but now I think we're going in the wrong direction ...
I don't think it's a problem of the hardware, because not one udev rule contains nm in them (checked with grep).
IP is OK, eww does not interact with nm/iwd in any way other than my gatherer scripts, I have a motherboard RJ45, a usb adapter, and a intel PCIe WiFi Card, but as said, HW shouldn't be a problem. (<= These all worked OOTB BTW)

I use NetworkManager because I can not use dhcpcd+iwd with network monitoring tools, and I have the nm+iwd setup to keep iwgtk because it's awesome and way better then any other DE-agnostic NetworkManager GUI.

seth · 2025-08-29 17:50:18

'lsinitcpio /boot/efi/EFI/Linux/arch-linux.efi | grep NetworkManager' doesn't output anything either.

Not sure that lsinitcpio can decode UKIs

systemctl status NetworkManager-initrd.service

and then please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Succulent of your garden · 2025-08-29 18:05:09

Jan wrote:

Appreciate the efforts, but now I think we're going in the wrong direction ...
I don't think it's a problem of the hardware, because not one udev rule contains nm in them (checked with grep).
IP is OK, eww does not interact with nm/iwd in any way other than my gatherer scripts, I have a motherboard RJ45, a usb adapter, and a intel PCIe WiFi Card, but as said, HW shouldn't be a problem. (<= These all worked OOTB BTW)
I use NetworkManager because I can not use dhcpcd+iwd with network monitoring tools, and I have the nm+iwd setup to keep iwgtk because it's awesome and way better then any other DE-agnostic NetworkManager GUI.

Okey , then follow seth branch instead

jl2 · 2025-08-29 18:15:27

Not sure that lsinitcpio can decode UKIs

It didn't throw an error ...
But I have nothing special configured with services in the initcpio, so I guess your output has the same value (unless you explicitly added it)

https://paste.c-net.org/GoldfarbNative

○ NetworkManager-initrd.service - NetworkManager (initrd)
     Loaded: error (Reason: Unit NetworkManager-initrd.service failed to load properly, please adjust/correct and reload service manager: File exists)
     Active: inactive (dead)

Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 20:14:35 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 20:14:58 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 20:15:04 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

seth · 2025-08-29 18:39:43

Aug 29 07:44:40 PC NetworkManager[792]: <info>  [1756446280.9958] NetworkManager (version 1.54.0-1) is starting... (boot:c41659c4-f4cc-4fe1-950d-5ca7de7f075b)
Aug 29 07:44:40 PC NetworkManager[792]: <info>  [1756446280.9959] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/{20-connectivity.conf,30-wifi-backend.conf}
…
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

So this is actually triggered super-late.

Specifically

Aug 29 08:14:19 PC sudo[40714]:  janluca : TTY=pts/0 ; PWD=/home/janluca ; USER=root ; COMMAND=/usr/bin/pacman --sync -y --
Aug 29 08:14:19 PC sudo[40714]: pam_unix(sudo:session): session opened for user root(uid=0) by janluca(uid=1000)
Aug 29 08:14:19 PC sudo[40714]: pam_unix(sudo:session): session closed for user root
Aug 29 08:14:38 PC systemd[1185]: Starting User preferences database...
Aug 29 08:14:38 PC systemd[1185]: Started User preferences database.
Aug 29 08:14:40 PC systemd[1]: Failed to put bus name to hashmap: File exists
Aug 29 08:14:40 PC systemd[1]: NetworkManager-initrd.service: Two services allocated for the same bus name org.freedesktop.NetworkManager, refusing operation.

You're performing a questionable pacman -Sy (why?! WHY!!!)
Then the dconf.service seems to re-start and that seems to trigger the NM-initrd service for whatever reasons.
Did that thing somehow end up in the user services, https://wiki.archlinux.org/title/Systemd/User ?

Also what were you doing before the service flared up?

Succulent of your garden · 2025-08-29 19:03:41

seth wrote:

Also what were you doing before the service flared up?

The system said that before the error Jan was in order:
+ Training a neural network which seems to be a systemd service.
+ Opening his browser.
+ Performing pacman -Sy

That is what I saw in the first iteration of the error. I don't think that the meow_meow service could be an issue, but does this issue started after the creation of that service Jan ? Just in case.

Last edited by Succulent of your garden (2025-08-29 19:04:28)

seth · 2025-08-29 19:06:56

Yeah, but not "long before" - I esp. wonder about what causes the dconf.service start.

jl2 · 2025-08-29 20:51:53

So this is actually triggered super-late.

Oh, I thought you read the timestamps in the OP (because I was listing what I was doing at what time). But I also thought I had a journal there, so ...

You're performing a questionable pacman -Sy (why?! WHY!!!)

That's paru ... got the trust in it that it won't nuke my system.

Also what were you doing before the service flared up?

I can set up the systemd-notify-on-failure thingy so I get notified and then I'll report back.

Arch Linux

#1 2025-08-27 15:18:14

NetworkManager-initrd tries starts despite NetworkManager running

#2 2025-08-27 16:01:35

Re: NetworkManager-initrd tries starts despite NetworkManager running

#3 2025-08-27 16:54:43

Re: NetworkManager-initrd tries starts despite NetworkManager running

#4 2025-08-27 17:01:37

Re: NetworkManager-initrd tries starts despite NetworkManager running

#5 2025-08-27 17:45:23

Re: NetworkManager-initrd tries starts despite NetworkManager running

#6 2025-08-27 17:54:12

Re: NetworkManager-initrd tries starts despite NetworkManager running

#7 2025-08-28 01:41:48

Re: NetworkManager-initrd tries starts despite NetworkManager running

#8 2025-08-28 13:38:31

Re: NetworkManager-initrd tries starts despite NetworkManager running

#9 2025-08-28 14:56:36

Re: NetworkManager-initrd tries starts despite NetworkManager running

#10 2025-08-28 18:24:09

Re: NetworkManager-initrd tries starts despite NetworkManager running

#11 2025-08-28 19:16:13

Re: NetworkManager-initrd tries starts despite NetworkManager running

#12 2025-08-28 19:36:05

Re: NetworkManager-initrd tries starts despite NetworkManager running

#13 2025-08-28 19:37:48

Re: NetworkManager-initrd tries starts despite NetworkManager running

#14 2025-08-29 00:16:57

Re: NetworkManager-initrd tries starts despite NetworkManager running

#15 2025-08-29 14:28:05

Re: NetworkManager-initrd tries starts despite NetworkManager running

#16 2025-08-29 16:36:00

Re: NetworkManager-initrd tries starts despite NetworkManager running

#17 2025-08-29 17:18:30

Re: NetworkManager-initrd tries starts despite NetworkManager running

#18 2025-08-29 17:42:18

Re: NetworkManager-initrd tries starts despite NetworkManager running

#19 2025-08-29 17:50:18

Re: NetworkManager-initrd tries starts despite NetworkManager running

#20 2025-08-29 18:05:09

Re: NetworkManager-initrd tries starts despite NetworkManager running

#21 2025-08-29 18:15:27

Re: NetworkManager-initrd tries starts despite NetworkManager running

#22 2025-08-29 18:39:43

Re: NetworkManager-initrd tries starts despite NetworkManager running

#23 2025-08-29 19:03:41

Re: NetworkManager-initrd tries starts despite NetworkManager running

#24 2025-08-29 19:06:56

Re: NetworkManager-initrd tries starts despite NetworkManager running

#25 2025-08-29 20:51:53

Re: NetworkManager-initrd tries starts despite NetworkManager running

Board footer