Sebastian P. Luque wrote: > On Fri, 04 May 2007 20:25:43 +0200, > Brice Goglin <[EMAIL PROTECTED]> wrote: > > [...] > > >> Did you upgrade some kde packages recently? (/var/log/dpkg.log might be >> helpful) Does the problem happens if you don't use KDM at all? either >> use startx directly to login, or use xdm or gdm? The only related bug I >> found in KDE is #395570 but it does not look similar to you problem. >> > > I don't know how to use startx or activate gdm (I do have it installed), > rather than kdm.
dpkg-reconfigure gdm shoud ask you to choose between gdm/kdm/xdm/... Anyway, to eliminate all possible problems related to X, the best would be to disable gdm/kdm/xdm/... at startup (moving their /etc/init.d/foo script away temporarily is an easy way to do so), reboot (you shouldn't get X started automatically) and check whether the problem occurs. > However, I found something else. During boot-up the > light is on, but if I hit the Num Lock key at this stage it gets turned > off for good; i.e. it can't be toggled back on. This suggests it's a > kernel problem. So maybe this bug should go to linux-image-2.6.20-1-amd64 > or the headers package? I would rather say linux-image-2.6.20-1-amd64 since the headers are basically useless as long as you don't build anything. Before reassigning the bug to linux-2.6, it would be good to downgrade to the previous kernel (probably linux-image-2.6.18-foo-amd64, see /var/log/dpkg.log) or reboot on it if it is still installed, and see whether the problems goes away. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
