Bug 103863

Created attachment 45567 [details]
output from hwinfo

Created attachment 45568 [details]
part of /var/log/messages file

is it reproducable? do you see further interrupts when you press keys?
watch -n1 cat /proc/interrupts

I can't reproduce this hangup. If that will happen again, I'll check the interrupts.

I have *the same* problem. 
 
However, my keyboard stops responding mostly when working with KDE-Yast 
modules. 
For example when I want to search for new software in Yast Install; 
 
My keyboard: 
Genius Multimedia KB-18, PS/2 keyboard  
 
However, when I move to other window (i.e. KWrite) it restores. 
 
Is my behavior is similar to yours ? 
 
Or your keyboard, after hangs is not working under *any* app ? 

In order to restore my keyboard to working state in Suse-Yast, I needed to 
open any application in 2nd Desktop (in KDE pager), click to focus on it,  
the get back to Desktop 1 and Focus on SuSE-Yast. 
 
If I by mistake focus on different app, the keyboard will be non-functional in 
Yast -Again. 

(In reply to comment #5)
> Is my behavior is similar to yours ? 
>  
> Or your keyboard, after hangs is not working under *any* app ? 
No, my keyboard stops working at all. I'm not using KDE but Windowmaker.

I had that too here, on an ibook. I was able to c&p a 'chvt 1' into a root
shell, kbd worked on the console. But not when switching back to X. Everything
was ok after reboot. Odd, I was able to login via kdm before it happend. Looks
like somehow X loses the keyboard. 

Egbert, any ideas where X does read from the keyboard?

> For example when I want to search for new software in Yast Install; 
I have seen this too. It's a toolkit problem. Has nothing to do with keyboard
data not being sent to X any more.
> had that too here, on an ibook. I was able to c&p a 'chvt 1' into a root
> shell, kbd worked on the console. But not when switching back to X. Everything
> was ok after reboot. Odd, I was able to login via kdm before it happend. Looks
> like somehow X loses the keyboard. 
This may or may not be related to the original problem.
> Egbert, any ideas where X does read from the keyboard?
Yes. Basically you can run strace and see if select returns of you press a key.
A look at /proc/<server-pid>/fd should also tell you which file handle your
keyboard device is.

Any news here?

I havent seen it since then.

So do I. I have already Beta 3 and it's OK.

Really.
 I can't reproduce that with BETA 3.

ok, reopen if it happens again.

Created attachment 98763 [details]
Configuration file when keyboard/mouse don't respond.

I just created an attachment (see last comment) but my explanation was lost! I'm reopening this bug because it fits my symptoms so nicely. I hope that I'm adding useful informatin but apologize if I'm not following protocol.

I've seen this same problem on SLES 10 prior to GMC (final release) and SLED 10 GMC, under similar cirumstances,  four times in the last 5 weeks, always associated with changes to VNC. I'm not sure that it is 100% reproducible but there seems to be a high probablity that playing with VNC will cause the problem

I just installed SLED 10 GMC.  I enabled VNC during installation.  After the install I used YAST->network services->network services (xinted) to enable all 6 of the VNC options:  vnc1, vnc2, vnc3, httpvnc1... etc.  (Enabling vnc during install or using remoted admin only seems to configure vnc1.) On reboot the mouse and keyboard are not responding at the GUI login:  caps lock detected, alt-ctrl-f1, etc. work, but it doesn't respond to typing a user name or moving the mouse.   When I saw this problem on SLES 10 the helpdesk Linux guru examined the file and said xorg.conf was fouled up, so I included the file from this SLED 10 system while it was in a broken state.

Please file a new X11 bug, your symptoms differ.