I've added test support for the logind seat API in revision 2023. I'm working on making a Login1Service class.
Since the seats are automatically populated from logind we can probably drop the xdg-seat configuration option (there's no case where a user should set it). The reason for the "Seat:" prefix is we just don't know what seat names might be used in the future. If a name conflicted with a LightDM section then we'd have problems. So I think it is safest to keep the prefix there. I think it will end up unlikely for users to need to make per seat configuration other than setting things in [SeatDefaults]. The only case I can come up with is when you might want to set one seat for the sysadmin and this would probably be done with: [SeatDefaults] # Options for the n seats connected to this system [Seat:seat0] # Options for the sysadmin -- https://code.launchpad.net/~ubuntu-multiseat/lightdm/automatic-multiseat/+merge/229682 Your team Ubuntu Multiseat is subscribed to branch lp:~ubuntu-multiseat/lightdm/automatic-multiseat. -- Mailing list: https://launchpad.net/~ubuntu-multiseat Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-multiseat More help : https://help.launchpad.net/ListHelp
