Hi all, I see a lot of DBUS error in the messages:
dbus[11185]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out dbus-daemon: dbus[11185]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out dbus[11185]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' dbus-daemon: dbus[11185]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' dbus[11185]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out dbus-daemon: dbus[11185]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out dbus[11185]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out dbus-daemon: dbus[11185]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
I use KDE and the errors are frequent when an application have to open the file selector windows (Libreoffice on save as or Virtualbox in select a disk). The timeout is about 2 3 minutes. I can't understand why (but I think this is also related to a NFS filesystem mounted on my machine - I have to test without it). Little timeout I have also when I unlock the session. A big timeout when I logoff and logon with the same user.
I can't found solutions. There is someone that had the same problem?
Bye Ambrogio
On Thu, 06 Feb 2014 18:01:30 +0100 Ambrogio De Lorenzo wrote:
Hi all, I see a lot of DBUS error in the messages:
dbus[11185]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out dbus-daemon: dbus[11185]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Could be yet another variation on this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1043212
If a reboot fixes everything, then it comes back later after cron runs or a yum update then it probably is this bug.
Hi Tom
Could be yet another variation on this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1043212
If a reboot fixes everything, then it comes back later after cron runs or a yum update then it probably is this bug.
I cant understan why you think my problem is related to this bug.
Bye Ambrogio
On Fri, 07 Feb 2014 00:00:01 +0100 Ambrogio De Lorenzo wrote:
I cant understan why you think my problem is related to this bug.
Because creating the nologin file was the original symptom people noticed first, but in reality what has happened is that systemd has gotten itself blowed up and all sorts of things get randomly screwed up depending on what gets hit by the shrapnel from the explosion. For instance, I'm almost certain these are all the same bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1057883 https://bugzilla.redhat.com/show_bug.cgi?id=1057811 https://bugzilla.redhat.com/show_bug.cgi?id=1057618 https://bugzilla.redhat.com/show_bug.cgi?id=1057614
They really should have switched back to the version of systemd on fedora 19 weeks ago, because it doesn't look like they are ever gonna figure out how to fix this bug.