From: sirgazil <sirgazil@zoho.com>
To: "sirgazil" <sirgazil@zoho.com>
Cc: "Jack Hill" <jackhill@jackhill.us>,
"Marius Bakke" <mbakke@fastmail.com>,
"guix-devel" <guix-devel@gnu.org>,
"help-guix" <help-guix@gnu.org>
Subject: Re: core-updates call for testing
Date: Sat, 25 Apr 2020 18:13:30 +0000 [thread overview]
Message-ID: <171b28b5db3.b7f8250413979.384803412674883512@zoho.com> (raw)
In-Reply-To: <171b1831b1a.115b6d00411708.1618548316460064982@zoho.com>
---- On Sat, 25 Apr 2020 13:24:51 +0000 sirgazil <sirgazil@zoho.com> wrote ----
> ---- On Sat, 25 Apr 2020 03:02:23 +0000 Jack Hill <jackhill@jackhill.us> wrote ----
> > On Fri, 24 Apr 2020, Marius Bakke wrote:
> >
> > > The "core-updates" branch is ready for testing!
> >
> > Hi,
> >
> > I've reconfigured my user profile and system from the core-updates branch.
> > I use a GNOME desktop session. However, I don't use too many fancy
> > features. I mostly use GNOME-Terminal, GNOME-Web, and Emacs. I also use
> > some GNOME shell extensions.
> >
> > I have not done extensive testing, but so far the desktop itself seems to
> > be in working order, including cursory use of the GNOME settings dialog.
>
> Same here. So far, things are working normally. I see the same bugs I've reported against GNOME 3.32.2. Sadly, the leak reported in https://issues.guix.gnu.org/40116 is still there.
By the way, it would be great if someone could review this patch: https://issues.guix.gnu.org/issue/39069, which is supposed to fix bugs like this one: https://issues.guix.gnu.org/issue/40686, which have been around for a long time and make the GNOME experience unsatisfying from day one.
next prev parent reply other threads:[~2020-04-25 18:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 23:24 core-updates call for testing Marius Bakke
2020-04-24 3:20 ` sirgazil
2020-04-24 12:58 ` sirgazil
2020-04-24 16:25 ` Marius Bakke
2020-04-24 16:54 ` Gábor Boskovits
2020-04-24 19:29 ` sirgazil
2020-04-24 18:08 ` sirgazil
2020-04-24 21:52 ` Marius Bakke
2020-04-24 22:42 ` sirgazil
2020-04-24 18:46 ` sirgazil
2020-04-24 14:40 ` Jack Hill
2020-04-24 20:06 ` Jack Hill
2020-04-25 3:02 ` Jack Hill
2020-04-25 13:24 ` sirgazil
2020-04-25 18:13 ` sirgazil [this message]
2020-04-29 11:31 ` Ricardo Wurmus
2020-04-25 18:36 ` sirgazil
2020-04-25 21:19 ` Jack Hill
2020-04-25 21:54 ` sirgazil
2020-04-27 22:09 ` Jack Hill
2020-04-29 6:17 ` Ricardo Wurmus
2020-04-25 18:06 ` Leo Famulari
2020-04-28 13:17 ` Marius Bakke
2020-04-28 12:46 ` Efraim Flashner
2020-04-28 13:12 ` Marius Bakke
2020-05-04 14:51 ` Timothy Sample
2020-05-04 15:32 ` Marius Bakke
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=171b28b5db3.b7f8250413979.384803412674883512@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=jackhill@jackhill.us \
--cc=mbakke@fastmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).