← Back to team overview

ubuntu-multiseat team mailing list archive

[Bug 1190581] Re: Support logind's automatic multiseat feature

 

I've started writing some code to implement automatic multiseat support
in LightDM [1], largely based on GDM implementation of the feature.
After several tries, I've got this state, which is a little bit well
written, but still incomplete.

I'll really like your feedback about this branch. At the moment, I can
list the following issues:

* Some login1-related code was introduced, and login1.h was #included,
in lightdm.c itself. Is this OK? Should this code be moved elsewhere?

* We need to implement properly the functions add_login1_seat() and
remove_login1_seat() declared in lightdm.c.

* When loading initial seat list from logind (by calling
login1_sync_seats()), we always get at least seat0, which may conflict
with LightDM property "start-default-seat", so we may end up with two
seat0 seats registered in LightDM (one triggered by start-default-seat,
and another triggered by login1_sync_seats()). Which is the preferred
way to prevent this conflict?

* Currently, callback functions for logind signals SeatNew() and
SeatRemoved() should be implemented outside login1.c. Do you agree?

-- 
You received this bug notification because you are a member of Ubuntu
Multiseat, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1190581

Title:
  Support logind's automatic multiseat feature

Status in Light Display Manager:
  Triaged
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