From: Julien Lepiller <julien@lepiller.eu>
To: 40116@debbugs.gnu.org, zimon.toutoune@gmail.com,
luis.felipe.la@protonmail.com
Cc: 41215@debbugs.gnu.org, sirgazil@zoho.com
Subject: bug#40116: bug#41215: memory leak in gnome-shell
Date: Wed, 23 Mar 2022 17:00:54 +0100 [thread overview]
Message-ID: <C4582435-0768-469F-8DB1-3F52B1B1D59F@lepiller.eu> (raw)
In-Reply-To: <CAJ3okZ1_KNLF+Z_JNaQ9rQ14GTEE9cvhXZ_rvG77Jw-WuvXX0g@mail.gmail.com>
On March 23, 2022 4:46:53 PM GMT+01:00, zimoun <zimon.toutoune@gmail.com> wrote:
>Hi Luis,
>
>On Wed, 23 Mar 2022 at 16:13, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
>> So, if Julien and Arne, for example, don't experience the issue anymore, I'm happy to close the issue.
>
>Let wait 15 days and if no answer, let assume it is not an issue and
>close it. :-)
>
>Thank you for your feedback.
>
>Cheers,
>simon
>
>
>
I haven't had that issue in a while, I tgink we can close.
next prev parent reply other threads:[~2022-03-23 16:32 UTC|newest]
Thread overview: 16+ 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 ` bug#41215: memory leak in gnome-shell zimoun
2022-03-23 15:13 ` Luis Felipe via Bug reports for GNU Guix
2022-03-23 15:46 ` bug#40116: " zimoun
2022-03-23 16:00 ` Julien Lepiller [this message]
2022-04-09 15:19 ` bug#40116: GDM: Memory leak in .gnome-shell-real process Luis Felipe 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=C4582435-0768-469F-8DB1-3F52B1B1D59F@lepiller.eu \
--to=julien@lepiller.eu \
--cc=40116@debbugs.gnu.org \
--cc=41215@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=sirgazil@zoho.com \
--cc=zimon.toutoune@gmail.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).