FS#44969 - [lightdm] Conflicts with vt02

Attached to Project: Arch Linux
Opened by Hermann Zahnweh (eigengrau) - Friday, 15 May 2015, 10:15 GMT
Last edited by Maxime Gauduin (Alucryd) - Thursday, 13 October 2016, 13:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
lightdm.service is correctly set-up to conflict with getty@tty1.service. However, when lightdm invokes a greeter while a user session is running (e. g., to switch users or lock the seat), it starts a new X display on vt02. This can break a getty or shell session running there.

One way of dealing with this would be to make lightdm conflict with getty@tty2.service. Since this doesn’t leave too many gettys available, it might be preferable to instead configure lightdm to start up on vt07. The secondary display will then be started on vt08, where no getty is running anyway.

Additional info:
* lightdm 1:1.14.0-2

Steps to reproduce:
- Log user into X session.
- Optionally log user in on vt02.
- Invoke «dm-tool lock».
- This starts an X display on vt02, in some instances breaking the getty or shell running there.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Thursday, 13 October 2016, 13:07 GMT
Reason for closing:  Upstream
Comment by Hermann Zahnweh (eigengrau) - Friday, 15 May 2015, 10:29 GMT
I’ve had a further look, and it turns out that not only is the lock screen started on the next VT, but for every user that logs in (e. g., when switching seats), a new VT is used. So this would speak in favor of option 2, namely starting lightdm on a VT that is above any VTs where a getty runs.
Comment by Maxime Gauduin (Alucryd) - Monday, 18 May 2015, 12:03 GMT
GDM does the same, but at least it's smart enough to check if the VT is used and switches to the next when it is. Reverting to VT 7.
Comment by Balló György (City-busz) - Friday, 31 July 2015, 22:47 GMT
I reported this problem to upstream:
https://bugs.launchpad.net/lightdm/+bug/1480479

SDDM has the same problem:
https://github.com/sddm/sddm/issues/446
Comment by Balló György (City-busz) - Wednesday, 12 October 2016, 17:15 GMT
It looks like upstream is not interested in fixing this bug, so it's fine to use VT 7.

Loading...