And of corse, this is the snippet from the log - X-server dies!!! See here:
May 16 11:47:31 localhost kdm[3491]: X server died during startup May 16 11:47:31 localhost kdm[3491]: X server for display :0 cannot be started, session disabled and here: May 16 11:48:30 localhost acpid: 1 client rule loaded May 16 11:48:30 localhost kdm[6182]: X server died during startup May 16 11:48:30 localhost kdm[6182]: X server for display :0 cannot be started, session disabled and here: y 16 13:10:24 localhost snort[5248]: 137 client (Footprint) May 16 13:10:24 localhost snort[5248]: 139 client (Footprint) May 16 13:10:24 localhost kdm[3965]: X server for display :0 cannot be started, session disabled May 16 13:10:24 localhost snort[5248]: 143 client (Footprint) May So it is NOT kdm, but xserver itself. Just as I mentioned related to the Xorg.log I sent. If evdev is the indeed the reason for this is still not proved, but the reason is NOT kdm ( treid also gdm and xdm, with the same result) Cheers Hans -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
