- xmonad - Haskell.org

Issue 192 in xmonad: doesn't check for existing window manager
by codesite-noreply＠google.com 26 May '08

26 May '08

Issue 192: doesn't check for existing window manager http://code.google.com/p/xmonad/issues/detail?id=192 New issue report by t.lainson: What steps will reproduce the problem? 1. Run any reparenting window manager 2. Launch xmonad while the other WM is still running What is the expected output? "xmonad: fatal: a window manager is already running" What do you see instead? Lots of X11 BadAccess errors, and two window managers trying to run at once. Haven't checked whether it's been fixed since 0.7 was released. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

1 0

Issue 190 in xmonad: FF3 steals focus
by codesite-noreply＠google.com 26 May '08

26 May '08

Issue 190: FF3 steals focus http://code.google.com/p/xmonad/issues/detail?id=190 Comment #3 by dons00: Great news. Can you sumarise details of the problem and the fix on the FAQ: http://haskell.org/haskellwiki/Xmonad/Frequently_asked_questions -- 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

1 0

Issue 190 in xmonad: FF3 steals focus
by codesite-noreply＠google.com 26 May '08

26 May '08

Issue 190: FF3 steals focus http://code.google.com/p/xmonad/issues/detail?id=190 Comment #2 by curolan.zebeth: While I'd still like to see this fixed on the xmonad side, I now know how to change the behavior in firefox: simply set browser.tabs.loadDivertedInBackground to "true". As far as I'm concerned, the priority of this bug just dropped a lot. :-) -- 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

1 0

Issue 189 in xmonad: MultiToggle to Full and tabbed layout makes X crusn
by codesite-noreply＠google.com 25 May '08

25 May '08

Issue 189: MultiToggle to Full and tabbed layout makes X crusn http://code.google.com/p/xmonad/issues/detail?id=189 Comment #1 by curolan.zebeth: I can reproduce this. xmonad segfaults immediately. Here's what gdb says: #0 0x08282056 in ?? () #1 0x4f004137 in _XlcResetConverter () from /usr/lib/libX11.so.6 #2 0x4f0311e3 in _XomInitConverter () from /usr/lib/libX11.so.6 #3 0x4f02dbe6 in ?? () from /usr/lib/libX11.so.6 #4 0x08278250 in ?? () #5 0x00000001 in ?? () And here are the last lines of an ltrace log: XNextEvent(0x8271818, 0xb7e7e158, 0, 0, 0) = 0 __errno_location() = 0xb7f6b688 XInternAtom(0x8271818, 0xb7e64098, 0, 0, 0) = 257 XGetTextProperty(0x8271818, 0x1800006, 0xb7e640b0, 257, 0 <unfinished ...> SYS_write(3, "\024", 24) = 24 SYS_read(3, "\001\b\007\007\002", 32) = 32 SYS_readv(3, 0xbfe8cfe4, 2, 0xbfe8cfe4, 0x41779ff4) = 8 <... XGetTextProperty resumed> ) = 1 XwcTextPropertyToTextList(0x8271818, 0xb7e640e8, 0xb7e640c8, 0xb7e640d8, 0) = 0 XwcFreeStringList(0x8277b98, 0, 0, 0, 0) = 0x8277c80 XFree(0x8278228, 0, 0, 0, 0) = 1 XwcTextEscapement(0x8281210, 0xb7e64100, 5, 0, 0 <unfinished ...> --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ Unfortunately I have no idea how tabbed works, so I'm a bit clueless as to what's going wrong here. -- 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

1 0

Issue 190 in xmonad: FF3 steals focus
by codesite-noreply＠google.com 25 May '08

25 May '08

Issue 190: FF3 steals focus http://code.google.com/p/xmonad/issues/detail?id=190 Comment #1 by vogt.adam: This looks like (my) issue: #139, which may have been with an earlier ff beta... I see this one too, but it's only a minor annoyance. -- 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

1 0

Issue 191 in xmonad: Mirror makes hint-respecting layouts misbehave
by codesite-noreply＠google.com 25 May '08

25 May '08

Issue 191: Mirror makes hint-respecting layouts misbehave http://code.google.com/p/xmonad/issues/detail?id=191 Comment #1 by curolan.zebeth: A possible solution can be found in <http://www.haskell.org/pipermail/xmonad/2008-May/005651.html>. -- 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

1 0

Issue 191 in xmonad: Mirror makes hint-respecting layouts misbehave
by codesite-noreply＠google.com 25 May '08

25 May '08

Issue 191: Mirror makes hint-respecting layouts misbehave http://code.google.com/p/xmonad/issues/detail?id=191 New issue report by curolan.zebeth: What steps will reproduce the problem? 1. set your layoutHook to something like Mirror (HintedTile ...) 2. open mplayer and tile it 3. What is the expected output? What do you see instead? I expect mplayer to get a window that respects its size hints. Instead, it appears weirdly distorted because Mirror swaps x and y coordinates before calling HintedTile and "unswaps" them again in the coordinates returned from HintedTile. This works for "normal" layouts, but HintedTile calls mkAdjust to apply size hints to its windows. The result is that windows get their preferred height as width and vice versa. This happens for any hint-respecting layout under Mirror. What version of the product are you using? On what operating system? xmonad-darcs, xmonad-contrib-darcs, gentoo linux. Please provide any additional information below. To fix this issue, mkAdjust would need to magically know whether it was called from a context in which the coordinate system was transformed somehow. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

1 0

Issue 190 in xmonad: FF3 steals focus
by codesite-noreply＠google.com 25 May '08

25 May '08

Issue 190: FF3 steals focus http://code.google.com/p/xmonad/issues/detail?id=190 New issue report by curolan.zebeth: What steps will reproduce the problem? 1. have firefox 3RC1 open 2. type 'firefox http://google.com/' in a terminal (on the same workspace) 3. What is the expected output? What do you see instead? I expect firefox to open google in a new tab (this happens). However, the new tab gets keyboard focus without xmonad noticing, i.e. the red border is still on urxvt but keypresses go to firefox (urxvt itself knows what happened because the cursor becomes hollow). If the mouse pointer was previously on firefox, moving it over urxvt has no effect because xmonad thinks urxvt already had the focus. Similarly for clicking on it. To fix the confusion you have to explicitly move the focus to another window (such as firefox or a third application) and back to urxvt. What version of the product are you using? On what operating system? xmonad-darcs, xmonad-contrib-darcs, compiled manually on gentoo linux. Please provide any additional information below. This may be a bug in firefox (no idea), but can't xmonad notice what's going on somehow? If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

1 0

why dose not my urgency hook work?
by Changying Li 24 May '08

24 May '08

hi. I want to let something flash when the hidden desktop or window demands my attention. so I tried urgency hook. But it didnt work. its my configure: statusBarCmd= "dzen2 -bg '#1a1a1a' -fg '#777777' -h 16 -w 600 -sa c -e '' -fn '-*-courier-*-r-normal-*-*-120-*-*-*-*-iso8859-*' -ta l" main = do din <- spawnPipe statusBarCmd xmonad $ withUrgencyHook dzenUrgencyHook { args = ["-bg", "yellow", "-xs", "1"] } $ defaults { logHook = dynamicLogWithPP $ dzenPP { ppOutput = hPutStrLn din } } and when I use dynamicLogDzen directy , the dzen showed nothing, but when I use dzenPP it worked. btw, I'm using archlinux and xmonad 0.7 -- Thanks & Regards Changying Li

2 1

darcs patch: add FadeInactive to fade out inactive wi... (and 1 more)
by Justin Bogner 24 May '08

24 May '08

Fri May 23 14:58:38 MDT 2008 Justin Bogner <mail(a)justinbogner.com> * add FadeInactive to fade out inactive windows using xcompmgr Fri May 23 15:39:37 MDT 2008 Justin Bogner <mail(a)justinbogner.com> * made fadeInactiveLogHook take an argument amount to fade

2 1