Thanks, now I understand where does the problem come from. So, is that simply not achievable in systemd? I mean, since logind "has no way to know about my session on vt7", then what about I *tell* it explicitly? Maybe through some cmdline tools, for example, something like: `loginctl add-vt vt7 session03`, or through proper configuration of logind? Or can I just spawn startx in a new session that is associative with vt7, i.e. something like `systemd-setsid startx -- vt7`?
Kevin On Fri, Mar 28, 2014 at 11:46 PM, Colin Guthrie <[email protected]>wrote: > 'Twas brillig, and Mantas Mikulėnas at 28/03/14 15:22 did gyre and gimble: > > You have already found the correct way to fix this – start X on the > > /same/ vt that you logged in (e.g. `startx -- vt2` or `startx -- > > vt$XDG_VTNR`). > > Yes, and indeed most distros patch their startx to do this for you > magically these days. > > Col > > -- > > Colin Guthrie > gmane(at)colin.guthr.ie > http://colin.guthr.ie/ > > Day Job: > Tribalogic Limited http://www.tribalogic.net/ > Open Source: > Mageia Contributor http://www.mageia.org/ > PulseAudio Hacker http://www.pulseaudio.org/ > Trac Hacker http://trac.edgewall.org/ >
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
