You are not logged in.
I have a question, but also think this may shed light on some common problems.
Basically I had my perfect arch setup running and tanked it on a justifiable risk. Then I spent 3 days with multiple re-isntalls trying to get back to my ideal setup.
x11 and openbox installed fine, but if I did "exec openbox-session" (as root or a user) from the cli, I would always get buggy popup windows saying "login". It wouldnt let me use any terminals from the openbox preconfigured menu but firefox and nautilus worked just fine. Gedit only worked half the time.
after deleting the xclock junk at the bottom I changed it to just "exec openbox-session", and everything works now.
Why is this happening? Is the problematic/diagnostic "login" window seen in openbox just clutter from the x11 test suite?
It feels like openbox isn't streamlined yet in pacman. (most other packages integrate super easy). I know custom configuration is always a reason but I don't feel the wiki put enough emphasis on the extremely dramatic differences of changing xinit. The login window "errors" I saw in openbox were always dependent on the program you were trying to execute and not true openbox errors. This led to many many incorrect forum searches and no real leads.
I consider myself a gui insistant user (even for cli I prefer xlterminal because I can copy paste). *it took me days to figure out I wanted "~" not "`" (because of font differences, visual similarities, and both characters being on the same key).
so how come typing from the command line did it wrong, but editing xinitrc did it correctly even though it was the same command?
Offline
I'm surprised exec openbox-session works at all from the console. I guess it launches X if X is not already running.
You should read `man exec`. If you have "exec openbox-session" in ~/.xinitrc then X will start properly, and once x is already started, then openbox will replace the xinitrc script.
If you run "exec openbox-session" from the console, then openbox-session replaces your login shell. You are then no longer loged in, but yet openbox-session tries to start X. Again, I'm amazed this works at all, some buggy performance and a login window don't seem odd then.
Edit:
you might be able to compare "exec openbox-session" in ~/.xinitrc to running just "openbox-session" from the console without the exec command. This way you would still be within a login shell in both cases. Anyone who suggested running "exec openbox-session" from a console drastically led you astray.
Last edited by Trilby (2012-06-23 19:21:27)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
You may find the manual pages for xinit and startx etc. helpful in reading the one for exec.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline