I have noticed the following error messages in the system log whenever openSuse starts. This occurs on all (6) of the v12.1 systems here. The systems may run KDE or Gnome desktops. There does not appear to be any consequence(s) to its failure.
Is there a way to fix this?
Or do I just treat this as a “known good error?”
The obvious answer seems to be “find the file.” But why is it missing in the first place?
Apr 25 00:01:34 sma-station14l dbus[1142]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
Apr 25 00:01:34 sma-station14l dbus-daemon[1142]: dbus[1142]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
Apr 25 00:01:34 sma-station14l dbus[1142]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Apr 25 00:01:34 sma-station14l dbus-daemon[1142]: dbus[1142]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
$ systemctl status dbus-org.freedesktop.NetworkManager.service
dbus-org.freedesktop.NetworkManager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
I think this is a general problem with the recent kernel update they gave. It brought a systemd related issue, with me it is that “udev does not find the directory of ntp” one. I would suggest to raise a bug report, currently it seams at least that this is only the persistence of some line in some config file that is not pertinent any more and that throws the error. At least that would be my guess. (BTW I also have the 12.1 64)
I don’t think it’s a kernel problem. Rather a systemd problem, where some of the services miss configuration files. Wait for the systemd experts to drop in
I see that message on my desktop. The network there is configured to use the “ifup” configurations, so does not use NetworkManager.
I am ignoring the log message. It doesn’t seem to cause any problem.
As best I can tell, that message is logged whenever I start a browser. It is probably related to the browser trying to lookup PROXY settings, but that’s a guess.
You touched the back of my mind. Couldn’t find it, but IIRC there was something about setting Proxy to “none” instead of “auto”. But this could very well be another matter.