You are not logged in.
Okay not sure if this is the correct area of the forum but since it deals with a WM I'll put it here. After running pacman -Syu and updating a whole lotta stuff this afternoon (including xfree), my openbox no longer works, yet KDE still does (I'm in KDE right now to post this). When running 'startx', the X server will start up, I will see the grey screen before the WM loads, and will also see briefly my mouse cursor theme show up, then it will dump back out to the CLI. This is the error that is given to me:
openbox: signal 11 caught
shutting down
aborting...dumping core
It is strange to me that openbox ceases to work and KDE still works just fine...maybe I will try to compile the openbox source on my local machine to see if that fixes the problem, but I'm still wondering if anyone else has run into something like this in the past?
My hovercraft is full of eels.
Offline
Okay not sure if this is the correct area of the forum but since it deals with a WM I'll put it here. After running pacman -Syu and updating a whole lotta stuff this afternoon (including xfree), my openbox no longer works, yet KDE still does (I'm in KDE right now to post this). When running 'startx', the X server will start up, I will see the grey screen before the WM loads, and will also see briefly my mouse cursor theme show up, then it will dump back out to the CLI.
I could observe an equivalent behaviour using xfce4. My X server startet and
everything worked fine - until the xscreensaver started its cycle. The Xserver
crashed with signal 11. Using Gnome the problem didn't occur.
It is strange to me that openbox ceases to work and KDE still works just fine...maybe I will try to compile the openbox source on my local machine to see if that fixes the problem, but I'm still wondering if anyone else has run into something like this in the past?
Yes, but since it takes some time to compile it I wanted to wait until beta3/
rc1 will comme out, which is sceduled for the next couple of days. But it
also might be neccessary to recompile xscreensaver againts the new
xfree build.
bye neri
Offline
Hi,
I had a little time and rebuild xfce4 and ... no success
moreover, I did observe that mistake in Gnome now. All that startet with the
latest version of XFree.
Maybe I have some time to test that on another machine this afternoon. So I
hope I can provide some more information tomorrow. It would be great if
you could compile Openbox and tell about success.
Good luck,
bye neri
Offline
Sorry, read two posts at once and replied to the wrong one.... :oops:
SORRY!!!
Offline
Well I recompiled Openbox locally and that seemed to fix the issue...so now all is good
My hovercraft is full of eels.
Offline
Well I recompiled Openbox locally and that seemed to fix the issue...so now all is good
Maybe you should mail that to the maitainer.
I did some further investigation on my problem with the xscreensaver
and the Ctrl+Alt+F1 showed me that the nvidia driver can't load its glx
implementation so I think, I have to recompile the Nvidia driver. Since
Xscreensaver makes heavy use on OpenGL it makes sense, that X crashes
then.
bye neri
Offline
i had no issues when upgrading openbox.
AKA uknowme
I am not your friend
Offline
Hi,
I'm not using the nvidia-driver package cause it didn't work for me or - in
other words - I was to lazy to investigate why. This was because the Nvidia
driver from the company works fine. So I stayed with it.
The actual reason for the crash was probably not the xfree update but the
kernel, Nvidia compiles a kernel module.
Now I recompiled it and that works fine.
bye neri
Offline