From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 52786@debbugs.gnu.org
Subject: bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway
Date: Sat, 1 Jan 2022 12:47:04 +0100 [thread overview]
Message-ID: <20220101114704.sbq3bk3gvebrus65@pelzflorian.localdomain> (raw)
In-Reply-To: <20211228153523.abeersugniwcjfvz@pelzflorian.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
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
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: TEST-elogind-Watch-PID-file.patch --]
[-- Type: text/plain; charset=utf-8, Size: 1389 bytes --]
From: Florian Pelz <pelzflorian@pelzflorian.de>
Date: Sat, 1 Jan 2022 12:17:14 +0100
Subject: [PATCH] TEST elogind: Watch PID file.
* gnu/services/desktop.scm (elogind-shepherd-service): Set #:pid-file.
---
gnu/services/desktop.scm | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/gnu/services/desktop.scm b/gnu/services/desktop.scm
index c6761ca784..fc5617c046 100644
--- a/gnu/services/desktop.scm
+++ b/gnu/services/desktop.scm
@@ -13,6 +13,7 @@
;;; Copyright © 2020 Tobias Geerinckx-Rice <me@tobias.gr>
;;; Copyright © 2020 Reza Alizadeh Majd <r.majd@pantherx.org>
;;; Copyright © 2021 Brice Waegeneire <brice@waegenei.re>
+;;; Copyright © 2022 Florian Pelz <pelzflorian@pelzflorian.de>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -731,7 +732,9 @@ (define (elogind-shepherd-service config)
#:environment-variables
(list (string-append "ELOGIND_CONF_FILE="
#$(elogind-configuration-file
- config)))))
+ config)))
+ ;; The PID path from elogind's package definition:
+ #:pid-file "/run/systemd/elogind.pid"))
(stop #~(make-kill-destructor)))))
(define elogind-service-type
base-commit: 87624540b486d710749ad00ef5aa427a9e5c1d0c
--
2.34.0
next prev parent reply other threads:[~2022-01-01 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 8:41 bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway pelzflorian (Florian Pelz)
2021-12-28 15:35 ` pelzflorian (Florian Pelz)
2022-01-01 11:47 ` pelzflorian (Florian Pelz) [this message]
2022-01-10 17:16 ` pelzflorian (Florian Pelz)
2022-06-22 8:59 ` pelzflorian (Florian Pelz)
2022-06-22 12:26 ` Josselin Poiret via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220101114704.sbq3bk3gvebrus65@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=52786@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).