From: Aiko Kyle <aikokyle@gmail.com>
To: 51970@debbugs.gnu.org
Subject: [bug#51970] [PATCH core-updates-frozen 0/2] wlroots now uses libseat
Date: Sat, 1 Jan 2022 21:32:39 -0700 [thread overview]
Message-ID: <CAPWcbYGNr5hu3ZNOJ3wPP8xbBBt-66rZ4bh+yM9VTvMGNs75bQ@mail.gmail.com> (raw)
In-Reply-To: <20211119110454.4265-1-dev@jpoiret.xyz>
I was wondering if sway still works for you? Sometime between guix
v1.3.0 and now sway broke for me and I think it may have to do with
this update to sway requiring seatd. When I try run sway I get the
error:
00:00:00.007 [ERROR] [wlr] [libseat] [libseat/backend/seatd.c:78]
Could not connect to socket /run/seatd.sock: No such file or directory
00:00:00.017 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:267]
Could not activate session: Interactive authentication required.
00:00:00.017 [ERROR] [wlr] [libseat] [libseat/libseat.c:73] No backend
was able to open a seat
00:00:00.017 [ERROR] [wlr] [backend/session/session.c:84] Unable to
create seat: Function not implemented
00:00:00.017 [ERROR] [wlr] [backend/session/session.c:218] Failed to
load session backend
00:00:00.017 [ERROR] [wlr] [backend/backend.c:353] Failed to start a DRM session
00:00:00.017 [ERROR] [sway/server.c:53] Unable to create backend
prev parent reply other threads:[~2022-01-02 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 11:04 [bug#51970] [PATCH core-updates-frozen 0/2] wlroots now uses libseat Josselin Poiret via Guix-patches via
2021-11-19 11:08 ` [bug#51970] [PATCH core-updates-frozen 1/2] gnu: seatd: Make elogind a propagated input Josselin Poiret via Guix-patches via
2021-11-19 11:08 ` [bug#51970] [PATCH core-updates-frozen 2/2] gnu: wlroots: Remove unneeded elogind dependency Josselin Poiret via Guix-patches via
2021-11-19 13:22 ` bug#51970: [PATCH core-updates-frozen 0/2] wlroots now uses libseat Ludovic Courtès
2022-01-02 4:32 ` Aiko Kyle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPWcbYGNr5hu3ZNOJ3wPP8xbBBt-66rZ4bh+yM9VTvMGNs75bQ@mail.gmail.com \
--to=aikokyle@gmail.com \
--cc=51970@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.