From: Ricardo Wurmus <rekado@elephly.net>
To: Kei Kebreau <kkebreau@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: 'core-updates' Q4 2019
Date: Fri, 18 Oct 2019 05:08:20 +0200 [thread overview]
Message-ID: <87a79ylpi3.fsf@elephly.net> (raw)
In-Reply-To: <87k192es4n.fsf@posteo.net>
Kei Kebreau <kkebreau@posteo.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Kei Kebreau <kkebreau@posteo.net> writes:
>>
>>> I have news! The good part is that I got 54 packages to build on top of
>>> master. The bad part is that when I try to use the resulting packages as
>>> my system configuration, my computer gets stuck in tty1, and attempting
>>> to switch to Xorg on tty7 leaves my screen frozen though the system is
>>> still responsive.
>>
>> Have you tried removing /var/lib/gdm and the contents of your user
>> account’s .local/share/gnome* directories?
>
> I just did, and now tty7 simply shows a copy of tty1 rather than
> irreversibly freezing my screen. What files are in /var/lib/gdm and
> $HOME/.local/share/gnome that would have such an effect?
~/.local/share/gnome-shell/application_state is a common problem. It
contains some state that different versions of GNOME seem to be choking
on. There are some other files like ~/.cache/gnome* that might affect
GNOME and prevent starting after upgrades. It’s frustrating.
/var/lib/gdm is the home directory of the gdm account, and it too can
accumulate state. In my opinion /var/lib/gdm should always be recreated
on every boot.
--
Ricardo
next prev parent reply other threads:[~2019-10-18 3:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 21:55 'core-updates' Q4 2019 Marius Bakke
2019-10-09 11:53 ` Mathieu Othacehe
2019-10-10 14:32 ` Ludovic Courtès
2019-10-10 15:35 ` Mathieu Othacehe
2019-10-10 21:22 ` Svante Signell
2019-10-11 7:52 ` Ludovic Courtès
2019-10-11 20:42 ` Kei Kebreau
2019-10-12 22:15 ` Ludovic Courtès
2019-10-15 1:28 ` Kei Kebreau
2019-10-15 16:49 ` Marius Bakke
2019-10-17 20:44 ` Kei Kebreau
2019-10-17 21:29 ` Ricardo Wurmus
2019-10-18 1:53 ` Kei Kebreau
2019-10-18 3:08 ` Ricardo Wurmus [this message]
2019-10-19 13:34 ` Timothy Sample
2019-10-20 3:29 ` Kei Kebreau
2019-10-21 13:58 ` pelzflorian (Florian Pelz)
2019-10-22 0:37 ` Timothy Sample
2019-10-23 3:07 ` Timothy Sample
2019-10-23 7:49 ` pelzflorian (Florian Pelz)
2019-10-26 20:26 ` Kei Kebreau
2019-10-23 17:49 ` Marius Bakke
2019-10-24 2:07 ` Timothy Sample
2019-10-24 18:17 ` Marius Bakke
2019-10-26 21:25 ` Timothy Sample
2019-11-02 2:27 ` Kei Kebreau
2019-11-04 19:37 ` Miguel Arruga Vivas
2019-11-05 23:38 ` Kei Kebreau
2019-11-06 17:46 ` Leo Famulari
2019-11-07 1:16 ` Kei Kebreau
2019-11-07 2:58 ` Timothy Sample
2019-11-08 0:58 ` Miguel Arruga Vivas
2019-11-23 2:11 ` Kei Kebreau
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=87a79ylpi3.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=kkebreau@posteo.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 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).