You are not logged in.
Startx used to put X on VT 7, and this has 2 important benefits for me :
1. the output of xsession is visible on the terminal i ran startx from
2. if i used CTRL-C on the terminal where i ran startx, it killed the X session.
man startx, xinit, logind.conf & systemctl help graphical.target gave no clues how to get this behaviour with systemd/logind .
While i could enable the CTRL-ALT-BACKSPACE shortcut to be able to kill X again and get 2 back, this is much more error prone then using CTRL-C in 1 specific terminal.
Last edited by Lone_Wolf (2012-11-21 13:36:08)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I've never used graphical.target, but if there is a call to startx or xinit you can include a parameter for the xserver as follows:
xinit -- vt7
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
the command is
startx -- vt1
for me it is started on 1 as you can see.
But as described in the wiki, you can make an alias for startx which creates the logs on the terminal in a file:
alias startx='startx &> ~/.xlog'
Maybe read this https://wiki.archlinux.org/index.php/Co … emd-logind
because loginctl will not be able to track your session and automount will not work and stuff.
Offline
Thanks a lot, Trilby & phil.
Using
startx --vt7
does exactly what i want it to do.
As for automounting and such : i never use that, pmount/pumount work great and are simple to use.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline