From: zimoun <zimon.toutoune@gmail.com>
To: sirgazil <sirgazil@zoho.com>
Cc: 41215@debbugs.gnu.org, 40116@debbugs.gnu.org
Subject: bug#41215: memory leak in gnome-shell
Date: Wed, 23 Mar 2022 12:35:47 +0100 [thread overview]
Message-ID: <86wngkzyss.fsf@gmail.com> (raw)
In-Reply-To: <170ee024512.c9ac6ac476703.6325608537898017895@zoho.com> (sirgazil@zoho.com's message of "Wed, 18 Mar 2020 09:18:11 -0500")
Hi,
On Wed, 18 Mar 2020 at 09:18, sirgazil <sirgazil@zoho.com> wrote:
> I can't use GNOME anymore because of the problem I explained in the following thread:
[...]
> $ guix describe
> Generation 61 Mar 15 2020 08:44:39 (current)
What is the status of this old bug [1]? Especially since the last merge
of core-updates.
1: <http://issues.guix.gnu.org/issue/41215>
Cheers,
simon
next prev parent reply other threads:[~2022-03-23 12:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 14:18 bug#40116: GDM: Memory leak in .gnome-shell-real process sirgazil via Bug reports for GNU Guix
2020-03-18 15:09 ` Ludovic Courtès
2020-03-18 16:10 ` sirgazil via Bug reports for GNU Guix
2020-03-29 16:08 ` Jan Nieuwenhuizen
2020-03-29 16:10 ` Jan Nieuwenhuizen
2020-03-18 16:09 ` Julien Lepiller
2020-03-19 18:13 ` sirgazil via Bug reports for GNU Guix
2020-03-22 0:38 ` sirgazil via Bug reports for GNU Guix
2020-03-23 17:01 ` sirgazil via Bug reports for GNU Guix
2020-03-24 13:15 ` sirgazil via Bug reports for GNU Guix
2020-10-01 15:56 ` Luis Felipe via Bug reports for GNU Guix
2022-03-23 11:35 ` zimoun [this message]
2022-03-23 15:13 ` bug#41215: memory leak in gnome-shell Luis Felipe via Bug reports for GNU Guix
2022-03-23 15:46 ` bug#40116: " zimoun
2022-03-23 16:00 ` Julien Lepiller
2022-04-09 15:19 ` bug#40116: GDM: Memory leak in .gnome-shell-real process Luis Felipe via Bug reports for GNU Guix
-- strict thread matches above, loose matches on Subject: below --
2020-05-12 19:47 bug#41215: memory leak in gnome-shell Arne Babenhauserheide
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=86wngkzyss.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=40116@debbugs.gnu.org \
--cc=41215@debbugs.gnu.org \
--cc=sirgazil@zoho.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.
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).