[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking s
From: |
pelzflorian (Florian Pelz) |
Subject: |
bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway |
Date: |
Sat, 25 Dec 2021 09:41:09 +0100 |
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
rock64-config.scm
Description: Lotus Screencam
- bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway,
pelzflorian (Florian Pelz) <=