On Tue, Dec 28, 2021 at 04:35:23PM +0100, pelzflorian (Florian Pelz) wrote:
> elogind commit 7db52c01ed07f543f8272ea9a726cb542e771595 is the first
> elogind version that does not launch, but it is too entangled to
> simply revert.  I will take another look tomorrow.

This was a dead end.  With 7db52c01ed07f543f8272ea9a726cb542e771595,
elogind did actually launch but shepherd did not recognize it.  The
attached patch was required, but it does not make a difference for
starting sway.  (Neither is it an alternative fix for
<https://issues.guix.gnu.org/issue/52051>.)

Elogind’s entire v246-stable branch does not run sway anymore on
ROCK64.  I don’t think bisecting is a good way to find the cause.

The sway errors are:

00:00:00.013 [ERROR] [wlr] [libseat] [libseat/backend/seatd.c:78] Could not connect to socket /run/seatd.sock: No such file or directory
00:00:00.031 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:267] Could not activate session: Action org.freedesktop.login1.chvt is not registered
00:00:00.031 [ERROR] [wlr] [libseat] [libseat/libseat.c:73] No backend was able to open a seat
00:00:00.031 [ERROR] [wlr] [backend/session/session.c:84] Unable to create seat: Function not implemented
00:00:00.031 [ERROR] [wlr] [backend/session/session.c:218] Failed to load session backend
00:00:00.031 [ERROR] [wlr] [backend/backend.c:353] Failed to start a DRM session
00:00:00.031 [ERROR] [sway/server.c:53] Unable to create backend

The first line seems harmless and is also printed on old elogind
before sway starts.

I will try to actually understand what is happening.

Regards,
Florian