Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=974458.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-06-14T08:36:31+00:00 Jonathan wrote: Description of problem: Lightdm doesn't seem to properly support systemd multiseat. The first seat is properly opened on seat0, but lightdm's other seats aren't tied to any of logind's seats Version-Release number of selected component (if applicable): lightdm-1.7.0-2.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1. Set up four seats using udev (I named mine seat-1, seat-2 and seat-3, as well as leaving the default seat0) 1. Configure lightdm to use the four seats 2. Start lightdm.service 3. Run loginctl Actual results: SESSION UID USER SEAT 10 0 root c14 990 lightdm seat0 c16 990 lightdm c17 990 lightdm c18 990 lightdm Expected results: SESSION UID USER SEAT 10 0 root c14 990 lightdm seat0 c16 990 lightdm seat-1 c17 990 lightdm seat-2 c18 990 lightdm seat-3 Additional info: Lightdm does start correctly and does use all four seats, but, because the seats aren't registered correctly with logind, USB devices don't automatically get sent to the right seat. Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/1 ------------------------------------------------------------------------ On 2013-06-14T10:49:55+00:00 Christoph wrote: Shouldn't this go upstream? Looks more like a feature request than a bug. Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/2 ------------------------------------------------------------------------ On 2013-06-14T10:59:51+00:00 Jonathan wrote: Yes, it is actually open at https://bugs.launchpad.net/lightdm/+bug/1190581. I want to use this bug to track its progress in Fedora, but forgot to add the link. Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/3 ------------------------------------------------------------------------ On 2013-06-14T16:48:25+00:00 Christoph wrote: Thanks for bringing this upstream. Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/4 ------------------------------------------------------------------------ On 2014-11-11T14:27:25+00:00 Fedora wrote: lightdm-kde-0.3.2.1-8.fc19, lightdm-gtk-1.8.5-9.fc19, lightdm-1.10.3-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2014-14034/lightdm-kde-0.3.2.1-8.fc19,lightdm-gtk-1.8.5-9.fc19,lightdm-1.10.3-1.fc19 Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/29 ------------------------------------------------------------------------ On 2015-01-09T22:34:31+00:00 Fedora wrote: This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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. Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/34 ------------------------------------------------------------------------ On 2015-01-10T05:54:28+00:00 Jonathan wrote: This has been fixed in the version of lightdm in F20. Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/35 ** Changed in: lightdm (Fedora) Status: Unknown => Invalid ** Changed in: lightdm (Fedora) Importance: Unknown => Undecided -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1190581 Title: Support logind's automatic multiseat feature Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Utopic: Fix Released Status in lightdm package in Fedora: Invalid Bug description: [Impact] LightDM does not use the information provided by logind to support automatic multi-seat setups. We have backported this support from LightDM 1.12 so this functionality can be used in 14.04 LTS. It is disabled by default. [Test Case] 1. Enable multiseat in the LightDM configuration: [LightDM] logind-load-seats=true 2. Start LightDM Expected result: The greeter is shown on both monitors and two sessions can be logged in. Observed result: Currently only one monitor / seat works. [Regression Potential] There is some risk of unrelated code being changed. This has been reduced by the use of regression tests, manual testing and providing this in the Ubuntu Desktop PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
