[Dev] Tizen 3 services: use case for multi user
imran.zaman at intel.com
Wed Sep 10 10:47:37 GMT 2014
Thanks dominig for the wiki page but it does not really answer all the questions which I have asked.
Btw have you guys really tried UserA logged into Seat0 and UserB logged into Seat1 using current weston and it is working in Tizen Common?
To my understanding it is by no means possible with current weston and drm-backend.
Manuel/Dominig, It would be really nice if you can give it a try please.
From: Dev [dev-bounces at lists.tizen.org] on behalf of Kaskinen, Tanu [tanu.kaskinen at intel.com]
Sent: 10 September 2014 12:09
To: dominig.arfoll at fridu.net
Cc: dev at lists.tizen.org
Subject: Re: [Dev] Tizen 3 services: use case for multi user
On Tue, 2014-09-09 at 18:53 +0200, Dominig ar Foll (Intel OTC) wrote:
> Manuel Bachman has added a page on Multi-user Display Management
> Your comments are welcome.
Thanks for the wiki page!
On the multi-user display management page there is this statement:
User sessions are not associated with a particular seat ; nor
I feel that some clarifications are needed for that statement. logind
associates each session with zero or one seat, and last time I checked
this on Common, all sessions are currently assigned to seat0 by default.
Does the statement mean that logind can assign whatever it wants, but we
ignore that? Or do you think that things should be changed so that
logind doesn't assign sessions to any seat? Or does the statement only
mean that sessions are not associated *permanently* with a particular
seat? (I hope it's the last one, but in the rest of this mail, I'll
assume that it's not that.)
What's the rationale behind not associating sessions with seats? I know
we need to support moving running applications between seats, are there
other reasons? Do you perhaps want to allow one session to span multiple
If the motivation is just to be able to move applications between seats,
what do you think of the approach that Jussi has proposed: don't move
single applications, but move entire sessions between seats? This means
that sessions are associated with a seat, but that association can
As a PulseAudio developer, I'm interested in this, because currently
PulseAudio relies on logind's device ACL management to figure out which
sound cards are assigned to the user, and logind's device ACL management
in turn relies on sessions being correctly associated with seats. If we
want to support per-seat sound cards, the existing solution in
PulseAudio should work quite well for that (when the user's session
moves from one seat to another, the set of sound cards assigned to the
user changes automatically). If the sessions aren't correctly associated
with seats at logind level, we'd need some other solution in PulseAudio
to support per-seat sound cards, and currently I don't understand why we
should take that route.
Dev mailing list
Dev at lists.tizen.org
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
More information about the Dev