From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Inital updates for GNOME 40
Date: Sat, 03 Apr 2021 11:28:47 +0200 [thread overview]
Message-ID: <20210403092847.eGz9iiKRY19A5gHUxLacW7aql3IwzZ8Ppy0V0S7xcu0@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: 687 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/29959#issuecomment-812840140
Comment:
I have been running GNOME 40 on my computer for a week (updated templates are in my fork's master branch), but there have been some problems:
* the shell crashed 2 times, I don't have a backtrace yet
* every workspace preview on top of the screen shows preview of the same workspace from my secondary monitor
* I had to add a small sleep to the gdm service on one of my computers, because elogind was not starting fast enough. sv check elogind in the service should fix this.
* gnome-control-center should have libhandy1-devel in makedepends
next prev parent reply other threads:[~2021-04-03 9:28 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 [this message]
2021-04-03 12:21 ` st3r4g
2021-04-03 13:11 ` ericonr
2021-04-03 13:29 ` paper42
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=20210403092847.eGz9iiKRY19A5gHUxLacW7aql3IwzZ8Ppy0V0S7xcu0@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).