Hello,
"pelzflorian (Florian Pelz)" writes:
> * 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.
Just FTR, seatd is a light alternative to the seat management part of
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
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.
Regards,
FlorianFrom: Florian Pelz
Date: Mon
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 7db5
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.
On Sat, Dec 25, 2021 at 09:41:09AM +0100, pelzflorian (Florian Pelz) wrote:
> I shall try out if updating to
>
>
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 comm
