Openbox exit

Multimoon · 2012-10-28 02:52:43

Hi, I was playing around with some different themes, so I just attempted to use the regular openbox Exit menu using the exit action, or the openbox --exit command. This does stop openbox, but not the x server, and the x server continues running. Before, I could use this and it would do as I had it set up, and logout and restart my login manager, SLiM. I have just noticed this happening recently, possibly after a update. I cannot provide a specific action after which this began to happen, as I just noticed it yesterday. I can confirm that it is not the theme causing this. Any help would be appreciated! Thanks.

Last edited by Multimoon (2012-10-28 02:58:04)

2ManyDogs · 2012-10-28 03:15:11

https://bbs.archlinux.org/viewtopic.php?id=151304

Multimoon · 2012-10-28 03:27:50

Noted, similar issue, but my key binds such as CTRL+ALT+F1 do work.

2ManyDogs · 2012-10-28 03:29:38

Similar enough that I suggest you post in that thread. Perhaps I should have been more clear.

Last edited by 2ManyDogs (2012-10-28 03:31:48)

jasonwryan · 2012-10-28 04:00:33

Please provide more detail: openbox version, slim logs etc...

It does bear some similarity to the thread 2ManyDogs linked to, but I assume you are not using [testing] as you would have explicitly mentioned that.

Multimoon · 2012-10-28 12:59:07

No, I'm not. This seems to have began after I updated the system, assumably updating Xorg as well. Please name the log and location of the log(s) you would like me to post.

n125 · 2012-10-31 06:48:06

I am having the same problem, so perhaps my information will be helpful. I am not sure if this started with yesterday's removal of ConsoleKit from the official repositories, since I've been using i3 recently.

I am not in [testing] and am running Openbox 3.5.0-7. It's started by Slim using this line in ~/.xinitrc:

exec dbus-launch openbox-session

The only lines in /var/log/slim.log read:

slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.

This error also happens if try exiting Openbox after starting it from another tty with "startx".

I have looked through most of the logs in /var/log/ and couldn't find anything timestamped remotely close to the last failed Openbox exit attempt. Nothing registers in the Journal immediately after trying to exit either. Finally, running "openbox --exit" in a terminal does not return any output. So at this point, I am at a loss as to where to look for useful information.

As Gusar suggested in the other thread, exiting of Openbox with "pkill -KILL openbox" does seem to work, but are there any disadvantages to doing it this way?

Last edited by n125 (2012-10-31 07:42:39)

demaio · 2012-10-31 09:20:45

As a workaround I use CTRL-ALT-BACKSPACE to kill the X server after closing all applications ~~(including openbox)~~. If CTRL-ALT-BACKSPACE does not work, see here: https://wiki.archlinux.org/index.php/Xo … s_not_work.

EDIT:

It seems the openbox process is not exiting properly when using the Exit function of Openbox as the openbox process is still running when I look in the process list.

Last edited by demaio (2012-10-31 09:29:58)

TobyJamesJoy · 2012-11-01 07:07:05

I am also affected, not using testing repos. I use a gxmessage script to call "reboot" and "poweroff", these too no longer work, however issuing the commands in a terminal works fine.

Arch Linux

#1 2012-10-28 02:52:43

Openbox exit

#2 2012-10-28 03:15:11

Re: Openbox exit

#3 2012-10-28 03:27:50

Re: Openbox exit

#4 2012-10-28 03:29:38

Re: Openbox exit

#5 2012-10-28 04:00:33

Re: Openbox exit

#6 2012-10-28 12:59:07

Re: Openbox exit

#7 2012-10-31 06:48:06

Re: Openbox exit

#8 2012-10-31 09:20:45

Re: Openbox exit

#9 2012-11-01 07:07:05

Re: Openbox exit

Board footer