all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, bug-guix@gnu.org
Subject: Re: fixing GDM + GNOME Shell
Date: Mon, 5 Aug 2019 10:17:19 +0300	[thread overview]
Message-ID: <20190805071719.GB15819@E2140> (raw)
In-Reply-To: <87tvawzlvq.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

On Sun, Aug 04, 2019 at 11:00:41PM +0200, Ricardo Wurmus wrote:
> 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.

For this one can we create a single-shot service that, on reconfigure or
boot, removes this directory and recreates it? In fact, it seems this is
basically what Debian does¹.

> 
> 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 part seems a little harder to automate. /etc/skel is only sourced
when a user is created, so it's hard to make sweeping changes to help
people in this case, if they even want automated help. I'm guessing
making .cache/gdm(?) read-only would create other issues.

> 
> 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?

Modify the logout scripts to remove a users' .cache file seems extreme.
Some of the other options, such as removing and recreating directories
would address other issues we've had (such as /var/cache/fontconfig).


¹ https://sources.debian.org/src/gdm3/3.30.2-3/debian/gdm3.postinst/#L76

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-08-05  7:17 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 [this message]
2019-08-05 14:36   ` bug#36924: " Ricardo Wurmus
2019-08-05 14:36   ` 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 ` bug#36924: GDM, GNOME Shell, etc. break when there are stale caches zimoun
2022-03-23 12:48   ` 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=20190805071719.GB15819@E2140 \
    --to=efraim@flashner.co.il \
    --cc=bug-guix@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.