Re: Issue 200 in xmonad: xmonad spins in a tight loop changing focus back and forth

Comment #11 on issue 200 by wapcaplet88: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 Same issue here, on Gentoo with xmonad-0.9 and openoffice-bin-3.2.0. Adding 'export SAL_USE_VCLPLUGIN=gen' to ~/.xsession worked a treat!

Comment #12 on issue 200 by girard.cedric: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 Is this really an Xmonad bug or should this be reported on LibreOffice bug tracker (or OOo one) ?

Comment #13 on issue 200 by dunric29a: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 girard.cedric> Nope, this is _not_ a Xmonad issue but the stupid OpenOffice.org behaviour when it tries supply improper desktop handling of some common used window managers. OO has same or similar problems with other tiling window managers like Stumpwm or wmii. What would be next OO's next feature ? Filesystem defragmentation or procesess scheduler ?!

Comment #14 on issue 200 by konstant...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 getting the same behaviour with Pandora client after the recent Adobe Air update. doIgnore "helps".

Comment #15 on issue 200 by mesz...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 Using XMonad.Hooks.EwmhDesktops fixes this issue for me (setup according to http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-EwmhDesktops.html). I'm running xmonad 0.9.2 and libreoffice 3.4.3.

Comment #16 on issue 200 by alex.hen...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 I can confirm like http://code.google.com/p/xmonad/issues/detail?id=200#c15 that with xmonad 0.10 and libreoffice 3.5.4.2 enabling emwh helps eliminate the floating dialog flicker loop in LibreOffice. I used to get a 10 - 15 second loop, now it's just a flicker or two, and I can keep working.

Comment #17 on issue 200 by allber...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 Could someone try setting borderWidth to 0? We just had someone see something similar from Steam for Linux and the problem was revealed by xscope to be that their window placement code didn't support server-side window borders, so it got confused about where the dialog was relative to the root window and tried to "fix" it by closing and reopening it.

Comment #18 on issue 200 by ptr...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 tried it with borderWidth = 0 --> Problem solved! However, i need some form of border...so this is not very handy. -- 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 #19 on issue 200 by allber...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 Right, I wasn't suggesting that as a solution, just as a way to try to diagnose what's going on. Unfortunately, this means it's likely a bug in LibreOffice. Although, does using EwmhDesktops help as specified by others here? Alternately, as an ugly workaround it might be possible to identify just the LibreOffice dialog windows in the ManageHook and only force those windows' borders to 0. Something like (note, I don't have any idea if this will actually match LibreOffice dialogs, it's just an example) className =? "LibreOffice" <&&> stringProperty "WM_WINDOW_ROLE" =? "dialog" --> ask >>= \w -> liftX (withDisplay $ \d -> setWindowBorder d w 0) <+> idHook -- 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 #20 on issue 200 by cpscha...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 The provided code does not work, 'setWindowBorder :: Display -> Window -> Pixel -> IO ()' , not -> X (Endo StackSet). Even mixing in 'io' to convert to 'X ()' doesn't fully fix it. For example this doesn't work: -- really is: 'doRemoveBorders :: Query ()' doRemoveBorders :: Query (Endo WindowSet) doRemoveBorders = ask >>= \w -> liftX . withDisplay $ \d -> io $ setWindowBorder d w 0 That said, using ewmh as recommended appears to fix it entirely. -- 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 #21 on issue 200 by collinst...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 I can also confirm that the workaround posted in http://code.google.com/p/xmonad/issues/detail?id=200#c15 helps. It does not prevent flicker, but prevents the entire system from becoming unusable and unresponsive. LibreOffice is not the only program that this is an issue with. I encountered it both with LibreOffice dialog boxes, and with dialog boxes from a VLSI CAD software suite by a company called Cadence. -- 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 #22 on issue 200 by dan.krejsa@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 I've seen very similar behavior using the emacs 'ediff' diff/merge tool, if I try to make the ediff control window a floating window. xmonad 0.11 emacs 24.3.1 On Arch linux. I'll try some of the suggestions... -- 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 #23 on issue 200 by dan.krejsa@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 OK, enabling XMonad.Hooks.EwmhDesktops does NOT appear to affect the case with emacs ediff for me. -- 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 #24 on issue 200 by allber...@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 No, it won't affect ediff, that's one of many frame-related bugs in emacs. Emacs likes to think it gets to decide things like focus (this hasn't been true or legal since X11R4), so when the window manager sets the focus emacs decides it wants another frame to have focus instead and moves it. Most window managers don't pay attention to emacs forcibly setting focus, xmonad is being strict about ICCCM/EWMH and switching focus back. It's the equivalent of Chrome and Firefox switching focus around, except they use EWMH to tell the window manager to do it instead of just slamming it themselves and if you hack EWMH to ignore the focus change message you can override it. (I have managed to provoke all kinds of weird behavior from emacs' frame support. Speedbar is another good way to do it; if you try to capture it in an IM layout, it will constantly escape the layout. I gave up, as the emacs folks don't appear to have any intention of following ICCCM or EWMH.) -- 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 #25 on issue 200 by dan.krejsa@gmail.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 Thanks alber..., I'll work around the emacs issue. Not being knowlegeable about X topics I looked up the Wikipedia article on ICCCM and was amused by a couple of the references ;-) -- 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 #26 on issue 200 by nicolas....@b2ck.com: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 Hello, I'd like to add my comment on this bug because it also affects me. It usually happens with firefox but it can also happens with urxvt. I have tried the EWMH solution without much success. Since firefox is launched on a workspace that is configured with noBorders I did not try the 0-border size solution. The bug manifest itself by spinning between two windows, I break this loop by pressing again the key combination to switch to another window. Then in that case sometimes the focus is on the displayed window (I am using a Tabbed Simplest layout) sometimes on the other window. One way I have found to reset everything to the normal state is to create a new firefox window and then closing it. I am using xmonad 0.11 on a debian sid box (all packages comes from the standard repository). I have attached my xmonad.hs configuration ... Let me know if I can be of any help. Attachments: xmonad.hs 3.8 KB -- 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