Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and then I get an X error immediately after logging in and am bounced back to the login screen. Logging in again normally works fine. Here is .xsession-errors from one of those occasions: /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=en_GB. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. /home/jim/.xsession: line 9: 5756 Segmentation fault $CABAL_BIN/xmonad ############### And here is my .xinitrc: #!/usr/bin/env bash xsetroot -cursor_name top_left_arrow -solid gray30 CABAL_BIN=/home/jim/.cabal/bin $CABAL_BIN/xmobar & gnome-settings-daemon & numlockx on & unclutter & $CABAL_BIN/xmonad ################ The line .xsession-errors refers to is the last one, which launches xmonad. What's going on? Thanks, -- Jim Burton
On Tue, Mar 31, 2009 at 07:50:29AM +0100, Jim Burton wrote:
Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and then I get an X error immediately after logging in and am bounced back to the login screen. Logging in again normally works fine. Here is .xsession-errors from one of those occasions:
/etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=en_GB. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. /home/jim/.xsession: line 9: 5756 Segmentation fault $CABAL_BIN/xmonad
###############
And here is my .xinitrc:
#!/usr/bin/env bash xsetroot -cursor_name top_left_arrow -solid gray30 CABAL_BIN=/home/jim/.cabal/bin $CABAL_BIN/xmobar & gnome-settings-daemon & numlockx on & unclutter &
$CABAL_BIN/xmonad
################
The line .xsession-errors refers to is the last one, which launches xmonad. What's going on?
Thanks,
-- Jim Burton
We need information to see what is going on. The most likely problem is a miscompiled xmonad, try cleaning, rebuilding, and reinstalling xmonad and contrib. Finally, execute "xmonad --recompile". If the problem persists, try to get a stack trace. Cheers, Spencer Janssen
At Tue, 31 Mar 2009 18:23:49 -0500, Spencer Janssen wrote:
On Tue, Mar 31, 2009 at 07:50:29AM +0100, Jim Burton wrote:
Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and then I get an X error immediately after logging in and am bounced back to the login screen. Logging in again normally works fine. Here is .xsession-errors from one of those occasions:
[snip]
The line .xsession-errors refers to is the last one, which launches xmonad. What's going on?
Thanks,
-- Jim Burton
We need information to see what is going on. The most likely problem is a miscompiled xmonad, try cleaning, rebuilding, and reinstalling xmonad and contrib. Finally, execute "xmonad --recompile".
Thanks for your reply. I already rebuilt but will try xmonad --recompile.
If the problem persists, try to get a stack trace.
How do I do this? Regards, Jim
Cheers, Spencer Janssen _______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
At Wed, 1 Apr 2009 08:57:32 +0100 (BST), Jim Burton wrote:
At Tue, 31 Mar 2009 18:23:49 -0500, Spencer Janssen wrote:
On Tue, Mar 31, 2009 at 07:50:29AM +0100, Jim Burton wrote:
Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and then I get an X error immediately after logging in and am bounced back to the login screen. Logging in again normally works fine. Here is .xsession-errors from one of those occasions:
[snip]
The line .xsession-errors refers to is the last one, which launches xmonad. What's going on?
Thanks,
-- Jim Burton
We need information to see what is going on. The most likely problem is a miscompiled xmonad, try cleaning, rebuilding, and reinstalling xmonad and contrib. Finally, execute "xmonad --recompile".
Thanks for your reply. I already rebuilt but will try xmonad --recompile.
If the problem persists, try to get a stack trace.
How do I do this?
Can anyone tell me how to get a stack trace when xmonad crashes or otherwise diagnose my problem? The problem does indeed persist and I don't know if it's a known bug etc. Thanks, Jim
Regards,
Jim
Cheers, Spencer Janssen _______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
jim:
At Wed, 1 Apr 2009 08:57:32 +0100 (BST), Jim Burton wrote:
At Tue, 31 Mar 2009 18:23:49 -0500, Spencer Janssen wrote:
On Tue, Mar 31, 2009 at 07:50:29AM +0100, Jim Burton wrote:
Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and then I get an X error immediately after logging in and am bounced back to the login screen. Logging in again normally works fine. Here is .xsession-errors from one of those occasions:
[snip]
The line .xsession-errors refers to is the last one, which launches xmonad. What's going on?
Thanks,
-- Jim Burton
We need information to see what is going on. The most likely problem is a miscompiled xmonad, try cleaning, rebuilding, and reinstalling xmonad and contrib. Finally, execute "xmonad --recompile".
Thanks for your reply. I already rebuilt but will try xmonad --recompile.
If the problem persists, try to get a stack trace.
How do I do this?
Can anyone tell me how to get a stack trace when xmonad crashes or otherwise diagnose my problem? The problem does indeed persist and I don't know if it's a known bug etc.
The main way is to attach gdb to the core, and we'll see if it is in Haskell code (meaning a GHC bug or FFI binding error), or in X11 code (X bug?). The most important thing is to list GHC versions, X11 versions, Haskell library versions, and to ensure it is clean build. Then, narrow down the extensions you're using to find the smallest set that produces the error.
At Fri, 17 Apr 2009 02:15:33 -0700, Don Stewart wrote:
jim:
At Wed, 1 Apr 2009 08:57:32 +0100 (BST), Jim Burton wrote:
At Tue, 31 Mar 2009 18:23:49 -0500, Spencer Janssen wrote:
On Tue, Mar 31, 2009 at 07:50:29AM +0100, Jim Burton wrote:
Hi, I'm using xmonad 0.8.1, GHC 6.10, Ubuntu intrepid, and every now and then I get an X error immediately after logging in and am bounced back to the login screen. Logging in again normally works fine. Here is .xsession-errors from one of those occasions:
[snip]
Can anyone tell me how to get a stack trace when xmonad crashes or otherwise diagnose my problem? The problem does indeed persist and I don't know if it's a known bug etc.
The main way is to attach gdb to the core, and we'll see if it is in Haskell code (meaning a GHC bug or FFI binding error), or in X11 code (X bug?).
Hi Don, Thanks for your reply. I've never used gdb -- any advice on what exactly I need to do? I think I need to start this from .xinitrc as when xmonad crashes it does so on login so will it be something like # in .xinitrc #$CABAL_BIN/xmonad gdb $CABAL_BIN/xmonad > ~/debug.txt ?
The most important thing is to list GHC versions, X11 versions, Haskell library versions, and to ensure it is clean build.
I listed most of these already: GHC 6.10.1, X version is (the ubuntu intrepid package) 1:7.4~5ubuntu3, xmonad 0.8.1 installed via cabal. Re a clean build, I tried to upgrade/reinstall with cabal just now and it fails when trying to install unix: Building unix-2.3.2.0... [ 1 of 21] Compiling System.Posix.User ( dist/build/System/Posix/User.hs, dist/build/System/Posix/User.o ) [ 2 of 21] Compiling System.Posix.Unistd ( dist/build/System/Posix/Unistd.hs, dist/build/System/Posix/Unistd.o ) [ 3 of 21] Compiling System.Posix.Time ( dist/build/System/Posix/Time.hs, dist/build/System/Posix/Time.o ) [ 4 of 21] Compiling System.Posix.Resource ( dist/build/System/Posix/Resource.hs, dist/build/System/Posix/Resource.o ) [ 5 of 21] Compiling System.Posix.Process.Internals ( System/Posix/Process/Internals.hs, dist/build/System/Posix/Process/Internals.o ) System/Posix/Process/Internals.hs:10:17: Module `GHC.Conc' does not export `Signal' cabal: Error: some packages failed to install: containers-0.2.0.1 failed during the building phase. The exception was: exit: ExitFailure 1 directory-1.0.0.3 depends on unix-2.3.2.0 which failed to install. process-1.0.1.1 depends on unix-2.3.2.0 which failed to install. unix-2.3.2.0 failed during the building phase. The exception was: exit: ExitFailure 1 xmonad-0.8.1 depends on unix-2.3.2.0 which failed to install.
Then, narrow down the extensions you're using to find the smallest set that produces the error.
Let me know if it's useful to see my .xinitrc and xmonad.hs. I am using very few extensions, just tabbed layout. I'll experiment with removing this. Thanks, Jim
participants (3)
-
Don Stewart -
Jim Burton -
Spencer Janssen