You are not logged in.
Hey guys, I'm not sure if this is specifically a [testing] problem or not, but:
Whenever I close openbox or run openbox restart, it drops me to a simple x session with no window management and doesn't close X. As a result of this, I've had no way to restart openbox without rebooting my computer completely.
CTRL+ALT+F1 and CTRL+C doesn't work, as it did in the past, since it seems X now starts on VT1, which I think is a side-effect of systemd but I'm not sure.
If anyone has experienced this, or has advice on how to restore this behavior to normal, I would appreciate it.
Last edited by ndt (2012-11-02 18:29:33)
[~/.]
Offline
How do you start openbox?
Last edited by karol (2012-10-23 22:11:11)
Offline
Ah, so it's not just me. I'm not sure, but I think it started with the upgrade of xorg-server to 1.13. I use a zenity dialog for shutdown/reboot/suspend/logout and simply changed it from doing "openbox --exit" to "pkill -KILL openbox". Yeah, totally not elegant . But hey, it works
Offline
I use openbox on two up-to-date systemd machines with no problems at all. Shutting down/rebooting is done via dbus-send, and exiting is done using the built in exit menu "action", which I suspect is the same as "openbox --exit" which doesn't seem to work for Gusar.
I think the answer to Karol's question will be the most useful information you can both provide right now.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
How do you start openbox?
startx with
exec ck-launch-session dbus-launch openbox-session
in ~/.xinitrc
Running "openbox --exit" or using the built-in openbox menu produces the same issue.
[~/.]
Offline
Can you switch to tty2? If so, does your journalctl list anything relevant immediately after the erroneous behaviour?
If you can't switch to tty2, check your persistent journals for relevant entries.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Same here. I use systemd with gdm as my login manager.
Offline
I can switch to TTY2, and journalctl doesn't show anything of importance.
What's interesting is I can still fully use the programs that are open when I shutdown openbox. It's like openbox closes, but the X session doesn't shut down and none of the programs that are running react to the shutdown, so they just run like if X didn't have a window manager ...
[~/.]
Offline
doesn't need ck-launch-session
my xinitrc start
exec dbus-launch openbox-session
Last edited by martadinata (2012-10-28 06:26:56)
Offline
Since today's update I'm experiencing the same issue. 'openbox --exit' stops openbox itself but Xserver, tint2, other open apps stay running.
my .xinitrc just has the
exec dbus-launch openbox-session
Offline
Another thread is also discussing this problem:
Offline
Beemer, are you sure openbox exits? What I'm seeing here is that openbox's functionality disappears i.e. I can no longer manage windows, but the openbox executable is still running. Killing that returns me to a console prompt.
Offline
I see exactly the same problem. It appears that 'openbox --exit' kills the WM, but does not fully exit openbox, hence the session remains. In my logout script, I now need an extra line after the exit, eg. 'openbox --exit; pkill -9 openbox'.
The issue also affects oblogout.
[EDIT}: I didn't notice that this is on [testing]. I do not use testing. This affects me on non-testing repos. I noticed it today (Oct 30).
Last edited by mervinb (2012-11-01 02:08:08)
Offline
somehow this happen, after recent update the problem exactly the same,,, reported as bug maybe?
Offline