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.
Slow as in somewhere in the range of 3-7 seconds. In my previous installation Chromium would show up on screen in less than a second. And it is not only after logging in but often also when reopening a Chromium window after having shut down all previous ones. Even my libreoffice-writer/calc (not the snappy ones) start up in a fraction of what Chromium takes now.
My Dell XPS13 laptop of about 5 years old has a modest i7-3537U CPU @ 2.00GHz but coupled with the SSD it still used to be fast enough for my daily work.
File save/open dialogs do not use the proper theming
This is [bug #1791307](link removed).
Please see blow…
Funky home directory in the same dialogs
This is [bug #1798450](link rmoved).
Please see below…
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 ? This works for me, and I’d be interested in hearing whether it does for you too.
Even if that would works I don’t want that. I want to do my own updates in my own time. Snaps should hold off all updates until I use the Software updater or something similar.
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?
Actually this is a mistake on my part, these processes where indeed there. The unexpected name has probably thrown me off.
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.
Yes, I know that but that does not make it less annoying. Just another way snaps are sticking out.
Gnome shell extensions plugin no longer works because it does not detect chrome-gnome-shell
This is [bug #1741074](link removed).
I understand some of the issues I have are more snap related than snap-Chromium related. But that does not make it any better for me. For a number of reasons I am obliged to keep up with the latest Ubuntu version and 19.10 is only weeks away. The assurance that this transition will not be back-ported to previous Ubuntu releases until major issues have been resolved does not help me at all. I need a Ubuntu 19.10 with a properly working Chromium.
In the meantime I have moved to Debian testing because of this. Luckily I have a separate / and /home partition and keeping /home worked like a charm. So far I have no issues with this setup, although I do miss some of the Ubuntu-niceness. To boot my Chromium browser once again opens in a flash.
BTW: I removed all links because I was not allowed to post this otherwise.