Re: x and virtual consoles
On Tue 06 Aug 2019 at 07:11:04 (+0100), Ed wrote:
> On 2019-08-05 16:59-0500, David Wright wrote:
> > Perhaps this is all to do with your DM. I use startx, and since
> > stretch the Xserver runs "on top of" the VC that started it, and
> > as the user, not root. In the past, Xservers ran as root on VC7,
> > VC8, …
>
> Does lightdm or gdm act as your greeter? I have not reproduced this
> between xsessions started by tty login, only ever the session started by
> lightdm crashes.
No, I'm afraid I'm a member of Curt's “ineluctable "just use Mutt"”
association, using startx (though I don't see what Mutt has to do with
the price of fish).
One footnote to my comment, though. After posting it, I looked back
at the line in Xsession and noted that nowadays there's a variable
that might be more useful than the date, so I changed it.
ERRFILE=$HOME/.xsession-errors-$XDG_VTNR
will number them by the VC that the Xserver started on. This could
be fragile if you were to be able to start more than one from the same
VC. OTOH it's predictable as it's available before the Xserver starts,
unlike another alternative which is
ERRFILE=$HOME/.xsession-errors-${DISPLAY#:}
Both these have the advantage over date that they are self-cleaning,
getting overwritten in the normal course of events.
> Tried to force a x session on vt8, but that responds with 'Permission
> denied' when doing that. I think system d sets up the permissions of
> tty1 when you use that console:
>
> crw------- 1 ed tty 4, 1 2019-08-06 06:57:48 /dev/tty1
I take what the system throws at me. AIUI the user-owner Xserver has
to run on the tty from which it was started, whereas the older
root-owned ones could open tty7, 8, etc. I don't use the latter
any more.
My guess is that you can't run two user-owned Xservers from the *same*
VC, which is why I trust using $XDG_VTNR above. I take it that this
variable is a new Desktop Group thingy, and its newness is why I
wasn't using it already.
Cheers,
David.
Reply to: