← Back to team overview

epoptes team mailing list archive

[Bug 980141] Re: some more suggestions for dealing with multiseat environments

 

> The most common way to identify a seat in a multiseat network is by
its hostname/IP and by the value of DISPLAY variable for the Xorg
instance running in that seat.

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.

> Both of them gave me the same value (DISPLAY = :0), so they are
running on the same seat.

That's because epoptes doesn't yet handle multiseat correctly; they
should be different. It's also the reason why broadcasting didn't work
for you out of the box and you had to make that one-line change in
gui.py.

> Both of them gave me the same value (DISPLAY = :0), so they are
running on the same seat.

If you select a user in epoptes and run "killall firefox" (from the
execute dialog, without sudo), it will only kill processes for that
user.

> I will study epoptes code and try to contribute some patches.

Your patches will be welcome, of course as long as they don't break
anything for other use cases. And once multiseat support in xorg
matures, the code for handling multiseat systems will probably become
more straightforward. :)

-- 
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


References