Stuck inside a window - this happen to anyone else?

This is just a complete shot-in-the-dark bug report, to see if anyone else has experienced similar symptoms. I don't imply that the following problem has anything to do with xmonad, though it would seem the prime suspect. Earlier today I was working in Firefox with a bunch of other windows open on screen, a bunch of other workspaces populated too. FF was working fine, but everything I tried to do *outside* of the browser didn't work. I couldn't mouse over other windows to give them focus. I couldn't switch to other workspaces. I couldn't move the focussed window around with mod-shift-j/k or choose a new master. I couldn't mod-q to restart, though I managed to switch to another virtual terminal and back (ctrl-alt-Fn) so the keyboard seems to have been responsive. If I'd been thinking at the time I would have tried to open another window from within Firefox to see what it would do. In the end I killed xmonad from the other VT and it all worked out fine. Has this ever happened to you? And secondarily, is there a way to mod-q Xmonad through a kill sig? Does it recognise SIGHUP? Cheers, D. -- Dougal Stanton dougal@dougalstanton.net // http://www.dougalstanton.net

On Dec 14, 2007 11:23 AM, Dougal Stanton
This is just a complete shot-in-the-dark bug report, to see if anyone else has experienced similar symptoms. I don't imply that the following problem has anything to do with xmonad, though it would seem the prime suspect.
Earlier today I was working in Firefox with a bunch of other windows open on screen, a bunch of other workspaces populated too. FF was working fine, but everything I tried to do *outside* of the browser didn't work. I couldn't mouse over other windows to give them focus. I couldn't switch to other workspaces. I couldn't move the focussed window around with mod-shift-j/k or choose a new master.
I couldn't mod-q to restart, though I managed to switch to another virtual terminal and back (ctrl-alt-Fn) so the keyboard seems to have been responsive. If I'd been thinking at the time I would have tried to open another window from within Firefox to see what it would do. In the end I killed xmonad from the other VT and it all worked out fine.
Has this ever happened to you? And secondarily, is there a way to mod-q Xmonad through a kill sig? Does it recognise SIGHUP?
Cheers,
D.
That sounds like something I've experienced. Firefox still responded to the keyboard and mouse, right? Next time it happens, try opening another window from within firefox -- when I've experienced this sort of thing, opening another window has fixed the problem. Very strange, at any rate... -Brent

On 14/12/2007, Brent Yorgey
That sounds like something I've experienced. Firefox still responded to the keyboard and mouse, right? Next time it happens, try opening another window from within firefox -- when I've experienced this sort of thing, opening another window has fixed the problem. Very strange, at any rate...
Yep, that's exactly it. If I did it over I would have put a bit more thought into diagnosis, but I was trying to get back to what I was actually doing. I've only just upgraded to xmonad 0.5 so it may happen frequently. Or maybe it was a total freak and it won't happen again for weeks or months? D. -- Dougal Stanton dougal@dougalstanton.net // http://www.dougalstanton.net

ithika:
On 14/12/2007, Brent Yorgey
wrote: That sounds like something I've experienced. Firefox still responded to the keyboard and mouse, right? Next time it happens, try opening another window from within firefox -- when I've experienced this sort of thing, opening another window has fixed the problem. Very strange, at any rate...
Yep, that's exactly it. If I did it over I would have put a bit more thought into diagnosis, but I was trying to get back to what I was actually doing.
I've only just upgraded to xmonad 0.5 so it may happen frequently. Or maybe it was a total freak and it won't happen again for weeks or months?
If it happens again, consider upgrading to the darcs version, and X11 1.4.1. Two rare bugs have been fixed, possibly related (or not). That would at least let us rule out something that might have been fixed. -- Don

On 14/12/2007, Don Stewart
If it happens again, consider upgrading to the darcs version, and X11 1.4.1. Two rare bugs have been fixed, possibly related (or not).
That would at least let us rule out something that might have been fixed.
It just happened to me again so I've upgraded to the latest X11/Xmonad. We'll see what happens. I was in a terminal window this time, so I tried a few more things to see what would happen. - opening a new terminal had no effect. The program launched (at least, my CPU usage spiked) but no new window appeared. I ctrl-c'ed and my prompt re-appeared in the current window. - the mouse pointer still changes shape as it moves across different windows, and I can still highlight by click-dragging in other terminal windows. Can't move focus to them though. D. -- Dougal Stanton dougal@dougalstanton.net // http://www.dougalstanton.net
participants (3)
-
Brent Yorgey
-
Don Stewart
-
Dougal Stanton