[Bug 725951] New: gdm fails to start - can't connect to system bus
https://bugzilla.novell.com/show_bug.cgi?id=725951 https://bugzilla.novell.com/show_bug.cgi?id=725951#c0 Summary: gdm fails to start - can't connect to system bus Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: RBrownCCB@opensuse.org QAContact: qa@suse.de Found By: --- Blocker: --- Machine running openSUSE Factory + Gnome:Factory + Gnome:Apps for Factory last zypper dup'd at approx 11:30 UTC on 22/10/2011 When booting, systemd fails to start xdm.service Rebooting with systemd being verbose shows that the root cause is gdm failing to start with the following error ** (gdm:1043): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory startproc: exit status of parent of /usr/sbin/gdm: 1 After the machine has booted, the file most certainly exists, and starting the service manually with systemctl start xdm.service works So I'm guessing this is some sort of timing issue, but as I'm new to systemd I'm not sure where to look next, help! -- 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=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c1
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c2
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c3
Richard Brown
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c4
--- Comment #4 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c5
--- Comment #5 from Richard Brown
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c6
--- Comment #6 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c7
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c8
--- Comment #8 from Harald Koenig
*** Bug 725656 has been marked as a duplicate of this bug. ***
indeed (full dmesg-systemd-1 attached)!
how to get rid of this (such) cycle(s) ?
$ dmesg | grep systemd
[ 5.882291] systemd[1]: systemd 37 running in system mode. (+PAM +LIBWRAP
+AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse)
[ 6.293614] systemd[1]: Set hostname to
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c9
--- Comment #9 from Harald Koenig
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c10
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=725951
https://bugzilla.novell.com/show_bug.cgi?id=725951#c11
Frederic Crozat
participants (1)
-
bugzilla_noreply@novell.com