https://bugzilla.novell.com/show_bug.cgi?id=664308 https://bugzilla.novell.com/show_bug.cgi?id=664308#c42 --- Comment #42 from Dr. Werner Fink <werner@novell.com> 2011-01-26 08:16:36 UTC --- You should grep for gdm not xdm: you log with ereased environment informations <notice -- Jan 25 21:52:43.168701000> service xdm start <notice -- Jan 25 21:52:43.216627000> startproc: execve (/usr/sbin/gdm) [...] <notice -- Jan 25 21:52:43.258469000> service xdm done <notice -- Jan 25 21:52:43.518884000> startproc: execve (/sbin/auditd) [...] + '[' -x /etc/X11/xdm/keytable ']' + /etc/X11/xdm/keytable + test -x /etc/X11/xdm/TakeDevices + /etc/X11/xdm/TakeDevices as you can see if you have look on /etc/init.d/xdm the /etc/X11/xdm/TakeDevices only will be called if startproc is not able to start the gdm. Make sure that you're using the latest sysvinit package and retry as there was a small bug which only hurts if and only if a partition was mounted twice. If this does not help you should investigate why gdm fails or return with an exit status not equal to zero. You may add the option -v to startproc, then it will report the pid of the process id of the gdm (which could be the pid of the parent of the gdm deamon as). -- 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.