Bug 725656

Summary: xdm/gdm does not start anymore with syslogd
Product: [openSUSE] openSUSE 12.1 Reporter: Harald Koenig <koenig>
Component: BasesystemAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Harald Koenig 2011-10-20 23:28:38 UTC
beta1 after "zypper up" to factory switched from sysvinit to systemd.
now X11 (gdm) does not start anymore.

with systemd there is no /var/log/boot.msg anymore :-(((


in /var/log/messages I find these xdm/gdm/dbus messages:

	Oct 21 01:09:05 linux-fudg cups[866]: Starting cupsd..done
	Oct 21 01:09:05 linux-fudg haveged: haveged starting up
	Oct 21 01:09:05 linux-fudg haveged: arch:        x86#012vendor:      amd#012generic:     0#012i_cache:     64#012d_cache:     64#012loop_idx:    15#012loop_idxmax: 40#012loop_sz:     64806#012loop_szmax:  100861#012etime:       23579#012havege_ndpt  0
==>	Oct 21 01:09:05 linux-fudg xdm[873]: Starting service gdm
==>	Oct 21 01:09:05 linux-fudg xdm[873]: ** (gdm:936): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Datei oder Verzeichnis nicht gefunden
==>	Oct 21 01:09:05 linux-fudg startproc: startproc:  exit status of parent of /usr/sbin/gdm: 1
==>	Oct 21 01:09:05 linux-fudg systemd[1]: xdm.service: control process exited, code=exited status=1
==>	Oct 21 01:09:05 linux-fudg xdm[873]: ..failed
	Oct 21 01:09:05 linux-fudg systemd[1]: Unit xdm.service entered failed state.
	Oct 21 01:09:06 linux-fudg network[927]: Setting up (localfs) network interfaces:
	Oct 21 01:09:06 linux-fudg network[927]: lo
	Oct 21 01:09:06 linux-fudg ifup:     lo        
	Oct 21 01:09:06 linux-fudg ifup:     lo        
	Oct 21 01:09:06 linux-fudg ifup: IP address: 127.0.0.1/8  
	Oct 21 01:09:06 linux-fudg network[927]: lo        IP address: 127.0.0.1/8
	Oct 21 01:09:06 linux-fudg ifup:  
	Oct 21 01:09:06 linux-fudg network[927]: ..done    eth0      device: Broadcom Corporation NetXtreme BCM5723 Gigabi
	

running 'init 5' from a ssh session will start X11.

BUT: that ssh login took some time (much longer as usual) and syslog shows

	Oct 21 01:09:39 linux-fudg systemd[1]: Startup finished in 6s 198ms 38us (kernel) + 50s 328ms 146us (userspace) = 56s 526ms 184us.
	Oct 21 01:09:41 linux-fudg sshd[4120]: error: Could not load host key: /etc/ssh/ssh_host_dsa_key
	Oct 21 01:09:44 linux-fudg sshd[4120]: Accepted keyboard-interactive/pam for root from 192.168.178.20 port 54195 ssh2
	Oct 21 01:09:44 linux-fudg sshd[4120]: pam_systemd(sshd:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
	Oct 21 01:17:51 linux-fudg systemd[1]: NetworkManager.service: control process exited, code=exited status=1
	Oct 21 01:17:51 linux-fudg systemd[1]: Job NetworkManager-wait-online.service/start failed with result 'dependency'.
	Oct 21 01:17:51 linux-fudg alsactl[4218]: /usr/sbin/alsactl: load_state:1586: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory


so dbus-daemon is not running at that time.  it only got started by that "init 5" command at 01:17:50 as "ps" shows:

	# ps p 4255
	  PID TTY      STAT   TIME COMMAND
	 4255 ?        Ss     0:00 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation
	# ps olstart -p 4255
	                 STARTED
	Fri Oct 21 01:17:50 2011
Comment 1 Stephan Kulow 2011-10-22 14:22:52 UTC
same for you: check dmesg for systemd cycles

*** This bug has been marked as a duplicate of bug 725951 ***