Keyboard and mouse dying
Hi, When using xmonad, sometimes my mouse and keyboard stop answering, to the point that I have to reboot the computer. Does anyone had the same experience? I first thought that it could be a hardware problem, but when I use gnome nothing wrong happens. Here is my .xmonad.hs: ----- import XMonad import XMonad.Layout.Grid main = xmonad $ defaultConfig {borderWidth=11, modMask=mod4Mask, normalBorderColor="#00ff00", focusFollowsMouse=False, layoutHook =((Tall 0 (1/100) (1/2)) ||| (Tall 1 (1/100) (9/10)))} ----- Thanks, Maurício
On Tue, Jul 08, 2008 at 11:13:08AM -0300, Maur??cio wrote:
When using xmonad, sometimes my mouse and keyboard stop answering, to the point that I have to reboot the computer.
Hrm, that's bad. I haven't had that happen since around 0.3. One thing that caused problems was hitting mod-q while a child process (e.g. a spawned dzen) was running. I'm not sure how to debug this -- perhaps there is relevant info in your Xorg log or in the stdout/stderr of xmonad? (You may need to capture it in your xinitrc.) When you say they stop answering, does the mouse cursor actually freeze, or does xmonad just stop moving the red border based on it? Perhaps make a keybinding that does nothing but putStrLn "hello!" and see if that works? (Perhaps it's the graphics driver that's freezing and not the input drivers.) Obviously if you can narrow down the context, that'd be good.
When using xmonad, sometimes my mouse and keyboard stop answering, to the point that I have to reboot the computer.
Hrm, that's bad. I haven't had that happen since around 0.3. One thing that caused problems was hitting mod-q while a child process (e.g. a spawned dzen) was running.
I'm not sure how to debug this -- perhaps there is relevant info in your Xorg log or in the stdout/stderr of xmonad? (You may need to capture it in your xinitrc.)
When you say they stop answering, does the mouse cursor actually freeze, or does xmonad just stop moving the red border based on it? Perhaps make a keybinding that does nothing but putStrLn "hello!" and see if that works? (Perhaps it's the graphics driver that's freezing and not the input drivers.)
Obviously if you can narrow down the context, that'd be good.
xmonad package is version 0.6-3 in Ubuntu latest version. I made a mistake about the mouse: I actually do not have a mouse, and use an X feature to control the mouse from the keypad; so, maybe it's just the keyboard freezing. (I also have a problem with that in xmonad, since usually the keyboard stops its control over the mouse until I restart that feature with Alt-Shift-NumLock. But that is on another thread.) I'll use xmonad again and as soon as my computer freezes I'll post the previous Xlog file here. Maurício
The last question in the xmonad FAQ deals with keyboard lockups. Some applications grab the keyboard and fail to release the grab (I find that VLC does fairly often after watching a fullscreen video).
lithis a écrit :
The last question in the xmonad FAQ deals with keyboard lockups. Some applications grab the keyboard and fail to release the grab (I find that VLC does fairly often after watching a fullscreen video).
Can an application grab the keyboard to the point that I can't use Control-Alt-Backspace? Sorry for asking, but I prefer to try everything before changing my X configuration. Maurício
On 2008.07.08 16:55:04 -0300, Maurício
lithis a écrit :
The last question in the xmonad FAQ deals with keyboard lockups. Some applications grab the keyboard and fail to release the grab (I find that VLC does fairly often after watching a fullscreen video).
Can an application grab the keyboard to the point that I can't use Control-Alt-Backspace? Sorry for asking, but I prefer to try everything before changing my X configuration.
Maurício
I think that is possible; I would swear Firefox and a Urxvt extension (which both seem to call the XGrabAllKeys function or whatever was the problematic one) have both locked up my X in the past such that while the mouse moved around fluidly and fine (indicating no systemic problems), all keypresses including C-M-Backspace were ignored. -- gwern Security 17 speech nkvd CACI ARC SASR FTS2000 Security Ionosphere
* On Tuesday, July 08 2008, Maurício wrote:
Can an application grab the keyboard to the point that I can't use Control-Alt-Backspace? Sorry for asking, but I prefer to try everything before changing my X configuration. You could also try using that magic sysRq to kill X and/or restart without risking filesystem and hardware damage: http://en.wikipedia.org/wiki/Magic_sysrq
On Tue, Jul 08, 2008 at 04:55:04PM -0300, Maurício wrote:
lithis a écrit :
The last question in the xmonad FAQ deals with keyboard lockups. Some applications grab the keyboard and fail to release the grab (I find that VLC does fairly often after watching a fullscreen video).
Can an application grab the keyboard to the point that I can't use Control-Alt-Backspace? Sorry for asking, but I prefer to try everything before changing my X configuration.
Maurício
Yes, an application can prevent ctrl-alt-backspace. What I generally do is alt-sysrq-r (puts the keyboard in raw mode), then ctrl-alt-F1 to switch to a virtual terminal and fix things from there. Cheers, Spencer Janssen
On Tue, Jul 08, 2008 at 03:39:20PM -0300, Maurício wrote:
When using xmonad, sometimes my mouse and keyboard stop answering, to the point that I have to reboot the computer.
Hrm, that's bad. I haven't had that happen since around 0.3. One thing that caused problems was hitting mod-q while a child process (e.g. a spawned dzen) was running.
I'm not sure how to debug this -- perhaps there is relevant info in your Xorg log or in the stdout/stderr of xmonad? (You may need to capture it in your xinitrc.)
When you say they stop answering, does the mouse cursor actually freeze, or does xmonad just stop moving the red border based on it? Perhaps make a keybinding that does nothing but putStrLn "hello!" and see if that works? (Perhaps it's the graphics driver that's freezing and not the input drivers.)
Obviously if you can narrow down the context, that'd be good.
xmonad package is version 0.6-3 in Ubuntu latest version. I made a mistake about the mouse: I actually do not have a mouse, and use an X feature to control the mouse from the keypad; so, maybe it's just the keyboard freezing. (I also have a problem with that in xmonad, since usually the keyboard stops its control over the mouse until I restart that feature with Alt-Shift-NumLock. But that is on another thread.)
I'll use xmonad again and as soon as my computer freezes I'll post the previous Xlog file here.
Maurício
I think X11's mouse-via-keyboard feature may be slightly broken. I know that I experienced numerous keyboard lockouts when using it. Cheers, Spencer Janssen
Maurício
I think X11's mouse-via-keyboard feature may be slightly broken. I know that I experienced numerous keyboard lockouts when using it.
Cheers, Spencer Janssen
I only have problems when using xmonad (although, of course, that doesn't mean it's xmonad's fault). But that Alt-SysRq tip from you and Adam is really great, I've tested it and it really does the trick. If I use Alt-SysRq-r and Ctrl-Alt-F1, is it possible to check which program is grabbing the keyboard in X, and kill only that program? Maurício
participants (6)
-
Adam Vogt -
Devin Mullins -
Gwern Branwen -
lithis -
Maurício -
Spencer Janssen