From:
[email protected]
Adeodato Sim� wrote:
that's because kdm uses the first available console unless told not to
do so. the kdmrc shipped by Debian points kdm to use console #7, but
your kdmrc probably doesnt. add this line to /etc/kde3/kdm/kdmrc:
I encountered this problem too, and it seems like it has a chance of
cropping up for anyone that's upgrading from a previous kdm version with a modified kdmrc, and doesn't choose to overwrite it with the packaged
file on upgrade. Since everyone that's ever used the Login Manager
panel in the control center will have a modified kdmrc, this could be a
lot of users....
Reverting /etc/kde3/kdm/Xservers to the previous version solved the
problem. 3.3.0-1 dropped the 'vt7' from the end of the :0 line. Might
it be worth reverting this change? I'd expect that few people have
modified Xservers, so the fix would be silent for most users.
% diff Xservers.3.3.0-1.orig Xservers
13c13
< :0 local@tty1 /usr/X11R6/bin/X -nolisten tcp
---
:0 local@tty1 /usr/X11R6/bin/X -nolisten tcp vt7
--
Nicholas Breen
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)