Call for testing: chromium 61.0.3163.100

Icon in the dock, or in the activities view (or both)? Can you share a screenshot?

Can you share details about your hardware (graphics card) and software:

snap info core chromium

The snap was probably refreshed automatically. Can you share the output of:

snap info chromium

And is the problem with the font fixed?

It was updated, sorry busy at work and didn’t even try checking loading the app, my apologies.

The title fonts look fine, but rendering on the page is still off

None of this is a road stopper for me, just thought it’s things you may want to address. Let me know if you need more info.

Thanks for the feedback. The font rendering problem on web content is most likely another missing font package, I’ll see if I can figure out which.

@diplo can you please share the output of:

gsettings get org.gnome.desktop.interface document-font-name

I like the alerts on Discourse :slightly_smiling_face:

andy@asuras ~ $ gsettings get org.gnome.desktop.interface document-font-name ‘Sans 11’

I was googling to try and work that out myself

What is the output of:

fc-match Sans

andy@asuras ~ $ fc-match Sans
ClearSans-Regular.ttf: “Clear Sans” “Regular”

I’m only here for another 25mins today, don’t have access to the machine till Monday I’m afraid, but will check here over the weekend, just don’t have the machine to test on.

Thanks. If that was the setting being used to determine the font for web content rendering, it should be found as it is in the snap. I’ll have to keep digging. Can you share a screenshot of that page as rendered by the chromium snap: chrome://settings/fonts ?

Good timing, just about to shut the machine down. Hope that is helpful, as I’ve said… this isn’t an issue for me, but nice to see how things work, will try and build my own snap next week.

name: core
summary: snapd runtime environment
publisher: canonical
description: |
The core runtime environment for snapd
type: core
snap-id: 99T7MUlRhtI3U0QFgl5mXXESAiSwt776
tracking: stable
installed: 16-2.27.6 (2898) 85MB core
refreshed: 2017-09-07 19:09:21 +1000 AEST
stable: 16-2.27.6 (2898) 85MB -
candidate: 16-2.28.1 (3017) 87MB -
beta: 16-2.28.1 (3017) 87MB -
edge: 16-2.28.1+git392.0a4186a (3033) 87MB -

name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: canonical
description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R

  • chromium
    tracking: candidate
    installed: 61.0.3163.100 (49) 242MB -
    refreshed: 2017-09-29 04:35:20 +1000 AEST
    stable: 60.0.3112.101 (9) 244MB -
    candidate: 61.0.3163.100 (49) 242MB -
    beta: 62.0.3202.29 (46) 241MB -
    edge: ↑

Hardware: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)

When I start chromium from the snap under a Wayland session I see a chromium process running but no window appears. There is no error message. It works normally under the Xorg session.

I have been using it for the whole day and it looks ok, no problem encountered. The only thing is that if you open a PDF in Chromium and then decide to save it, you have to search for your home/folder directory as you are, by default, in the snap folder.

Doesn’t work for me.
OS: Ubuntu GNOME 17.04

Steps to reproduce

  1. sudo snap install chromium --candidate
  2. chromium


Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"

Visual Output:

Thanks for all the good feedback everyone. I am aware that the snap is not working for everyone yet, there are issues to be investigated and addressed, however it does work for a number of people in various configurations, so it doesn’t make sense to hold it off any longer, especially since the stable version for upstream chromium is now at 62. I have therefore promoted the snap from candidate to stable, and a build of version 62.0.3202.62 is underway, which I hope will hit the candidate channel early next week (a separate call for testing will be issued then).
Keep up the testing and the feedback!

I can reproduce the Chromium icon issue. Here’s is a screnshot showing it. Also, it takes a couple of minutes to load fhe first time after a reboot.

Another thing I’ve noticed is that Chromium cannot set or check if it’s the default browser.

See here and here.

1 Like

Thank you, @Ads20000. So, there’s no solution yet for this problem, according to the links you provided :frowning: It’s a minor problem, though.

1 Like

You can however set chromium from the snap as your default browser applications in gnome-control-center:

gnome-control-center default-apps

The icon issue should be fixed in the candidate channel, please see the call for testing (and report there whether this works for you).