unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
	Ricardo Wurmus <rekado@elephly.net>
Cc: 36924@debbugs.gnu.org
Subject: bug#36924: GDM, GNOME Shell, etc. break when there are stale caches
Date: Wed, 23 Mar 2022 23:14:07 +0100	[thread overview]
Message-ID: <86wngkwc40.fsf@gmail.com> (raw)
In-Reply-To: <95cef7888b04a157f3ceb0ef40904f88a02c250b.camel@gmail.com>

Hi Maxime and Liliana,

On Wed, 23 Mar 2022 at 13:48, Maxime Devos <maximedevos@telenet.be> wrote:
> zimoun schreef op wo 23-03-2022 om 12:28 [+0100]:

>> Is it still an issue?

> IIRC, I encountered the same symptom (although perhaps with a different
> cause, and I did not know if was caused by upgrades) last time I used
> Guix System, which was in the 2022 or at least 2021, so I think it
> might still be an issue.  Or maybe it has been solved since then.


On Wed, 23 Mar 2022 at 21:22, Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
> Am Mittwoch, dem 23.03.2022 um 12:28 +0100 schrieb zimoun:

>> Is it still an issue?

> If I recall correctly, the offending caches have not been updated
> since, so the short answer is "we don't know".  The files in my
> /var/lib/gdm have some quite old dates, some of them ranging as far
> back as 2019, so I suppose there still exists an issue potential.


Thanks for your feedback.

Hum, do we keep a report open based on « maybe » or « we don’t know » or
« I suppose »?  It is an honest question and not a rhetoric one. :-)

Well, how is this bug report actionable?  Other said, what is missing as
concrete information for closing.

From my understanding of your feedback, the current answer to « Is it
still an issue? » seems « no ».  It does not mean that a bug is not
around – so many bugs are around ;-) – but it means that this bug is not
a blocking issue, again from my understanding.

Could you confirm that the bug is appearing for you?  Else, let close it
and reopen once the bug appears.  WDYT?


Cheers,
simon





  parent reply	other threads:[~2022-03-23 22:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 21:00 fixing GDM + GNOME Shell Ricardo Wurmus
2019-08-05  7:17 ` Efraim Flashner
2019-08-05 14:36   ` bug#36924: " Ricardo Wurmus
2019-08-06 16:12 ` Mark H Weaver
     [not found] ` <87k1bqgtn1.fsf@netris.org>
2019-08-06 18:08   ` Ricardo Wurmus
     [not found]   ` <87sgqexj2k.fsf@elephly.net>
2019-08-08  2:59     ` Timothy Sample
2019-09-12  9:54 ` bug#36924: Mesa/GDM/XFCE Andreas Enge
2019-09-12 11:40   ` Ludovic Courtès
2019-09-16  9:44     ` Andreas Enge
2019-09-16 14:57       ` L p R n d n
2019-12-27  7:25 ` bug#36924: Xfce not starting Andreas Enge
2019-12-30 19:00   ` Ludovic Courtès
2022-03-23 11:28 ` bug#36924: GDM, GNOME Shell, etc. break when there are stale caches zimoun
     [not found]   ` <95cef7888b04a157f3ceb0ef40904f88a02c250b.camel@gmail.com>
2022-03-23 22:14     ` zimoun [this message]
2022-06-23  9:26       ` zimoun
2022-06-23 10:07         ` Ricardo Wurmus
2022-10-08 14:47           ` zimoun
2022-10-08 16:04             ` Liliana Marie Prikler
2022-11-17 22:39             ` Maxim Cournoyer
2022-11-18  7:57               ` zimoun
2022-07-04 20:44 ` Ludovic via web
2022-07-04 21:38 ` reyman via web

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=86wngkwc40.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=36924@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=rekado@elephly.net \
    /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).