D-Bus activation problem

Leloup · 2025-04-23 08:48:10

Bonjour,

It's more of an alarm, but when I look in the logs it's quite frequent. I don't really know if it's a nuisance or not.

The error I'm getting, “activation request for ‘org.freedesktop.resolve1’ failed: the systemd unit ‘dbus-org.freedesktop.resolve1.service’ could not be found”, indicates that the D-Bus service for resolve1 is not available on my system. There are several possible reasons for this:

Missing service: The dbus-org.freedesktop.resolve1.service is not installed or enabled on my system. This service is usually linked to systemd-resolved, which handles DNS resolution.

NetworkManager configuration: I don't know what to think of NetworkManager, it can be configured not to use systemd-resolved. This can be checked in the NetworkManager configuration file (usually located in /etc/NetworkManager/NetworkManager.conf).

perhaps I should:
Install or activate systemd-resolved:

Check whether systemd-resolved is installed and active: bash systemctl status systemd-resolved
If not, perhaps with: bash sudo systemctl enable --now systemd-resolved

Configure NetworkManager:
Perhaps using systemd-resolved, configure NetworkManager to ignore this service. Add or modify the file /etc/NetworkManager/conf.d/no-systemd-resolved.conf with the following content: [main] systemd-resolved=false

I confess. I don't really know what to do.

Any ideas?

Regards, Leloup

V1del · 2025-04-23 09:03:27

As far as ChatGPT suggestions go this is somewhat tame and you could indeed follow either of those. Generally it's good that you don't blindly run it's suggestions and ask here first before shooting yourself in the foot.

Ultimately it's up to you whether you want to do this. NetworkManager handles DNS requests on it's own if systemd-resolved isn't running. systemd-resolved also provides an mDNS implementation so if you want local hostname resolution it could be an option in lieu of avahi. If these terms confuse and mean nothing to you, it's pretty safe to say it's not going to inherently matter. If it's just to get rid of the warning without changing anything else, the conf option is of course an option -- though it should normally not try to query systemd-resolved if /etc/resolv.conf is not a symlink already.

Might want to post

stat /etc/resolv.conf
 find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Last edited by V1del (2025-04-23 10:07:28)

Leloup · 2025-04-23 14:45:10

$ stat /etc/resolv.conf
Fichier : /etc/resolv.conf
Taille : 81 Blocs : 8 Blocs d'E/S : 4096 fichier régulier
Périphérique : 253/2 Inœud : 416755 Liens : 1
Accès : (0644/-rw-r--r--) UID : ( 0/ root) GID : ( 0/ root)
Accès : 2025-04-23 15:47:34.319946080 +0200
Modif. : 2025-04-23 15:47:32.991282186 +0200
Changt : 2025-04-23 15:47:33.015294185 +0200
Créé : 2025-04-23 15:47:32.991282186 +0200

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
display-manager.service | system
getty@tty1.service | getty.target.wants
gnome-keyring-daemon.socket | sockets.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
nvidia-hibernate.service | systemd-hibernate.service.wants
nvidia-resume.service | systemd-hibernate.service.wants
nvidia-resume.service | systemd-suspend.service.wants
nvidia-resume.service | systemd-suspend-then-hibernate.service.wants
nvidia-suspend.service | systemd-suspend.service.wants
p11-kit-server.socket | sockets.target.wants
pipewire-pulse.socket | sockets.target.wants
pipewire-session-manager.service | user
pipewire.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
systemd-userdbd.socket | sockets.target.wants
vboxservice.service | multi-user.target.wants
wireplumber.service | pipewire.service.wants
xdg-user-dirs-update.service | default.target.wants
[Mikaou@mikaouArch ~]$

V1del · 2025-04-23 15:00:50

That looks like it's supposed to, I wonder whether it's really NM triggering the "spam" (can you define that? Is it multiple times during the same boot or just once?) or some other process trying to talk to resolved at first.

And for the future please use [code][/code] tags instead of quote for outputs and adjust your post in this regard.

Last edited by V1del (2025-04-23 15:01:31)

seth · 2025-04-23 15:16:53

stat /usr/share/dbus-1/system.d/org.freedesktop.resolve1.conf
pacman -Qikk systemd

Do you intent to use resolved as local DNS cache?
Do you already have a (caching) local DNS server (eg. in your ISP issued switchroutermodemthatdoesdhcpanddns combo?)

Arch Linux

#1 2025-04-23 08:48:10

D-Bus activation problem

#2 2025-04-23 09:03:27

Re: D-Bus activation problem

#3 2025-04-23 14:45:10

Re: D-Bus activation problem

#4 2025-04-23 15:00:50

Re: D-Bus activation problem

#5 2025-04-23 15:16:53

Re: D-Bus activation problem

Board footer