Thanks for the feedback!
For the issue with chromium being silently updated while it’s running, I recommend turning on the Refresh App Awareness experimental feature, which will prevent exactly that:
snap set core experimental.refresh-app-awareness=trueThis should be fixed when this MR is merged: https://gitlab.gnome.org/Community/Ubuntu/gtk-common-themes/merge_requests/17
It’s been sitting there for a while, waiting for someone from the desktop team to review it.
Two new issues noted tonight:
Using Chromium to upload to Google Drive (and other sites), I see that the file upload dialog or ‘Open Files’ doesn’t display an icon against ~/Documents in the folder and file list. An icon is displayed when using Firefox or Google Chrome to upload. Noted on both Ubuntu and Xubuntu 20.04. Something must have changed recently as I use Chromium to upload on a regular basis and haven’t noticed the missing icon before. (Also noted in a Kubuntu 20.04 live session).
The file upload dialog in Xubuntu 20.04 displays GNOME icons rather than the icon theme I have selected in ‘Appearance’. Presumably the Chromium snap only has access to a limited number of icon sets and falls back to the default sets available to snaps.
@oSoMoN, let me know if you need a bug report for these issues.
I’ve recently noticed that Chromium no longer can display emoji. All I get are square boxes and some black & white symbols. E.g. https://getemoji.com/ renders like this:
I’ve also noticed this in my journalctl:
saus. 03 12:14:00 blynas chromium_chromium.desktop[5143]: Fontconfig error: Cannot load default config file
saus. 03 12:14:05 blynas chromium_chromium.desktop[5143]: Fontconfig error: Cannot load default config file
saus. 03 12:14:09 blynas chromium_chromium.desktop[5143]: Fontconfig error: Cannot load default config file
Unfortunately I don’t remember if earlier versions of snap-ified chromium had this problem or not. I’m quite sure Chromium in 19.04 did not have this problem (because I was working on a site where I had to explicitly add a “font-face: emoji” to my CSS to get colorful emoji characters in Chromium, and my site is now broken).
Of course it might be an upstream regression. I’m not sure how to check.
I’m getting color emoji with the Chromium Snap, but I’m on the beta channel.
You could snap refresh --beta chromium, but be warned that I think you’ll need to delete your profile if you want to go back to the stable channel. (If you use Chrome sync that might not be that bad…)
Other thoughts: Do you have the fonts-noto-color-emoji package installed? Does the same color emoji work for you in other apps, e.g. Firefox?
Indeed. There have been changes in how Widevine is bundled and detected in upstream chrome that affect chromium too. I recommend downloading the latest chrome deb and extracting the WidevineCdm directory that lives in opt/google/chrome into $SNAP/.local/lib/. That directory contains a manifest.json file and a _platform_specific folder under which libwidevinecdm.so lives.
Hey Paul, please file a bug report for these issues, if you don’t mind.
I’m seeing the same in a clean eoan VM (the chromium snap version doesn’t matter, all channels exhibit the problem). Interestingly my work laptop with the chromium snap from the stable channel doesn’t exhibit the problem, emojis are rendered correctly.
In both cases I’m seeing several instances of this error message:
[ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
but it’s probably unrelated, given that emojis are rendered correctly and coloured on my laptop.
Would you mind filing a bug to track the problem?
Sure. I’ve filed LP #1858636.
It’s not LP #1794354 because I don’t have fonts-symbola installed. (I do have fonts-noto-color-emoji installed.)
Try
snap refresh gtk-common-themes --candidate
and then restart your browser, it got the correct cursor working for me, after @kenvandine applied the fix .
Chromium not having access to .dot folders under $HOME is an issue for me, as I am using shared, short lived mtls certificates under .pki/nssdb. Is there a way to use the global nssdb?
Thanks for pointing out the issue. I filed a bug to track it, with a suggested solution which I will discuss with the security team.
I was just forced yesterday by ubuntu to use snapped chromium, which lead to tonns of problems:
snap security features is terrible, if I would to isolate something I would to use virtual environment, or chroot. Please restore deb chromium. Current one is almost unusable for me.
problem with system proxy is the following:
If you have running chromium and restart proxy which configured as “automatic proxy” chromium loose the proxy configuration and restores it only after restart.
APT just forced me to transition from Deb to Snap. Lost user profile, NOTHING got migrated. Stuck with snap’s GTK theme instead of the one I use. Who’s idea was it to move to SNAP? Just WHY?
Everything was great using deb now we’re 100% stuck with snap. I had to install the entire snapd to migrate. So now I need to run snapd + chromium via snap. A bigger, more resource hungry and buggier version. Ultimately snapd is going to be the Ubuntu thing that makes me switch to another distro…
Just FYI: I was able to move my profile over (copied ~/.config/chromium to ~/snap/chromium/.config)
Just curious: Apt tells me I still have the chromium-browser but I cannot call apt remove on it says it says it’s not installed. What kind of black magic is that? Also any way bypassing this at all?
This seems like a normal AskUbuntu-type of support request that seems unrelated to the snap discussion.
Hey there, just got the update to snap : user agent changed from apt version and WhatsApp webapp recognizes chromium as an old version of Chrome. So app refuses to work. I expect to see this more on other sites I didn’t test yet, and yes a user switcher is a workaround but definitly not the real solution.
I’ve managed to silence the audit warnings like this:
sudo sed -i '/^}/ {
i
i # added by Lucas, 2020-02-04
i # based on https://askubuntu.com/a/953988/854071, incl. comment by Paul A Jungwirth
i @{PROC}/@{pid}/mem r,
}' /var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver
sudo systemctl reload apparmor
(Hand-editing /var/lib/ files seems evil, but I couldn’t find an equivalent place below /etc. If you try this you’ll want to adjust the comment a bit, of course.)
But that doesn’t fix the chromedriver error at all – it still fails in the same way, only now there’s no more messages in the journal about it.