Also, chromium does not seem to respect the chosen audio output or input in pulseaudio. It will latch to the last connected one, regardless of what you have selected on the output or input choosers.
1 Like
I upgraded my main machine from Focal to Groovy, and now the first launch after a reboot of the Chromium snap is taking much longer than before. The one time I timed it, it was over 30 seconds. Anyone else seeing this? I’ve noticed this first launch took longer than further launches, but it always seemed to be under 10 seconds.
I tried another computer I could erase, and on Groovy that computer took about a minute to launch the Chromium snap after rebooting. Then I clean installed Focal on the same machine, and the Chromium snap was just under 10 seconds to launch after a reboot.
I haven’t noticed it for any other snap, although I don’t use many that I ever saw much of a launch delay like Chromium. VS Code for one doesn’t seem slower, but I didn’t compare.
Edit: I filed bug 1900783.
1 Like
I upgraded my laptop from Focal to Groovy and now I can’t launch Chromium at all in a Wayland session:
[5379:5379:1023/110218.809226:ERROR:browser_main_loop.cc(1426)] Unable to open X display.
AFAIU this is a known issue with Mutter dropping support for the abstract X11 socket, while snaps rely on the abstract socket don’t actually set up a /tmp/.X11-unix/X0 socket in the sandbox.
For now I’m using socat to forward the abstract socket to the real socket as a workaround, but it is very slow:
socat abstract-listen:/tmp/.X11-unix/X0,reuseaddr,fork unix:/tmp/.X11-unix/X0
1 Like
Indeed, this is a known regression in mutter 3.38, which @jamesh fixed. The fix should make its way to a maintenance release and will be SRUed to groovy as soon as possible.
3 Likes
The fix for Mutter is now available in groovy-proposed, so is on the way to groovy-updates:
1 Like
This may be of interest to people monitoring this discussion.
6 Likes
I saw this on the Chromium blog: https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html
It talks about “third-party Chromium based browsers”, which I thought at first meant things like Brave or Vivaldi, but the Arch Chromium maintainer says it applies to them (https://lists.archlinux.org/pipermail/arch-dev-public/2021-January/030260.html).
I don’t use sync myself, but I would miss the Google Translate feature.
2 Likes
That isn’t my understanding from the press release. They’re talking about 3rd party Chromium-Based. Not Chromium as it’s Chromium and not based on Chromium. I take it as your 1st meaning as in my opinion the nuance isn’t that subtle.
2 Likes
At this point this isn’t really clear. It is being discussed on the chromium-packagers group.
3 Likes
That would really suck if they do remove syncing.
1 Like
Sounds like Google considers Chromium shipped by anybody but Google, as a 3rd party project. I wonder what is really behind this move though?
But there are 3rd party browser sync projects that allow one to self-host, so maybe that’s an option for Chromium packagers to assimilate? Extra work for sure though.
2 Likes
Thank you, I was looking for it before I reported the problem.
@oSoMoN posted that Google client ID/secret has been removed from beta and dev builds (Desktop Team Updates - Monday 1st February 2021). I’m using the beta, so if it is live now I can confirm the Google Translate feature is still working. The original Google post linked to a list of APIs that included a bunch of things, including Translate, but later discussion on the mailing list clarified it was only sign-in/sync features that were being cut off, but they never gave an exact list that I saw.
1 Like
Is it hard to use Firefox sync/account functions for Chromium?
I don’t think that exists right now. Someone would need to write the code.
1 Like
@oSoMoN Hey, I’m curious about any changes with the latest beta (version 98.0.4758.66) — in a good way!
It didn’t seem to take nearly as long as usual to update (no fontconfig caching or something?) and first-time startup also seemed faster than usual.
2 Likes
Thanks for the positive feedback @elcste!
This can probably be explained by the rebasing of chromium on core20 and on the gnome-3-38-2004 extension.
This change is expected to be transparent to end users, but under the hood it is quite an important update, so feedback and bug reports for regressions are welcome. I didn’t do measurements myself, but I’m glad it appears to make the startup of the snap faster.
2 Likes
Indeed, I think it would be better to start a new thread on forum.snapcraft.io, or file a bug. Thanks!
1 Like