Package: xdm
Version: 1:1.1.8-3

hi!
   I've dist-upgraded from etch to lenny and now when xdm starts up
the X server at boot I get the login window but it seems totally deaf
to the keyboard. The mouse moves ok. I've tried every key with no
luck, except once when it suddenly spurted a load of
10;\99999999999999l!0 \n999999999999... running off the right side of
the login window, then going deaf again. Another (rare) time, in the
Login: box
=-09999999999999999999999999999999 - running off to the right hand
side of the login window (outside the Login: input field).
ctrl-alt-backspace won't work either.

However, disabling the automatic launch in Xservers
    - 0: local /usr/bin/X :0 vt7 -nolisten tcp
    + #0: local /usr/bin/X :0 vt7 -nolisten tcp
and enabling remote logins in xdm-config
    - DisplayManager.requestPort:    0
    + !DisplayManager.requestPort:    0
    # /etc/init,d.xdm restart
and starting the session from the command line
    $ X -query localhost
works perfectly, as does "startx".

I've tried purging xdm and reinstalling it, to eliminate old config
issues - no change.
The same thing happens if I change the ati driver for the fbdev driver.

The X server is normally idle but sometimes goes to consuming 100% CPU
if I press random keys. The 100% CPU consumption can erliably be
provoked by pressing digit 3 key - ther seems to be no other single
key that reliably provokes this behaviour.
There is no extra output in /var/log/Xorg.log.0 during this behaviour.

Killing the X server at this point usually makes xdm restart -
occasionally it leaves a black background with many white vertical
lines and hangs the console. In this case, Xorg.log.0 says:
(WW) xf86CloseConsole: KDSETMODE failed: Input/output error
(WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
(WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
(WW) xf86CloseConsole: VT_WAITACTIVE failed: Input/output error
but normality can be regained by issuing /etc/init.d/xdm restart

Looks like a corrupt pointer in xdm's input section when dealing with
the console directly. Any other diagnostics I can give you?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to