You are not logged in.

#1 2017-02-15 12:13:36

Tétrapyle
Member
Registered: 2014-01-03
Posts: 53

[SOLVED] xmonad crash

[title was: Xmonad / Xorg shuts down but Openbox is fine on new installation]

Hi,

I've not been able to launch xmonad for a year on my main computer so I've been using openbox instead. I couldn't find the issue.

I've just installed a brand new Arch on a brand new USB stick. Installed a bunch of programs with pacman. Copied a few configuration files like bash_profile. I'm using it now with UEFI boot on a laptop computer.

Problem is: it works, but whenever I try to launch xmonad, the Xorg server quits after a few seconds. Well, I just could see, once, a urxvt window for a second.
But, if I replace the 'exec xmonad' line by 'exec openbox' in .xinitrc, it does work.

$ tail -5 .xinitrc 
urxvt -geometry 130x40 &

#exec twm
#exec xmonad
exec openbox-session
$ startx

works.

But

$ tail -5 .xinitrc 
urxvt -geometry 130x40 &

#exec twm
#exec openbox-session
exec xmonad
$ startx

does not : it shuts down with

[...]
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.g_ap_p_ret      (GHC version 8.0.1 for x86_54_unknown_linux)    Please report this as a GHC bug:  http://
[...]

In the journal :

Feb 15 12:23:33 sansdisque systemd[1]: Started Process Core Dump (PID 5137/UID 0).
Feb 15 12:23:33 sansdisque systemd-coredump[5138]: Process 5110 (xmonad-x86_64-l) of user 1001 dumped core.
                                                   
                                                   Stack trace of thread 5110:
                                                   #0  0x00007fad03f8c04f raise (libc.so.6)
                                                   #1  0x00007fad03f8d47a abort (libc.so.6)
                                                   #2  0x0000000000556195 rtsFatalInternalErrorFn (xmonad-x86_64-linux)
                                                   #3  0x00000000005562dd barf (xmonad-x86_64-linux)
                                                   #4  0x000000000056718b stg_ap_p_info (xmonad-x86_64-linux)

I suppose I'm doing something wrong because xmonad seems to work for other people. A driver? Something in my list of packages? A configuration file (but there's almost none left)? Something else?

Thanks for any idea. I hope it's not obvious.

Last edited by Tétrapyle (2017-02-16 10:41:20)

Offline

#2 2017-02-16 10:38:59

Tétrapyle
Member
Registered: 2014-01-03
Posts: 53

Re: [SOLVED] xmonad crash

Well, it works, now.
I deleted xmonad-x86_linux in my .xmonad .

Offline

Board footer

Powered by FluxBB