Thanks for taking the time to share your feedback Silvio, this is very much appreciated.
Answers to your points below. Note that when I link to a known bug, I’m not discarding the issue. It will eventually be addressed (and contributions are welcome!).
Terribly slow first startup of Chromium after logging in
Can you please quantify how slow? A simple stopwatch measurement would be useful, and if you can run the snap with
snap run --trace-exec chromium then close the window and share the terminal output that would be even more useful.
File save/open dialogs do not use the proper theming
This is bug #1791307.
Funky home directory in the same dialogs
This is bug #1798450.
All my saved login-credentials are gone so I have had to go through a number of tedious password reset sessions
Can you check whether the
password-manager-service interface is connected? (
snap interfaces chromium | grep password)
Parts of recent state keeps getting lost between browser restarts. Sometimes it is simply browser history but I also lost recently created bookmarks on at least two occasions
This is most likely because an update happened under your feet. I concurr this is very annoying, and currently being actively worked on. Can you test the instructions at https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736 ? This works for me, and I’d be interested in hearing whether it does for you too.
9 processes called Chrome when I open 1 Chromium window
Chromium’s architecture relies on multiple sandboxed processes for security. This is not specific to the snap. How is that a problem? Is it the name (“chrome” VS “chromium”) that’s bothering you?
a load of file system mounts when Chromium is running
Do you mean snaps that are mounted under
That’s not specific to chromium, but an implementation specificy of snapd.
Gnome shell extensions plugin no longer works because it does not detect chrome-gnome-shell
This is bug #1741074.