From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Cc: bug-guix@gnu.org
Subject: fixing GDM + GNOME Shell
Date: Sun, 04 Aug 2019 23:00:41 +0200 [thread overview]
Message-ID: <87tvawzlvq.fsf@elephly.net> (raw)
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
next reply other threads:[~2019-08-04 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 21:00 Ricardo Wurmus [this message]
2019-08-05 7:17 ` fixing GDM + GNOME Shell 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
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=87tvawzlvq.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=bug-guix@gnu.org \
--cc=guix-devel@gnu.org \
/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).