> Unfortunately it isn't that simple; thin clients also run server sessions with different DISPLAYs, and even a simple ssh -X gives a different display. There's x-input related code in development (in xorg, not in epoptes) which should make handling multiseat systems easier.
Sorry if I'm wrong (I've never used LTSP), but in thin clients' context, can Epoptes identify, e.g., the MAC address of the network interface of each client? If so, I think we could use this information to distinguish multiseat from other multi-display contexts: 1. If we have multiple displays sharing a single network interface (indentified by MAC address), then guess we have multiseat. 2. Otherwise, guess we have other multi-display context( e.g., thin clients). Anyway, I'm starting a fork of Epoptes in lp:~oiteam/epoptes/trunk to study the code and try developing some multiseat support. -- You received this bug notification because you are a member of Epoptes Developers, which is the registrant for Epoptes. https://bugs.launchpad.net/bugs/980141 Title: some more suggestions for dealing with multiseat environments Status in Epoptes: New Bug description: I'd like to suggest some changes in Epoptes to work better with multiseat environments: 1. Add label options "Computer:Display (User)" and "Computer:Display" to "Labels" menu. 2. When lauching "Root, locally" terminals for several seats simultaneously, launch just one terminal for each computer, not one for each user. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/980141/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
