logind: doesn't monitor seats if started with VT#171
Conversation
multiple seats doesn't work when VT are enabled, so don't try to monitor seats in this case. This fixes the following error when starting sway from kmscon: $ /usr/bin/kmscon-launch-gui /usr/bin/sway 00:00:00.001 [ERROR] [wlr] [libseat] [libseat/libseat.c:79] No backend was able to open a seat 00:00:00.001 [ERROR] [wlr] [backend/session/session.c:83] Unable to create seat: Function not implemented 00:00:00.001 [ERROR] [wlr] [backend/session/session.c:248] Failed to load session backend 00:00:00.001 [ERROR] [wlr] [backend/backend.c:79] Failed to start a session 00:00:00.001 [ERROR] [wlr] [backend/backend.c:407] Failed to start a DRM session 00:00:00.001 [ERROR] [sway/server.c:228] Unable to create backend Signed-off-by: Jocelyn Falempe <[email protected]>
|
How do you reproduce this? Also the errors from wlroots seem to not even be related to seats. In wlroots the error is from the libseat_session_init function which calls the libseat_open_seat function in libseat. It seems like libseat has bad naming conventions for these functions. Just thinking about it, it doesn't make any sense why a wayland compositor would need to create a seat. It would be useful to reproduce this with the debug log level for libseat, but it seems like the only way to do this is to recompile wlroots. |
|
My steps to reproduce this:
If I have only one kmscon instance on tty2, there is no errors, but when I have two, I get this libseat errors. I'm also wondering if the issue is not on logind or libseat, because currently kmscon doesn't register seats, it only monitor seat creation/deletion. |
2 participants
multiple seats doesn't work when VT are enabled, so don't try to monitor seats in this case.
This fixes the following error when starting sway from kmscon: