:: Re: [DNG] [libseat/backend/logind.c…
Página Principal
Delete this message
Reply to this message
Autor: Mark Hindley
Data:  
Para: Андрей Сорокин
CC: dng
Assunto: Re: [DNG] [libseat/backend/logind.c:137] Could not take device: Device or resource busy
Andrey,

Thanks

On Wed, Jul 05, 2023 at 07:52:09AM -0400, Андрей Сорокин wrote:
> I have removed elogind,


That helps reduce some of the uncertainties.

> so seatd only remained of these two, but the problems still present:
> . only one x-session at once,
> . swithching between X and console sessions some times takes away keyboard control -- only reboot helps.
>
> But the errors in the X log file changed:
>
> [    63.315] (II) seatd_libseat init
> [    63.315] (EE) [libseat/backend/seatd.c:308] Could not poll connection: Broken pipe
> [    63.315] (II) [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping


This is the problem. Having failed to open a seat, non of the console switching
or multiple x-sessions is going to work.

Having said that, I am still unable to reproduce this.

Do you have SEATD_SOCK set in the environment (you shouldn't)

I will have to do some more testing to try and replicate.

> So, *any* ideas are welcome. For i do not know what to do with this and
> suppose "Daedalus" can not be used in this configuration as this is a fresh
> installation and only DM was removed since X was also chosen among other
> install options to be installed on the system.


I am running daedalus like this as my daily driver (sway and xorg), so it can
and should work fine.

Mark