You are not logged in.
I'm currently using openbox as a WM and lightdm as a DM. I've noticed that upon multiple logouts (Exit action from openbox's menu) the autostart process (the sh script in .config/openbox/autostart) is never being closed. That, of course, causes an increasing CPU consume.
I don't know if that's the intended behaviour but for me it's undesirable, as I often use openbox's exit as a quick reboot (as many people do). This is my autostart file so far:
compton -c .config/comptonrc &
tint2 &
nm-applet &
volumeicon &
~/.scripts/my_custom_script &
conky &Is there anything wrong with it? I don't think my custom script is causing any trobule, as killing the autostart process successfully kills my script so I'll assume it's unrelated.
Any help will be much appreciated.
Offline
Have you double checked if that script is still active after logging out of openbox? Without the scripts content it is somewhat futile. Do all the other applications get killed properly?
Offline
Maybe if you add 'exit' to the end of the autostart script it would close. Just an idea but could be worth a shot.
as a workaround, you could also just ditch the autostart file and use .xinitrc instead:
# ~/.xinitrc
# start window manager
openbox & wmpid=$!
# stuff from openbox autostart file
compton -c .config/comptonrc &
tint2 &
nm-applet &
volumeicon &
~/.scripts/my_custom_script &
conky &
# wait for window manager to exit
wait $wmpidOffline