Hi there. When it comes to openbox and X I am pretty much a noob. I like what I see, I can change the menu and also managed to edit some of the polybar icons, however that is pretty much all I know. That is also one reason why I chose Archlabs.
So today I was at my cousin’s house and showed him my fancy new laptop with that cool operating system (archlabs). So I gave it to her, locked. However she managed to restart the (probably X) session by pressing [CTRL] [ALT] [ENTER] [BACKSPACE]. That way she entered the system without knowing my password.
First of all to my configuration: I guess she was able to get into the system because I do not use LightDM. However, I tested the shortcut also on my arch Desktop with KDE and on the Ubuntu Bionic Beaver of my cousin, however it would not restart X there.
I would guess installing LightDM would at least stop people from breaking into the system, but I am not so much of a fan of this, however. I chose not to install LightDM because I have encrypted my system and you already need to know that password to even start it up. I would also prefer not to do that in the next time. However, if it is necessary, I will do it.
I did check the Arch Wiki site about Openbox, but I did not find a shortcut to exit the X server. Searching the combination I found something similar to kill X ([CTRL] [ALT] [BACKSPACE]). Turns out, that works on my system. Now I know its not a bug, its a feature, but if it is a feature, I hope one can deactivate it?
Looking further I found something called dontzap, that is used to activate and deactivate this key combination. I found that in the arch wiki. That should prevent X from being killed. However, the file I need to edit does not exist. When I want to create it, I need to stop the X server first. Turns out, I can kill it, but I can not prevent it from respawning. So no creating that file for me. Tried to do it with chroot. For some reason I can not just decrypt the partition and mount it as stated in the arch wiki. I am quite fed up.
Does anyone have a good idea how to fix this whole issue? Also, why is this configuration the default on archlabs? I imagine that to be dangerous.