Issue 515 in xmonad: XMonad freezes occasionally when using Gridselect (XMonadContrib)
Status: New Owner: ---- New issue 515 by bmathiasen: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 What steps will reproduce the problem? 1. Toggling Gridselect (goToSelected/gridselectWorkspace) 2. Attempt to move to another window or workspace. What is the expected output? What do you see instead? Expected output: Normal 2D grid of windows/workspaces, that I can swap to using the keyboard. What I see: The 2D grid opens, but any subsequent input from the keyboard will occasionally cause XMonad to freeze; windows and workspaces will become unresponsive. It is possible to go to another tty to kill xmonad, after which a WM can be launched on the appropriate display. What version of the product are you using? On what operating system? XMonad version 0.10 (built from source, package manager, and Cabal) on the following OS's: - LinuxMint (DebianTesting edition) using XFCE4. - Xubuntu (11.10 and 12.04). - Ubuntu (12.04). All setups tried on two separate laptops, Lenovo Thinkpad X220 and T400s. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". No output. Please provide any additional information below. My xmonad.hs uses custom functions for gridselecting windows and workspaces, but the same error occur with the default configuration. Upon freeze, there is no relevant error logging output in /var/log/messages, ~/.Xsession-errors or ~/.xmonad/xmonad.errors. Attachments: xmonad.hs 8.9 KB
Comment #1 on issue 515 by daniel.w...@gmail.com: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 Have you had a look at http://www.haskell.org/haskellwiki/Xmonad/Frequently_asked_questions#XMonad_... yet?
Comment #2 on issue 515 by bmathiasen: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 Except for the 'xclock'-method, I've tried (and failed) the other methods, excluding xmobar/statusbar as I don't use those. I'll try 'xclock'-method, and post any updates as soon as I get them.
Comment #3 on issue 515 by bmathiasen: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 xclock didn't help.
Comment #4 on issue 515 by thomas.a...@gmail.com: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 It won't help you. The problem is obvious. When the GridSelect windows are displayed, the XServer is grabbed, presumably for the keyboard input although I've not checked the exact reasons why the XServer is grabbed in this case.
Comment #5 on issue 515 by bmathiasen: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 If that is the case, surely every user of Gridselect should experience this?
Comment #6 on issue 515 by allber...@gmail.com: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 You won't see it 100% consistently; even the infamous putSelect wasn't 100% consistent. I just went through the GridSelect code. There is no full server grab; the keyboard and one mouse button are grabbed, though. Beyond this, the issue is that xmonad is not processing events in its main loop, and this means (a) it cannot do things like switching workspaces; (b) events that GridSelect does not expect are simply dropped, meaning: (c) new windows will completely fail to do the window management process; (d) other potentially important X11 events and negotiations are dropped on the floor. Which means that there are a number of ways that GridSelect can lead to gridlock with either clients or the X11 server. If you pick your selection quickly, you likely won't notice; the longer GridSelect stays up, and the more things that happen while it's up, the more likely that xmonad will drop/ignore something critical.
Comment #7 on issue 515 by bmathiasen: XMonad freezes occasionally when
using Gridselect (XMonadContrib)
http://code.google.com/p/xmonad/issues/detail?id=515
Thanks for the elaborate response.
Just to bring a status update: XMonad doesn't seem to freeze on Arch (hope
i don't jinx it ;). Both systems have xmonad/+contrib installed through
cabal and run identical xmonad.hs.
Here's some output from 'X -version' on my two currently running systems,
in case it makes any difference:
Mint (debian) 'X -version':
X.Org X Server 1.12.1.902 (1.12.2 RC 2)
Release Date: 2012-05-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-2-amd64 x86_64 Debian
Current Operating System: Linux none 3.2.0-3-amd64 #1 SMP Thu Jun 28
09:07:26 UTC 2012 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64
root=UUID=6cdaef22-3035-4c99-af66-553e95dcd62e ro quiet
Build Date: 20 May 2012 08:57:17AM
xorg-server 2:1.12.1.902-1 (Cyril Brulebois
Comment #8 on issue 515 by bmathiasen: XMonad freezes occasionally when using Gridselect (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=515 Nevermind, that was a false positive. Freezing still occurs. I'll attempt stracing the process.
participants (1)
-
codesite-noreply＠google.com