You have been subscribed to a public bug:
Binary package hint: upstart
Description: Ubuntu 9.10
Release: 9.10
upstart:
Installed: 0.6.3-10
Candidate: 0.6.3-10
Version table:
*** 0.6.3-10 0
500 http://de.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
The system has both gnome and KDE installed and /etc/X11/default-
display-manager is set to /usr/bin/kdm. When booting the system, the
screen goes black with a few scattered white pixels. No login is
possible.
The course of the problem is that /etc/init/gdm.conf, /etc/init/kdm.conf and
/etc/init/failsafe-x.conf direct the X-server into problems. /etc/init/gdm.conf
and /etc/init/kdm.conf are symmetrical as to check whether
/etc/X11/default-display-manager has been set to /usr/bin/kdm or /usr/bin/gdm
and exit (with return code 1) if it is not their turn. The return code is
recorded in /var/log/daemon.log and can be investigated with "grep init\:
/var/log/daemon.log" - like the following.
Dec 4 13:45:42 sirius init: gdm main process (1161) terminated with status 1
This would be perfectly OK, if failsafe-x hadn't specified "start on
stopped gdm EXIT_STATUS=[!0]". This means that with /etc/X11/default-
display-manager set to /usr/bin/kdm, both kdm and failsafe-x come up and
compete for starting the X server on DISPLAY 0.0 (actually they compete
for a X11 lock file).
My current work around is commenting out all active lines in
/etc/init/failsafe-x.conf .
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
kdm.conf and failsafe-x.conf compete to start X session
https://bugs.launchpad.net/bugs/492339
You received this bug notification because you are a member of Ubuntu-X, which
is subscribed to xorg in ubuntu.
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
