Hi.

> That was an excessive number of quotation marks. :)

Thank you! :^)

> > So, question is on your plans with "MultiSeat": do you plan to
> > accomplish "MultiSeat"
> 
> What is your multi-seat use-case? The plan is to support multi-seat
> in seatd, but due to how rare multi-seat uses are it has not had the 
> highest priority. Knowing about needs in the area would be useful
> though.

For me it is: several users may have long running x-applications at the
same time, simply, locking their sessions, using expensive hardware.
 
> > if "yes" then when do you plan to accomplish "MultiSeat"?
> As a general rule of thumb, unpaid work has no estimates and no 
> committed schedules/plans. It happens when it happens.

Thank you for the answer.
 
> > do not know why developers made such a decision, probably because
> > with "ELoginD" it is absolutely became impossible OR wanted also to
> > get rid if it
> 
> Presumably the latter, although you might be able to reinstall it 
> locally should you so desire.

I have tried that, but that gave no input devices to work -- just like
when seatd hangs x-session and i have to release the devices from the
x-server -- then all new x-sessions start without input devices and
therefore only reboot helps.


Andrey.

On 8/21/23 09:13, Андрей Сорокин wrote:
> For me it is: several users may have long running x-applications at the 
> same time, simply, locking their sessions, using expensive hardware.

Just to clarify, multi-seat would basically be several office desks 
(screens, keyboards, mice) powered by a single machine, each user having 
their own display, gpu(!), keyboard and mouse used to run their own X or 
Wayland session in parallel with and entirely separate from everyone else.

Multi-session would be 1 office desk with multiple users, where all 
users can be logged in simultaneously but only one session is active and 
shown (the user who is currently at the desk) with the rest being in the 
background, waiting to be activated.

Based on your description I am not sure if you mean multi-seat or 
multi-session. We support multi-session, multi-seat requires more work.

> I have tried that, but that gave no input devices to work -- just like
> when seatd hangs x-session and i have to release the devices from the
> x-server -- then all new x-sessions start without input devices and
> therefore only reboot helps.

seatd indeed will only let 1 session on the seat be active, the rest 
have their devices forcibly revoked and given back only when they are 
activated (multi-session). You will not get multi-seat from seatd yet, 
but you should not need to reboot to get back in control. Maybe ask the 
Devuan team or the people contributing the Devuan Xorg seatd patch.