From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 52786-done@debbugs.gnu.org
Subject: bug#52786: [aarch64] elogind 246.10 fails to start on ROCK64, breaking sway
Date: Wed, 22 Jun 2022 10:59:50 +0200 [thread overview]
Message-ID: <20220622085950.4s2kpqkft4khlegk@pelzflorian.localdomain> (raw)
In-Reply-To: <20220110171603.6ihwny2xf5xaaa7g@pelzflorian.localdomain>
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
next prev parent reply other threads:[~2022-06-22 9:00 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)
2022-01-10 17:16 ` pelzflorian (Florian Pelz)
2022-06-22 8:59 ` pelzflorian (Florian Pelz) [this message]
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=20220622085950.4s2kpqkft4khlegk@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=52786-done@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).