Bug 73152

Summary: gdm can get tty2-6 even with default "#ReserveVT=6" left in logind.conf
Product: systemd Reporter: Pacho Ramos <pachoramos1>
Component: generalAssignee: systemd-bugs
Status: RESOLVED NOTABUG QA Contact: systemd-bugs
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Pacho Ramos 2013-12-30 13:18:03 UTC
I didn't touch default logind.conf file that contains:
#ReserveVT=6

But gdm can still catch ttys from 1-6 when I switch to new users and, then, I end up usually with a gdm in tty3, a console in 2 and 4, another tty in 5... that can be a bit confusing

Is this behavior normal? Per the man page it doesn't look to work as expected to me:
       ReserveVT=
           Takes a positive integer. Configures the number of one virtual
           terminal that shall unconditionally be reserved for autovt@.service
           activation (see above). The VT selected with this option will be
           marked busy unconditionally, so that no other subsystem will
           allocate it. This functionality is useful to ensure that regardless
           of how many VTs are allocated by other subsystems, one login
           "getty" is always available. Defaults to 6 (in other words, there
           will always be a "getty" available on Alt-F6.). When set to 0, VT
           reservation is disabled.


Thanks for your help
Comment 1 Lennart Poettering 2014-02-21 14:09:35 UTC
ReserveVT will only reserver the one tty specified, that's all. It has no effect on the VTs below it.

The man page is pretty explicit about it, no: "Configures the number of *one* virtual terminal..."

Hence X11 on tty3, tty2, tty4, tty5 are completely expected.
Comment 2 Pacho Ramos 2015-06-19 18:22:39 UTC
Is there any way to Reserve more than one tty? That way we could prevent gdm from opening new X session per user randomly on free ttys and causing me to need to surf across all TTYs to find the right one :/

Thanks a lot :)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.