GNU bug report logs - #36924
GDM, GNOME Shell, etc. break when there are stale caches

Previous Next

Package: guix;

Reported by: Ricardo Wurmus <rekado <at> elephly.net>

Date: Sun, 4 Aug 2019 21:02:02 UTC

Severity: important

Tags: moreinfo

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ricardo Wurmus <rekado <at> elephly.net>
To: guix-devel <at> gnu.org
Cc: 36924 <at> debbugs.gnu.org
Subject: bug#36924: fixing GDM + GNOME Shell
Date: Sun, 04 Aug 2019 23:00:41 +0200
Hi Guix,

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?

--
Ricardo





This bug report was last modified 2 years and 244 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.