Issue 413 in xmonad: Windows don't disappear
Status: New Owner: ---- New issue 413 by srburnet: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 What steps will reproduce the problem? 1. Open a window (e.g., a terminal, although it happens to all types of windows) 2. Do a bunch of other work with other windows. (This doesn't happen if you open and close a window immediately). 3. Close the original window. What is the expected output? What do you see instead? The window should disappear and the wallpaper should be shown. Instead, an artifact image of the window remains, although the window itself has definitely closed. I can't interact with the window and if open a new window xmonad behaves as if there is no additional window (the screen isn't split between the two windows). I can even drag a small window around in tiling mode over the image of the window and "erase" the closed window (i.e., the wallpaper is redrawn in areas touched by the window). I've attached a screenshot that hopefully makes sense. Note that the problem is very rare. There doesn't seem to be a pattern for which windows have the problem. What version of the product are you using? On what operating system? xmonad darcs, on Arch Linux. I am using the NVIDIA proprietary drivers with dual monitors (Twinview). I am not using compositing. The problem has occured with multiple versions of xmonad, the kernel versions, and the NVIDIA driver. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". xmonad --recompile yields no output. Attachments: xmonad.hs 5.2 KB bug.png 741 KB
Comment #1 on issue 413 by allbery.b: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 Sounds to me like the root window isn't processing Expose events properly. How are you setting the background? (Some setters only behave correctly when used with a window manager that redraws the root window itself using a cached copy of the background; not all window managers understood this protocol, and it's mostly obsolete these days.)
Comment #2 on issue 413 by srburnet: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 I'm using feh to set the background. I also tried xloadimage and have the same problem. What image setter do you recommend? I don't have Gnome or KDE installed, so something lightweight would be nice.
Comment #3 on issue 413 by srburnet: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 Some more information: I also tried setting a static background color with 'xsetroot -solid black' and still get the same problem. hsetroot doesn't work either.
Comment #4 on issue 413 by norbert.zeh: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 I ran into the same problem just now. Same setup: xmonad darcs, arch linux, feh for setting the background, NVIDIA dual screen. The caveats on the background actually looked like *parts* of me emacs window, each with nicely rounded corners. Really strange. Since I never had this problem using Debian on the same hardware before, nor using arch on a single screen with an ATI graphics card, I am inclined to think that this is not an xmonad issue and maybe blame the new X server in arch, the bleeding edge NVIDIA driver or something like that. I may of course be completely off with this guess and would still like to know what causes this behaviour and how to fix it.
Comment #5 on issue 413 by srburnet: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 Interesting. I neglected to mention that I sometimes get a stranger behavior. Suppose I have desktop with two windows and have the screen split so both windows are shown side by side (e.g., with the "Tall" layout). Then sometimes when I switch to an empty desktop, only one of the windows disappears; the other one is left on the display (but is not actually "there", since I cannot interact with it). Does xmonad do some weird things when it unmaps windows? Or perhaps this is in fact an NVIDIA issue. I'll note that I've had this problem for a long while now, with multiple driver versions.
Comment #6 on issue 413 by norbert.zeh: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 @srburnet: Do you have a way to consistently reproduce this issue? When I posted, it was the first time I ran into it, and 10 minutes of tinkering right after did not show any success in reproducing it. If we want to debug this, we need a test case.
Comment #7 on issue 413 by srburnet: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 Unfortunately, the behavior looks pretty random to me. If I find a way to reproduce it, I'll definitely post it. Are there any log files, memory dumps, diagnostics, etc. that could shed some light on this?
Comment #8 on issue 413 by ahanw...@storvisor.com: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 Seeing the same issue. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
Comment #9 on issue 413 by allber...@gmail.com: Windows don't disappear http://code.google.com/p/xmonad/issues/detail?id=413 ahanwadi, if you're seeing it now (note the original ticket is from 2010) you are seeing a known bug with the current NVidia drivers in Arch, introduced about a month and a half ago, and the workaround is to run a compositing manager. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
participants (1)
-
codesite-noreply＠google.com