December 2008 - xmonad

Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 08 Dec '08

08 Dec '08

Comment #24 on issue 97 by sharma.animesh: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 To add, the installation of dwm dwm-tools brought the problem back. Good thing is that removing the dwm thingy removes the problem as well. So I suspect some strange play between floating frames, dwm (mod-p thing) and xscreensaver. -- 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 244 in xmonad: .xmonad/history permissions may allow information leakage
by codesite-noreply＠google.com 08 Dec '08

08 Dec '08

Status: New Owner: ---- New issue 244 by j...(a)kitenet.net: .xmonad/history permissions may allow information leakage http://code.google.com/p/xmonad/issues/detail?id=244 What steps will reproduce the problem? 1. Use xmonad with XMonad.Prompt.Shell 2. Use the prompt to run some shell commands. 3. Observe ~/.xmonad/history is mode 644, and can be read by other users if home directory permissions allow it. What is the expected output? What do you see instead? I'd expect a history file to be written with permissions that do not allow the world to read it. Mode 600 is typical. This is because the file may contain sensative information, up to and including passwords in some circumstances, and home directory permissions sometimes don't block access. (Eg, my home directory and .xmonad are 755, because I want other users to be able to see my ~/.xmonad/xmonad.hs.) What version of the product are you using? On what operating system? 0.8 of xmonad-contrib on Debian unstable Please provide any additional information below. If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. Component-Contrib -- 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 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 07 Dec '08

07 Dec '08

Comment #23 on issue 97 by sharma.animesh: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I suspect the same as comment 22. Now I have reinstalled ubuntu 8.10 and running XMonad via gdm drop down choice menu for selecting sessions. This does not run xscreensaver and somehow this prevents this focus-freezing-mod-key-not-working mysterious phenomenon. -- 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 226 in xmonad: XMonad.Prompt lockups with ghc 6.10
by codesite-noreply＠google.com 06 Dec '08

06 Dec '08

Comment #10 on issue 226 by SpencerJanssen: XMonad.Prompt lockups with ghc 6.10 http://code.google.com/p/xmonad/issues/detail?id=226 Thanks for all the excellent test data. All tests so far have an error similar to: > xmonad: X11 error: BadMatch (invalid parameter attributes), request code=1, error code=8 Which indicates an invalid parameter (BadMatch) on a XCreateWindow call (X11 opcode 1). Naturally all subsequent X calls operating on that window will fail, leading to a failure to render windows and, in the case of Prompt which gathers input from the window, lock ups. We have also seen that superficially similar programs have different results, sometimes even varying from machine to machine. All of these results point to one of two things: incorrect foreign import declarations for createNewWindow, or correct foreign declarations but incorrect code generation by GHC. The next step is to come up with a minimal test program and ask for help from GHC HQ. -- 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 226 in xmonad: XMonad.Prompt lockups with ghc 6.10
by codesite-noreply＠google.com 05 Dec '08

05 Dec '08

Comment #9 on issue 226 by wirtwolff: XMonad.Prompt lockups with ghc 6.10 http://code.google.com/p/xmonad/issues/detail?id=226 Recompiled without xft and still get same errors (simpleTabbed shellPrompt) on x86_64/6.10. Attached is ghc-pkg list and output from sjanssen's test code. Attachments: xftTestLog 2.2 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 226 in xmonad: XMonad.Prompt lockups with ghc 6.10
by codesite-noreply＠google.com 05 Dec '08

05 Dec '08

Comment #8 on issue 226 by wirtwolff: XMonad.Prompt lockups with ghc 6.10 http://code.google.com/p/xmonad/issues/detail?id=226 With 5 Dec xm darcs (with xft), X11-1.4.5, xorg-server-1.5.2 on i686 and x86_64 machines: simpleTabbed works on i686, but on x86_64 allocates space for tabs and draws nothing, does not freeze. (i.e. a gap appears with root visible) http://hpaste.org/12713#a4 --simpleTabbed stdError output shellPrompt works on i686, does nothing then freezes on x86_64. http://hpaste.org/12713#a2 --shellPrompt stdError output -- 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 40 in xmonad: Screen focus does not follow the mouse pointer
by codesite-noreply＠google.com 05 Dec '08

05 Dec '08

Updates: Status: Fixed Comment #9 on issue 40 by SpencerJanssen: Screen focus does not follow the mouse pointer http://code.google.com/p/xmonad/issues/detail?id=40 Fixed! -- 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 226 in xmonad: XMonad.Prompt lockups with ghc 6.10
by codesite-noreply＠google.com 05 Dec '08

05 Dec '08

Comment #7 on issue 226 by SpencerJanssen: XMonad.Prompt lockups with ghc 6.10 http://code.google.com/p/xmonad/issues/detail?id=226 Since we see this error on x86_64, but not i386, it is logical to assume that the issue is most likely in our FFI code. The next step is to audit all the X11 calls that prompt makes and check that the proper sized types are used. -- 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

Always sink mplayer
by Jesús Guerrero 04 Dec '08

04 Dec '08

Hello, I can't seem to find anything (that works) that allows me to start mplayer sinked into the layout. I don't want it to float since I start mplayer into a separate monitor. I use the latest git as of today's date. Is there anything like doSink (instead of doFloat) or something like that? Thanks in advance. -- Jesús Guerrero

4 8

Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 03 Dec '08

03 Dec '08

Comment #22 on issue 97 by jus...(a)justinbogner.com: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I've seen keyboard and mouse input stop working after xscreensaver when gnome-screensaver is also running --- combined with the fact that gnome seems to enjoy starting applications you didn't ask it to, this happened quite a bit before I figured out what was wrong. -- 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