Issue 371 in xmonad: Program using popup menus can freeze the desktop
Status: New Owner: ---- New issue 371 by facundominguez: Program using popup menus can freeze the desktop http://code.google.com/p/xmonad/issues/detail?id=371 > What steps will reproduce the problem? 1. Compile and run the attached Java program. javac Grab.java java Grab > What is the expected output? What do you see instead? The expected output is that I should be able to use the other desktop applications while this application is running. What I see instead, is that none of the windows reacts to mouse clicks or keyboard events until the running java program is killed. > What version of the product are you using? On what operating system? I'm using xmonad 0.9.1 and java 1.6.0.12 Debian Lenny Linux 2.6.26-2-686 #1 SMP Sat Dec 26 09:01:51 UTC 2009 i686 GNU/Linux > Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". The output of "xmonad --recompile" is empty. Find attached xmonad.hs > Please provide any additional information below. This bug is very annoying when developing java applications that for any accidental bug freeze without closing all its open popup menus. Attachments: Grab.java 1.1 KB xmonad.hs 13.8 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #1 on issue 371 by daniel.wagner: Program using popup menus can freeze the desktop http://code.google.com/p/xmonad/issues/detail?id=371 Have you tried this under other WMs (with the same toolkit, environment variables, etc.)? This sounds an awful lot like your app is doing an active grab and not releasing it, which can't really be blamed on xmonad. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #2 on issue 371 by hgabreu: Program using popup menus can freeze the desktop http://code.google.com/p/xmonad/issues/detail?id=371 I can reproduce this problem. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #3 on issue 371 by facundominguez: Program using popup menus can freeze the desktop http://code.google.com/p/xmonad/issues/detail?id=371
Have you tried this under other WMs (with the same toolkit, environment variables, etc.)? This sounds an awful lot like your app is doing an active grab and not releasing it, which can't really be blamed on xmonad.
I have tested the application with metacity, and the same happens. But I do not understand if that frees xmonad from all possible responsibility. Is it mandatory to give focus to user applications when they request it, despite of the fact that the user may not want that? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #4 on issue 371 by daniel.wagner: Program using popup menus can freeze the desktop http://code.google.com/p/xmonad/issues/detail?id=371 The way I understand it, it's not just mandatory -- there is literally no choice. The request goes straight to the X server, with no WM intervention at all. ...but IANA X expert -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Updates: Status: Invalid Comment #5 on issue 371 by SpencerJanssen: Program using popup menus can freeze the desktop http://code.google.com/p/xmonad/issues/detail?id=371 As others have indicated, this is a fundamental issue in the X11 protocol. There is nothing a WM can or should do to work around it. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
participants (1)
-
codesite-noreply＠google.com