From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, 36924@debbugs.gnu.org
Subject: bug#36924: fixing GDM + GNOME Shell
Date: Tue, 06 Aug 2019 20:08:51 +0200 [thread overview]
Message-ID: <87sgqexj2k.fsf__38752.8749111638$1565115018$gmane$org@elephly.net> (raw)
In-Reply-To: <87k1bqgtn1.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> It's interesting that I've never run into this problem, not even once,
> in all my years of running GNOME on Guix systems. Since recently
> reverting to mostly using GNOME under X and GDM (whereas for a while I
> was mostly launching GNOME manually under Wayland), I've run into some
> other problems, e.g. GDM suspending my system automatically, sometimes
> immediately after logging out, but I've *never* had to remove my caches.
Interesting.
> I wonder if this is related to my use of Btrfs instead of Ext4. Whereas
> system crashes cause file system corruptions under Ext4 (usually in the
> form of some files being left empty after a crash), I've never seen any
> evidence of corruption from crashes under Btrfs.
I haven’t had a system crash on this machine. I didn’t use it for a
month, upgraded, rebooted, and then had GDM + GNOME Shell problems.
--
Ricardo
next prev parent reply other threads:[~2019-08-06 18:10 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 [this message]
[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='87sgqexj2k.fsf__38752.8749111638$1565115018$gmane$org@elephly.net' \
--to=rekado@elephly.net \
--cc=36924@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).