You are not logged in.
Pages: 1
I have the xserver set to start in my .bash_profile. I was filled with glee when I had xmonad running in Arch for only 36 hours before I broke it!
I'm running a Lenovo t520 (an oooold friend)
X doesn't seem to want to start under root, either when I get dbus related errors. What have I done?!
Here's the output from various commands:
cat /var/log/Xorg.0.log
http://ix.io/23jb
cat ~/.local/share/xorg/Xorg.0.log
http://ix.io/23jc
lspci -k
http://ix.io/23jg
lspci -v
http://ix.io/23jh
I am SO looking forward to getting back on track here. Thank you SO MUCH for your help!
Offline
Try to enable https://wiki.archlinux.org/index.php/Ke … _KMS_start
Also ensure to have read https://wiki.archlinux.org/index.php/NVIDIA_Optimus
Welcome to the forum.
Offline
Try to enable https://wiki.archlinux.org/index.php/Ke … _KMS_start
Also ensure to have read https://wiki.archlinux.org/index.php/NVIDIA_OptimusWelcome to the forum.
Thank you so so much! I enabled the Early KMS on my intel and I disabled the Nvidia card in the bios. Unfortunately still won't start.
Here are updated log files:
Thanks again! So excited to have this up and running!
Offline
http://ix.io/23lY doesn't suggest any remaining issues in the server - it starts and terminates immediately w/o error.
Please post your xinitrc.
Also familiarize yourself w/ https://wiki.archlinux.org/index.php/Xinit#xinitrc
Offline
Gosh thank you so so much for this Seth.
Here's my ~/.xinitrc
Here's the files in my /etc/X11/xinit/xinitrc.d/
Here's the contents of those files:
Offline
"man exec"
Nothing after the first "exec" invocation is reached in that script and because you forked it (don't throw ampersands around as if they were candy), the script terminates immediately and with it your session and X11 server.
Offline
Actually, backgrounding gets precedence over the exec, so all the lines are executed, there's just a bunch of subshells created for no purpose other than to be destroyed instantaneously: the & creates a new subshell for the listed command to run in, then the exec replaces that subshell with the named process.
I don't think there is any possible use of `exec <command> &` that could ever make any sense. Use one or the other ... or in most cases, neither.
But the fact that *all* of them are backgrounded means that Xorg will exit right away as there is nothing left to do (no foreground process remains and the end of the xinitrc is reached).
The last lines of the xinitrc should be as follows:
setxkbmap -option caps:swapescape
feh --bg-scale ~/.wallpapers/cheatsheet-big.png
xmobar &
exec xmonad
Last edited by Trilby (2019-12-02 14:23:05)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Then edit the file and replace the default programs with desired commands. Remember that lines following a command using exec would be ignored. For example, to start xscreensaver in the background and then start openbox, use the following:
You are execing too hard, just exec xmonad at the end of a file without the & also don't run setxkbmap with & and run it before the other 3 commands you probably also don't need to background feh, but it shouldn't be inherently harmful
Edit: Argh, I fail my refreshes recently
Last edited by V1del (2019-12-02 14:22:55)
Offline
Actually, backgrounding gets precedence over the exec
Indeed - useless, but nice to know.
Offline
I could not be more grateful. Now my todo list is long, but I may begin it! I had no idea that that's how exec worked. Oy vey. I am so grateful for all of this free tutelage.
Offline
Pages: 1