Obmenu kills x
I have installed Openbox and Obmenu from slackbuild.org. Every time I save changes I've done in Obmenu, x is killed and I'm back at console. The changes are saved. I use startx to start openbox-session, and I changed in .xinitrc to
Code:
exec ck-launch-session dbus-launch --exit-with-session /usr/bin/openbox-session &>>xlog Code:
xinit: connection to X server lost Code:
obmenu &>>obmenulog Code:
$ lspci | grep VGA |
Run
Quote:
Quote:
|
I find this really strange. I don't think the problem is obmenu. It's just a few python script, and they are exactly the same as in Arch, where obmenu works as it should.
I'm quite sure that the moment x (or openbox) crashes is when obmenu has saved the changes and runs reconfigure. I can manually change in menu.xml and then run reconfigure from the menu without it crash. I'm out of ideas... Maybe I should just recompile openbox and see if that helps. (I had the dependencies before I installed openbox.) |
So finally I have solved this problem - as an extra bonus by getting rid of some autostart-bloat...
What I did was copy /usr/bin/openbox-session and /usr/bin/openbox-autostart to ~/.bin (which is first in my path). I changed them like this: openbox-session Code:
#!/bin/sh Code:
#!/bin/sh |
I open this thread again because this is a really strange mysterium, and I also think the solution I found earlier caused other crashes... The day after I thought this was solved, I started to get strange freezes, where everything except the mouse was freezing. I could right-click the desktop to get the menu and start a terminal. If I was fast I could run 'sudo reboot' before that terminal also froze, and the system rebooted. Changing the script to start openbox was the last change I did before this started. (But changing back did not stop the freezes, so maybe it is not related at all...)
I finally had to restore a backup, and now I'm struggling with Obmenu again. I restored the backup to another partition, so I have the original install left. Right now I'm on the old install, and I have tried to change back to start openbox from /usr/bin/openbox-session. In .xinitrc I have this line Code:
exec ck-launch-session dbus-launch --exit-with-session /usr/bin/openbox-session I copied the script openbox-session from /usr/bin to my /home, and changed .xinitrc to use it. I didn't change anything in it. And now Obmenu works as it should. I have tried it several times, and it really is so. If I use /usr/bin/openbox-session, then Obmenu cause openbox to crash, but if I use the exact same script, copied to somewhere in my /home (it doesn't matter if it is a directory I have added to my path or not), then no crashes from Obmenu. What's the difference, when the script is the exact same??? Code:
#!/bin/sh |
I would start by eliminating dependencies. Something like this
Code:
cd /usr/bin Then you probably have dud code in something. This is sometimes caused by a disk error, a lost sector or something that e2fsck corrects. |
This is what I get:
Code:
root@slack:/usr/bin# ldd * | grep found | more But I don't think this is related to the problem for this thread. Keep in mind Obmenu is just a few pythonscript. I recomplied Openbox, but it didn't make any difference. |
I'd guess kdelibs if you have a kde package without kde. After that you're on your own. kde core & kde graphics are also good guesses, as is kde desktop. If it's Slackware, there's a file list with each installed package.Try a few of the obvious ones with
cd /tmp/somedir explodepkg /path/to/package find -name ' If obmenu is python based try opening an xterm and running python /path/to/obmenu > ~/bugfind.txt 2>&1 and see if you get any interesting errors. |
I think I have found the cause of this problem, even if I still think it's strange. In .xinitrc, if I have the full path "/usr/bin/openbox-session" then obmenu causes X to crash, but if I only have "openbox-session" (exec ck-launch-session dbus-launch openbox-session) then it works.'which openbox-session' gives '/usr/bin/openbox-session'. It behaves the same in Salix, which has never crashed for me, but when I changed to "/usr/bin/openbox-session" it also crashed.
I think I can finally mark this thread as solved, even if I really don't understand why it can't handle absolute path to openbox-session... |
All times are GMT -5. The time now is 09:57 AM. |