bug#52786: closed ([aarch64] elogind 246.10 fails to start on ROCK64, breaking sway)

[GNU bug Tracking System]

Your message dated Wed, 22 Jun 2022 10:59:50 +0200
with message-id <20220622085950.4s2kpqkft4khlegk@pelzflorian.localdomain>
and subject line Re: bug#52786: [aarch64] elogind 246.10 fails to start on 
ROCK64, breaking sway
has caused the debbugs.gnu.org bug report #52786,
regarding [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
52786: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52786
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [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

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway
>
>
>
>
> Date: 
>
> Wed, 22 Jun 2022 10:59:50 +0200
>
>
>
>
> On Mon, Jan 10, 2022 at 06:16:03PM +0100, pelzflorian (Florian Pelz) wrote:
> > Reverting elogind commit 150d7b05074f16db70a2872765edbb39066d80af
> > makes sway start again.  See attached patch.  We could graft elogind
> > or put it on core-updates, but I have not yet properly tested nor
> > understood.  I will test and try understanding now.
>
> Closing, because:
>
> * muradm added seatd-service-type and using (service
>   seatd-service-type) in lieu of (elogind-service) works.  It looks
>   like a better (?) workaround than making elogind work.
>
> * I have not understood and do not plan to debug further.  Maybe that
>   I can no longer start sway by typing sway in a virtual terminal is
>   even a deliberate change in logind, but then again I don’t see it on
>   x86_64.
>
> Regards,
> Florian
>
>
> --- End Message ---