February 2009 - xmonad

error when building xmobar 0.9-3
by Chengqi(Lars) Song 27 Feb '09

27 Feb '09

i need to add xft and utf-8 support to xmobar, so i chose to install aur/xmobar; i add two lines in PKGBUILD for that: runhaskell Setup configure --flags="with_utf8" || return 1 runhaskell Setup configure --flags="with_xft" || return 1 then i tried to build aur/xmobar, but i got the following error msg: --------------------------start of output-------------------------- Building xmobar-0.9... [ 1 of 25] Compiling Commands ( Commands.hs, dist/build/xmobar/xmobar-tmp/Commands.o ) [ 2 of 25] Compiling Runnable[boot] ( Runnable.hs-boot, dist/build/xmobar/xmobar-tmp/Runnable.o-boot ) [ 3 of 25] Compiling XUtil ( dist/build/xmobar/xmobar-tmp/XUtil.hs, dist/build/xmobar/xmobar-tmp/XUtil.o ) [ 4 of 25] Compiling Plugins ( Plugins.hs, dist/build/xmobar/xmobar-tmp/Plugins.o ) [ 5 of 25] Compiling Plugins.StdinReader ( Plugins/StdinReader.hs, dist/build/xmobar/xmobar-tmp/Plugins/StdinReader.o ) Plugins/StdinReader.hs:29:15: Ambiguous type variable `e' in the constraint: `GHC.Exception.Exception e' arising from a use of `catch' at Plugins/StdinReader.hs:29:15-78 Probable fix: add a type signature that fixes these type variable(s) ==> ERROR: Build Failed. Aborting... Error: Makepkg was unable to build xmobar package. --------------------------end of output-------------------------- whats wrong here? it seems the community/xmobar has no utf8 and xft enabled, but it's really needed for CJK users. thanks lars

2 2

Issue 279 in xmonad: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Comment #5 on issue 279 by allbery.b: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null http://code.google.com/p/xmonad/issues/detail?id=279 The strace doesn't show what I really need, but you'd need to trace the entire X session to get it. What I suspect is that your stdout/stderr is going to a pty that is no longer open (screen session, or if you're launching the session with an xterm, starting xmonad, then closing the xterm). -- 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 278 in xmonad: quick xmonad restart is not enough to make IM layout work
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Updates: Status: Invalid Comment #3 on issue 278 by roma(a)ro-che.info: quick xmonad restart is not enough to make IM layout work http://code.google.com/p/xmonad/issues/detail?id=278 (No comment was entered for this change.) -- 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 278 in xmonad: quick xmonad restart is not enough to make IM layout work
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Comment #2 on issue 278 by arseni.buinitsky: quick xmonad restart is not enough to make IM layout work http://code.google.com/p/xmonad/issues/detail?id=278 yep, mod-shift-space works -- 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 279 in xmonad: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Comment #4 on issue 279 by seschwar: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null http://code.google.com/p/xmonad/issues/detail?id=279 Nothing gets written to stdout/fd 1. Here is basically what gets written to stderr/fd 2: write(2, "P"..., 1) = -1 EIO (Input/output error) write(2, "xmonad-i386-linux: "..., 19) = -1 EIO (Input/output error) write(2, "<stderr>: hPutChar: hardware fault (Input/output error)"..., 55) = -1 EIO (Input/output error) write(2, "\n"..., 1) = -1 EIO (Input/output error) I've attached the complete strace. Attachments: xmonad.strace 295 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 279 in xmonad: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Comment #3 on issue 279 by allbery.b: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null http://code.google.com/p/xmonad/issues/detail?id=279 Try attaching to xmonad with truss/dtruss/strace and watching fds 1 and 2 to capture the output without redirection. -- 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 279 in xmonad: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Comment #2 on issue 279 by seschwar: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null http://code.google.com/p/xmonad/issues/detail?id=279 And it doesn't matter where stderr is redirected. I've captured the output when I did what makes XMonad crash. However, since I redirected stderr it didn't crash anymore. Attachments: 2 165 bytes -- 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 279 in xmonad: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Comment #1 on issue 279 by seschwar: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null http://code.google.com/p/xmonad/issues/detail?id=279 Actually X is not crashing. XMonad does. The X server just shuts down afterwards. -- 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 279 in xmonad: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Status: New Owner: ---- New issue 279 by seschwar: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null http://code.google.com/p/xmonad/issues/detail?id=279 I usually like to start X form the console in the background an then logout. I do it like this: - Using zsh's builtins: startx &!; exit - Or using another shell and detach [1]: detach startx; exit Then the following actions will crash the whole X server: - Save and overwrite an already existing file with Firefox - Execute "Verify versions and deprecations" in Glade's preference dialog I can get my programs to behave normal again by appending "2> /dev/null" to the "exec xmonad" line in my ~/.xinitrc. I have no idea what's going on. The problem doesn't appear when i just have "exec xterm" in my ~/.xinitrc. Also it doesn't matter whether I use a log hook or not. I am using XMonad and XMonad-contrib from hackage and the following packages on Arch Linux: detach 0.2.0-1 firefox 3.0.6-1 glade 3.5.4-1 ghc 6.10.1-2 gtk2 2.14.7-1 xmonad 0.8.1 xmonad-contrib 0.8.1 zsh 4.3.9-1 [1] http://detach.sourceforge.net/ -- 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 277 in xmonad: Red border on two windows
by codesite-noreply＠google.com 25 Feb '09

25 Feb '09

Comment #7 on issue 277 by lit...(a)hethrael.org: Red border on two windows http://code.google.com/p/xmonad/issues/detail?id=277 This sounds similar to issue 237 that I was having. It started on its own, and it went away by itself. I suspect it had something to do with upgrading Xorg or some other library, because I didn’t make any changes to my xmonad configuration when the issue started happening or when it stopped. -- 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