Howdy, Timothy Sample <samp...@ngyro.com> skribis:
> Ricardo Wurmus <rek...@elephly.net> writes: > >> Ludovic Courtès <l...@gnu.org> writes: >>> I removed pretty both .cache directories, moved .config sub-directories >>> around, etc., and yet I am still unable to log in into the GNOME account >>> (logging in to a non-GNOME account from GDM is fine.) >>> >>> I even tried upgrading the user’s profile just in case is contained >>> incompatible schemas or who knows what, but that didn’t help. >>> >>> What extra bit of state am I missing? >> >> Do you have ~/.local? In my earlier tests this contained binary >> notification data that when loaded would lead to a crash. > > I’m testing GNOME on ‘staging’ now, and had the same problem (GDM worked > okay, but I could not login). I fixed it by deleting > “~/.local/share/gnome-shell/notifications”. I left everything else in > my home directory as it was. That’s the one! I moved ~/.local/share/gnome-shell out of the way and after that I could log in. \o/ ~/.local/share/gnome-shell contained a single file, “application_state”. It’s an XML file that looks exactly like the one created by the newer GNOME: same schema, same attributes, etc. The weird thing: if after successfully logging in, I log out, move the old ~/.local/share/gnome-shell into place, and log in again, it works. Perhaps the mere presence of ~/.local/share/gnome-shell causes it to take a different path? Thoughts? Thank you! Ludo’.