Hide Forgot
Description of problem: I have a two-seat system. After upgrade to F25 (and modifying lightdm.conf so that it can at even start the X server on both seats), I cannot log in to both seats simultaneously: when one user logs in (no matter on which seat), his name is changed to bold font in the greeter of the other seat. When I select another user (not in the bold font), the password field is disabled (greyed out). When I select the same user which is already logged in on the other seat, the password field is still greyed out, but the "Login" button is changed to "Unlock". Version-Release number of selected component (if applicable): lightdm-1.18.2-1.fc25.x86_64 How reproducible: 100 % on the only multiseat desktop I have :-) Steps to Reproduce: 0. create two local users (e.g user1 and user2) 1. set up a multi-seat desktop: create a seat "seat1", and attach graphics card, mouse and keyboard to this seat (see loginctl man page). 2. set up lightdm, and start it up. 3. on seat0, log in as user1 4. on seat1, try to log in as user2 Actual results: as soon as user1 is logged in on seat0, nobody can login on seat1. Expected results: multiple users should be able to use multi-seat desktop simlutaneously :-) Additional info: My lightdm configuration for multiple seats contains the stock /etc/lightdm/lightdm.conf with the following lines added: [Seat:seat0] xserver-command=X -layout Primary -isolateDevice PCI:0:2:0 -seat seat0 vt7 [Seat:seat1] xserver-command=X -layout Secondary -isolateDevice PCI:1:0:0 -seat seat1 -sharevts vt7 FWIW, I use lightdm GTK greeter and XFCE4 desktop (but the problem is not related to the session selected). This worked in previous versions of Fedora.
FWIW, I managed to work around the problem using autologin. This is not a clean solution, but it shows that the problem is probably only with the login/auth part of the chooser or its pam modules, not in lightdm itself.
OK, I discovered that "loginctl" shows several sessions on seat0. Apparently it does not honor the "vtX" option on the X server command line, and tries to start a new session also on vt1. Removing "vt7" from both xserver-command lines also works around the problem.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.