- xmonad - Haskell.org

Issue 303 in xmonad: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them.
by codesite-noreply＠google.com 01 Jul '09

01 Jul '09

Comment #3 on issue 303 by daniel.wagner: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them. http://code.google.com/p/xmonad/issues/detail?id=303 Can you check that this is definitely an xmonad problem? This sounds more like a video-driver problem to me. Please try Quake in another window manager and report the results 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 303 in xmonad: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them.
by codesite-noreply＠google.com 01 Jul '09

01 Jul '09

Comment #2 on issue 303 by twpedersen: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them. http://code.google.com/p/xmonad/issues/detail?id=303 Xorg.log attached Attachments: Xorg.0.log.old 33.7 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

1 0

Issue 303 in xmonad: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them.
by codesite-noreply＠google.com 01 Jul '09

01 Jul '09

Comment #1 on issue 303 by twpedersen: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them. http://code.google.com/p/xmonad/issues/detail?id=303 Also X gives me: XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 290 requests (288 known processed) with 0 events remaining. and dmesg: [drm] Setting GART location based on new memory map [drm] Loading R100 Microcode [drm] writeback test succeeded in 2 usecs mtrr: no MTRR for e0000000,1000000 found -- 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 303 in xmonad: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them.
by codesite-noreply＠google.com 01 Jul '09

01 Jul '09

Status: New Owner: ---- New issue 303 by twpedersen: Quake 3 and other OpenGL programs crash and bring down xmonad and X with them. http://code.google.com/p/xmonad/issues/detail?id=303 What steps will reproduce the problem? 1. Start Xmonad 2. Start Quake3 3. .... What is the expected output? What do you see instead? Fancy shooter, X crashes. What version of the product are you using? On what operating system? xmonad 0.8.1 Linux 2.6.30 xorg-server 1.6.1.901-1 sdl 1.2.13-3 libgl 7.4.2-2 mesa 7.4.2-1 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". no xmonad.hs Please provide any additional information below. Does not occur when using windowmanager other than xmonad (such as twm). This is my .xinitrc: #!/bin/sh urxvtd & exec 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

1 0

window placement where previously closed window was
by Matthias Merk 30 Jun '09

30 Jun '09

Hi, i was wondering if it's possible to configure xmonad to place a new window in the very same place where the previously closed window has been? i'm currently using: xmonad 0.8.1 and the grid layout most of the time ( http://hackage.haskell.org/packages/archive/xmonad-contrib/0.8/doc/html/XMo… ) for example when i'm closing a terminal in the bottom right corner, the next terminal opens in the top right corner changing the position of at least on other window. thanks in advance regards matthias

2 1

Issue 4 in xmonad: Separate focus for tiled and floating layers
by codesite-noreply＠google.com 30 Jun '09

30 Jun '09

Comment #13 on issue 4 by byorgey: Separate focus for tiled and floating layers http://code.google.com/p/xmonad/issues/detail?id=4 I may actually try working on this at Hac phi. We'll see. -- 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 294 in xmonad: fadeInactiveLogHook behaviour messed up on xinerama
by codesite-noreply＠google.com 30 Jun '09

30 Jun '09

Comment #6 on issue 294 by daniel.schoepe: fadeInactiveLogHook behaviour messed up on xinerama http://code.google.com/p/xmonad/issues/detail?id=294 Yes, the IORef part would still need to stay in your xmonad.hs(this could become easier, if my patch for extensible state in core will be applied). The main issue of the OP should also be solved by the standard criterion, which now checks, whether the window really is the focused one. -- 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 294 in xmonad: fadeInactiveLogHook behaviour messed up on xinerama
by codesite-noreply＠google.com 30 Jun '09

30 Jun '09

Comment #5 on issue 294 by hgabreu: fadeInactiveLogHook behaviour messed up on xinerama http://code.google.com/p/xmonad/issues/detail?id=294 Sorry, you're right. There's fadeOutLogHook in XMonad.Hooks.FadeInactive where you can specified criteria. The modified version in my xmonad.hs allows to toggle dynamically if a window is going to be faded. Anyway, the main issue pointed by OP is not this, but about the 'per screen' problem (I have not tested 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

1 0

Issue 294 in xmonad: fadeInactiveLogHook behaviour messed up on xinerama
by codesite-noreply＠google.com 30 Jun '09

30 Jun '09

Comment #4 on issue 294 by daniel.schoepe: fadeInactiveLogHook behaviour messed up on xinerama http://code.google.com/p/xmonad/issues/detail?id=294 I (my nick was asgaroth at that time) later sent in something like the custom version I gave you, as a patch and it has been applied. So after darcs pull'ing and rebuilding, it should work with the standard Hooks.FadeInactive module now. -- 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 294 in xmonad: fadeInactiveLogHook behaviour messed up on xinerama
by codesite-noreply＠google.com 30 Jun '09

30 Jun '09

Comment #3 on issue 294 by hgabreu: fadeInactiveLogHook behaviour messed up on xinerama http://code.google.com/p/xmonad/issues/detail?id=294 No, fadeInactiveLogHook doesn't has this implemented in contrib-darcs. I use a modified version of it to achieve this be behavior (inside my xmonad.hs, provided by asgaroth at #xmonad channel). Stripped xmonad.hs attached. Attachments: fadeOutLogHook.hs 2.4 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

1 0