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, 25 Dec 2021 09:41:09 +0100 [thread overview]
Message-ID: <20211225083537.7tj3n7gxf5wexlip@pelzflorian.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On a ROCK64 system-on-chip, herd start elogind fails. This is guix
commit 87624540b486d710749ad00ef5aa427a9e5c1d0c after the
core-updates-frozen merge. This breaks sway for me, which I start
from the Linux console.
But if I
Revert "gnu: elogind: Update to 246.10."
This reverts commit a0bf66ab9432675f86095d9a2533d7b80f58a668.
then it is working again.
(Actually on reconfigure in order to build python-dbusmock I also need
to add #:tests? #f to python-dbusmock.)
I shall try out if updating to
commit 488f1c589df00e802163af534294d93372e5c025
services: dbus: Wait 1 minute for elogind to get ready.
helps, but the failure is immediate, so that is probably unrelated.
If it does not help, I will bisect the elogind versions.
Attached is my config. (Note that the setup is unusual; to boot, I
copy all files referenced in /boot/extlinux/extlinux.conf from
/gnu/store to /boot/gnu/store.)
Regards,
Florian
[-- Attachment #2: rock64-config.scm --]
[-- Type: application/vnd.lotus-screencam, Size: 3390 bytes --]
next reply other threads:[~2021-12-25 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 8:41 pelzflorian (Florian Pelz) [this message]
2021-12-28 15:35 ` bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway pelzflorian (Florian Pelz)
2022-01-01 11:47 ` pelzflorian (Florian Pelz)
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=20211225083537.7tj3n7gxf5wexlip@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).