That version of the snap is expected to work on Ubuntu 16.04, 17.04, 17.10 and 18.04, and more generally on any linux distribution that supports snaps.
Specific Tests
I’m interested in your feedback using the snap for your normal browsing activities and workflows, including web development.
Please report any issues you encounter in this thread. Thanks!
Yes, I’m aware of the issue and I am investigating it. Any page that embeds video is affected, so it’s pretty bad, but it’s not affecting chromium in any other channel, as far as I know, only candidate/from-source.
I didn’t get to the bottom of the crash but the backtrace indicated that it had to do with clang’s Control Flow Integrity, so I restored a build flag that is also used when building chromium deb packages (this commit), and it did the trick.
Last night I was using revision 437 which I left running when I suspended my laptop. This morning when I resumed operation I used Chromium briefly before switching to another application and workspace.
Within a minute or two I noticed that Chromium’s indicator in Ubuntu Dock to show it was being used had gone. I switched back to Chromium’s workspace to find it had crashed. On restarting it offered to restore web pages as it had shutdown incorrectly.
“snap changes” shows I am now using revision 438 after an auto refresh which happened a couple of minutes after I switched on my laptop.
I’m new to snaps so I don’t know what I should have seen when the application auto-refreshed. I suspect either nothing or a message from Chromium to advise of the update. Or was the crash just a coincidence and not related to the refresh?
Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector.
Both Chrome and the regular version of Chromium allow me to use that site to manage extensions.
