[arch-general] X logs me out from tty on close
Hello everyone, I had a rather interesting problem recently. I dont have any display manager and I open desktop environment from tty when needed. Previously when I logged out from Xfce or closed down X server, it would put me back on my tty session. Now when I do the same, it also logs me out from tty and I must login again. Is this the expected behaviour after some xorg or kernel update? Or did I mess up something? I tried with both `startx` and `startxfce4`. And to be sure that this is not an driver related problem, I also tried with `nvidia-xrun`, same results. Thanks in advance.
(Thu, Jan 10, 2019 at 12:16:20PM +0300) Ali Emre Gülcü via arch-general :
Hello everyone, I had a rather interesting problem recently. I dont have any display manager and I open desktop environment from tty when needed. Previously when I logged out from Xfce or closed down X server, it would put me back on my tty session. Now when I do the same, it also logs me out from tty and I must login again. Is this the expected behaviour after some xorg or kernel update? Or did I mess up something? I tried with both `startx` and `startxfce4`. And to be sure that this is not an driver related problem, I also tried with `nvidia-xrun`, same results.
Hi Ali, To me it sounds rather like your session exists now with a killall instead of <something else that only kills the startx process> before. Did you change something related to that recently? You could try to check that hypothesis (I don’t know exactly how, maybe running some additional forked process in your initrc and see if it gets killed when you exit?). -- Ismael
On Thu, 10 Jan 2019, 12:23 Ismael Bouya (Thu, Jan 10, 2019 at 12:16:20PM +0300) Ali Emre Gülcü via arch-general : Hello everyone,
I had a rather interesting problem recently. I dont have any display
manager and I open desktop environment from tty when needed. Previously
when I logged out from Xfce or closed down X server, it would put me back
on my tty session. Now when I do the same, it also logs me out from tty
and
I must login again. Is this the expected behaviour after some xorg or
kernel update? Or did I mess up something? I tried with both `startx` and
`startxfce4`. And to be sure that this is not an driver related problem,
I
also tried with `nvidia-xrun`, same results. Hi Ali,
To me it sounds rather like your session exists now with a killall
instead of <something else that only kills the startx process> before. Did you change something related to that recently? You could try to
check that hypothesis (I don’t know exactly how, maybe running some
additional forked process in your initrc and see if it gets killed when
you exit?). --
Ismael Hello, thanks for your reply, but I don't know how to try that neither,
still looking into it. Also this is a fresh install and almost all files
are default. /etc/X11/xinit/xinitrc is auto-generated at install with some
xterms and an xclock, and /etc/X11/xorg.conf was non-existent (later
generated with nvidia-xconfig to try with nvidia-xrun). Another observation
is even when x fails to initialize or force closed by pkill, same thing
happens.
Hello, thanks for your reply, but I don't know how to try that neither, still looking into it. Also this is a fresh install and almost all files are default. /etc/X11/xinit/xinitrc is auto-generated at install with some xterms and an xclock, and /etc/X11/xorg.conf was non-existent (later generated with nvidia-xconfig to try with nvidia-xrun). Another observation is even when x fails to initialize or force closed by pkill, same thing happens.
I think you just proved my hypothesis wrong :) If I understand correctly, your environment is a single terminal + a clock? if so, then exiting the terminal should bring you back to the console. Other questions that could help investigate: - How do you start the startx command? - Do you have maybe an .xinitrc in your home? - startx is normally just a wrapper around xinit, could you maybe look at your process list and see what arguments are given to xinit? That could help investigate. xinit itself takes arguments of the form xinit [client] -- [server] where server is the part to start the X11 server and client is the script to run as user. This is the part that determines what is started (not /etc/X11/xinit/xinitrc, which is normally given by startx as a fallback) -- Ismael
On 01/10/2019 05:21 AM, Ali Emre Gülcü via arch-general wrote:
Hello, thanks for your reply, but I don't know how to try that neither, still looking into it. Also this is a fresh install and almost all files are default. /etc/X11/xinit/xinitrc is auto-generated at install with some xterms and an xclock, and /etc/X11/xorg.conf was non-existent (later generated with nvidia-xconfig to try with nvidia-xrun). Another observation is even when x fails to initialize or force closed by pkill, same thing happens.
I also startx from the terminal, but upon ending my xsession I am right back at the terminal. I have set up my local ~/.xinitrc as specified in: https://wiki.archlinux.org/index.php/Xinit -- David C. Rankin, J.D.,P.E.
Hello, ** Ali Emre Gülcü via arch-general [2019-01-10 12:16:20 +0300]:
Hello everyone, I had a rather interesting problem recently. I dont have any display manager and I open desktop environment from tty when needed. Previously when I logged out from Xfce or closed down X server, it would put me back on my tty session. Now when I do the same, it also logs me out from tty and I must login again. Is this the expected behaviour after some xorg or kernel update? Or did I mess up something? I tried with both `startx` and `startxfce4`. And to be sure that this is not an driver related problem, I also tried with `nvidia-xrun`, same results.
It looks the same as described here https://github.com/systemd/systemd/issues/11269 and that issue has a solution https://github.com/systemd/systemd/pull/11379
Thanks in advance.
--- WBR, Vladimir Lomov -- No one can feel as helpless as the owner of a sick goldfish.
@Ismael to be precise, there were 3 xterms and 1 xclock, on my older systems closing the main term would return me back to tty. And no .xinitrc was present in my home folder, modifying /etc/X11/xinit/xinitrc has observable effects so I am sure it is using that file. What made me surprised was that this happened when I was using all default configs. It seems that @Vladimir is right, this is the exact same thing happening here. I never thought this was caused by systemd, I think I will use a graphical DM until the new systemd patch. Thank you both for your time :)
participants (4)
-
Ali Emre Gülcü
-
David C. Rankin
-
Ismael Bouya
-
Vladimir Lomov