Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance!
-- You received this bug notification because you are a member of Ubuntu Touch seeded 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: Triaged Status in “lightdm” source package in Utopic: Fix Released Status in “lightdm” package in Fedora: Unknown Bug description: Now that initial logind support https://bugs.launchpad.net/lightdm/+bug/930488 was released for LightDM, I'm opening this bug to request a step further: provide support to logind's automatic multiseat feature. I have absolutely no experience with D-Bus interfaces, but it seems that LightDM has its own D-Bus interface for seat management, so I don't know what would be better: replace it with logind D-Bus interface (if logind is present) or chaining both (e.g.: a logind's SeatNew D-Bus signal should trigger LightDM's SeatAdded D-Bus signal). Does it make sense? To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
