Just to add that this is a vanilla install of Solus 3, not changed any settings apart from installing a few applications.
The “Clear Sans” font doesn’t appear to be packaged in Ubuntu, so it can’t easily be added to the snap’s stage packages. This problem will go away once snapd allows access to the host’s fonts, see the work James has done here.
If you can point me to the solus package for that fonts, I might be able to add it to the snap manually.
Found the font package from solus, and added to the snap here.
A build will kick off automatically shortly, and I will update the candidate channel once built.
And done. Can you refresh your snap from the candidate channel and let me know if the font issue is still there?
snap refresh chromium --candidate
Just a quick polish note here, the icon shown in GNOME Shell on Ubuntu 17.10 is generic, not the Chromium icon.
It doesn’t work on 17.10, Wayland session.
Thanks for the work! Apologies for the delay, this is my work machine
andy@asuras ~/Projects $ sudo snap refresh chromium --candidate
snap “chromium” has no updates available
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
andy@asuras ~ $ gsettings get org.gnome.desktop.interface document-font-name
I was googling to try and work that out myself
What is the output of:
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:
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.
summary: snapd runtime environment
The core runtime environment for snapd
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 -
summary: Chromium web browser, open-source version of Chrome
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
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 -
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.