Re: Xorg replaces TTY1
On Sun 22 Nov 2015 at 14:12:09 -0500, The Wanderer wrote:
> On 2015-11-22 at 13:26, Brian wrote:
>
> > On Sun 22 Nov 2015 at 08:16:50 -0600, John Hasler wrote:
> >
> >> Felix writes:
> >>> IIRC this change has to do with systemd
> >>
> >> It happens even when not using Systemd.
> >
> > Possibly something to do accomodating systemd-shim.
> >
> >> From the xinit changelog;
> >
> > * 10-startx-Under-Linux-start-X-on-the-current-VT.patch,
> > 11-startx-Pass-vtX-as-long-as-the-user-did-not-specify-.patch: By default
> > start the server on the current VT, this is necessary to avoid logind to
> > see the startx session as inactive (Closes: #743015 LP: #1247484)
>
> In other words, it's a consequence of logind, which is part of the
> systemd suite and is shipped in the systemd package.
>
> So yes, this change does have to do with systemd - just not with the
> binary named systemd, or with the init system which is (theoretically)
> contained within that binary.
It looks like it is. What functional disadvantage is it to a user of
sysvinit or systemd? Starting X on vt7 is not a Law of Nature.
> AFAIK I've yet to restart X since the xinit version in question hit my
> system, but if I'm now going to be affected by this behavior despite not
> having logind even installed on this machine, I will be - once more - at
> least mildly irritated. I don't even see any indication (in 'man
> startx', which is the obvious appropriate place) of how to disable this
> behavior, either on the startx command line (which would be unacceptable
> anyway) or in a config file...
>
> (Digging a bit finds what is probably the appropriate command-line
> option in 'man Xorg', but still no obvious indication of where to set it
> in a config file, given that I have no xorg.conf and creating one seems
> undesirable for other reasons.)
If the OP (or anyone else) wants X on vt7:
startx -- vt7
Reply to: