I apologize in advance, because this post will not be very productive. It’s basically a list of a lot of issues I encountered which are all pretty hard to debug and when I try to debug one I normally stumble into the next one. Maybe the right thing would be opening one github issue per bug, but I couldn‘t convince myself yet, because those bugs sound like they are really tough to pinpoint. I guess most of these are upstream problems but I can‘t really tell.
I realize writing and maintaining gnome is a lot of work and I appreciate everything that is being done for it. I really do. Still, my gnome drives my crazy quite often. The bugs listed here were all encountered within a 3h session, but most of them are not new to me. This is on nixos-unstable but I had most of these issues on 20.09, too.
- gnome often hangs, that’s okayish, performance is probably hard. (I have a Thinkpad T480s which is actually not that old, but I can stand a few lags.)
- when those hangs happen, the key I am currently pressing get’s repeated a lot, when I try to fix the resulting typo by pressing backspace often the next hang repeats the backspace, deleting everything I wrote. (That can be infuriating, I think it got a bit rarer when I switched to unstable. Improvement, yay!)
- pam-auto-keyring-unlock fails in roughly 3 out of 4 times when I (re-)login: It just prompts for the password of my default keyring although it shouldn‘t. The odds get better, when I wait 15s before reloging.
- When I unlock the keyring manually after the fail, the keyring does not work (i.e. respond) as a ssh-agent as it usually does.
- When I disable auto-keyring-unlock (via forcing the nixos option), my gnome-keyring hangs with 100% cpu consumption on start.
- I have done something (probably hard to reproduce, but I really don‘t think I have done anything far out of the ordinary) with my home-manager that closing the shell in which I ran
home-manager switchcauses gnome-shell to crash. (This one is actually a bit funny.)
- Normally after reloging some of the session-variables home-manager normally sets (and which are successfully set on first login) don‘t get set or overriden by systemd defaults.
- gnome-calendar crashes when I scroll to next january.
- Sometimes gdm hangs and freezes.
- Sometimes gdm login hangs after entering and confirming my password.
- Sometimes after relogin I don‘t have a running user systemd session.
- Sometimes the logout button does not have any effect.
- Sometimes the gnome-shell just crashes right after login and I get logged out again.
Maybe other people can share if they have encountered at least some of those issues and maybe have some tips for me? Or just mention that their gnome (and especially gnome-keyring-unlock) runs just great?
I don‘t want to give up on gnome, because I think the UI decisions are best in class. And I am always really happy when something works out of the box. (Like e.g. just click here in the options to map your wacom tablet input to a monitor of your choice. Imagine that working out of the box on a linux system 10 years ago … Or entering my nextcloud credentials and then having my calendars synchronized. Most of my i3/sway friends just don‘t have working calendars on their system …[I am sure there are solutions for that but in my sample most of them don‘t have them set-up.])