From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: fixing GDM + GNOME Shell Date: Sun, 04 Aug 2019 23:00:41 +0200 Message-ID: <87tvawzlvq.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Cc: bug-guix@gnu.org List-Id: bug-guix.gnu.org Hi Guix, Today I again couldn=E2=80=99t log into my workstation after upgrading the system. I=E2=80=99m using GDM + GNOME Shell. At first GDM wouldn=E2=80=99t start. I knew what to do: remove /var/lib/gd= m, because some state must have accumulated there. GDM came up after a reboot, but I still couldn=E2=80=99t 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=E2=80=99t know if booting into an older s= ystem 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