Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found

I am using manjaro / arch linux and I see the following error messages in my system log.

journalctl -f
...
dbus-daemon[798]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.4' (uid=0 pid=799 comm="/usr/bin/>
dbus-daemon[798]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
...

How do I fix this problem

1

1 Answer

This problem is related to the network-manager and systemd-resolved.service.

After reading the the manjaro forums and the arch wiki

You have 2 options

configure network-manager to not use systemd-resolved.service

vim /etc/NetworkManager/conf.d/no-systemd-resolved.conf

With this content:

[main]
systemd-resolved=false

Activate and use systemd-resolved.service

check if it is running and enabled

systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-resolved.service(8) 

Enable and start it.

systemctl enable systemd-resolved.service
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /usr/lib/systemd/system/systemd-resolved.service.
Created symlink /etc/systemd/system/ → /usr/lib/systemd/system/systemd-resolved.service.
systemctl start systemd-resolved.service
systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-04-19 10:36:53 SAST; 32min ago Docs: man:systemd-resolved.service(8)
Main PID: 21150 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) Memory: 5.0M CGroup: / └─21150 /usr/lib/systemd/systemd-resolved

That solved the errors from coming up in the logs.

2

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like