From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Inital updates for GNOME 40
Date: Sat, 03 Apr 2021 15:29:28 +0200 [thread overview]
Message-ID: <20210403132928.dCEIu4wKCbIGeXwzIU2iy26savI6iwhklCg1sFQ-1Q4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29959@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/29959#issuecomment-812865803
Comment:
> The issue with a check script is that docs say dbus activation is an option for elogind :/
>
> I'm not sure how we should solve this.
>
> @paper42 are you on musl or glibc? There might be some useful patches on Alpine.
I have GNOME 40 on 2 computers, one of them is an old thinkpad x220 and the second one is a new Ryzen 7 laptop. Both computers run glibc versions of Void, but only my x220 has this problem. A few months ago I noticed the same thing sometimes happening with gdm 3, so this is not a new bug. Before the elogind service managed to start, elogind was started by gdm, so the runit service kept failing. For some reason even though elogind was running, gdm crashed and I think I remember the logs complaining about elogind, but I am not 100% sure.
next prev parent reply other threads:[~2021-04-03 13:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 22:09 [PR PATCH] Inital updates for GNOME 40 [skip CI] Oreo639
2021-04-02 22:17 ` [PR PATCH] [Updated] Inital updates for GNOME 40 Oreo639
2021-04-02 22:47 ` ericonr
2021-04-02 22:50 ` Oreo639
2021-04-02 22:51 ` [PR PATCH] [Updated] " Oreo639
2021-04-02 22:51 ` Oreo639
2021-04-02 22:52 ` Oreo639
2021-04-02 22:52 ` Oreo639
2021-04-02 22:53 ` Oreo639
2021-04-02 22:54 ` Oreo639
2021-04-03 9:24 ` [PR REVIEW] " paper42
2021-04-03 9:28 ` paper42
2021-04-03 12:21 ` st3r4g
2021-04-03 13:11 ` ericonr
2021-04-03 13:29 ` paper42 [this message]
2021-04-03 16:03 ` [PR REVIEW] " Oreo639
2021-04-03 17:38 ` [PR PATCH] [Updated] " Oreo639
2021-04-03 18:23 ` Oreo639
2021-04-03 18:23 ` [PR PATCH] [Closed]: " Oreo639
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210403132928.dCEIu4wKCbIGeXwzIU2iy26savI6iwhklCg1sFQ-1Q4@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).