From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, 36924@debbugs.gnu.org
Subject: bug#36924: GDM, GNOME Shell, etc. break when there are stale caches
Date: Wed, 23 Mar 2022 12:28:57 +0100 [thread overview]
Message-ID: <867d8k29hi.fsf@gmail.com> (raw)
In-Reply-To: <87tvawzlvq.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 04 Aug 2019 23:00:41 +0200")
Hi,
This old bug [1] is there since a long time. What is the status?
1: <http://issues.guix.gnu.org/issue/36924>
On Sun, 04 Aug 2019 at 23:00, Ricardo Wurmus <rekado@elephly.net> wrote:
> Today I again couldn’t log into my workstation after upgrading the
> system. I’m using GDM + GNOME Shell.
>
> At first GDM wouldn’t start. I knew what to do: remove /var/lib/gdm,
> because some state must have accumulated there.
>
> GDM came up after a reboot, but I still couldn’t log in. Instead I was
> thrown back to the login screen without any error message. I looked in
> ~/.cache/gdm/session.log for information, but it only told me that
> gnome-shell was killed. Thanks.
>
> After removing both .local/share and .cache out of the way I could log
> in again.
>
> This happens whenever I upgrade the system. This makes the system
> rather frustrating to use. I don’t know if booting into an older system
> generation would result in the same problem, but my guess is that it
> would because both GDM and GNOME Shell appear to be leaving some binary
> files behind that cause different versions to crash unceremoneously.
>
> What can we do to make GDM and GNOME Shell more reliable?
Is it still an issue?
Cheers,
simon
next prev parent reply other threads:[~2022-03-23 11:54 UTC|newest]
Thread overview: 28+ 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 ` Ricardo Wurmus
2019-08-05 14:36 ` bug#36924: " Ricardo Wurmus
2019-08-06 16:12 ` Mark H Weaver
2019-08-06 18:08 ` bug#36924: " Ricardo Wurmus
2019-08-06 18:08 ` Ricardo Wurmus
2019-08-08 2:59 ` Timothy Sample
2019-08-08 2:59 ` bug#36924: " Timothy Sample
2019-08-06 16:12 ` Mark H Weaver
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 ` zimoun [this message]
2022-03-23 12:48 ` bug#36924: GDM, GNOME Shell, etc. break when there are stale caches Maxime Devos
2022-03-23 20:22 ` Liliana Marie Prikler
2022-03-23 22:14 ` zimoun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=867d8k29hi.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=36924@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.