[Bug 664514] New: systemd: dbus daemon is not started on boot, must be triggered manually
https://bugzilla.novell.com/show_bug.cgi?id=664514 https://bugzilla.novell.com/show_bug.cgi?id=664514#c0 Summary: systemd: dbus daemon is not started on boot, must be triggered manually Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: kasievers@novell.com ReportedBy: mvyskocil@novell.com QAContact: qa@suse.de CC: aj@novell.com Found By: Development Blocker: --- The dbusd is not started on boot - it causes the ConsoleKit error Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory The systemctl command did not helped me: $ systemctl list-units --all | grep dbus dbus.service loaded inactive dead D-Bus System Message Bus dbus.socket loaded inactive dead D-Bus System Message Bus dbus.target loaded inactive dead D-Bus $ systemctl status dbus.service dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service) Active: inactive (dead) CGroup: name=systemd:/system/dbus.service The similar is for .socket and .target This dependency might be pulled by multi-user.target, because dbus.target is in it's .wants/ directory, but that did not happened. There's nothing about dbus.{target,service,.socket) in system log, even if I have systemd.log_level=debug. grep dbus messages Jan 14 10:45:03 zelva kdm: :0[4112]: Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Jan 14 10:51:13 zelva systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/dbus_2etarget Jan 14 10:51:19 zelva systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/dbus_2esocket Jan 14 10:51:24 zelva systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/dbus_2eservice Jan 14 10:53:50 zelva systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/dbus_2eservice Jan 14 10:53:59 zelva systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/dbus_2eservice Jan 14 11:00:19 zelva systemd[1]: Failed to get system D-Bus connection, retrying later: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Jan 14 11:00:19 zelva systemd[1]: Failed to get API D-Bus connection, retrying later: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Manual start of socket or service works well. isolate of multi-user.target or graphical.target did not make it inactive too. /var/run is on tmpfs - but that's expected with systemd afaics -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=664514
https://bugzilla.novell.com/show_bug.cgi?id=664514#c1
--- Comment #1 from Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=664514
https://bugzilla.novell.com/show_bug.cgi?id=664514#c2
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=664514
https://bugzilla.novell.com/show_bug.cgi?id=664514#c3
Michal Vyskocil
participants (1)
-
bugzilla_noreply@novell.com