Since yesterday, we’ve been alerted to the fact that our latest snap update is causing a segmentation fault on Ubuntu 19.10, but works perfectly everywhere else. Here’s a summary:
- The update contains a few additions:
-
Electron v6 to v8
-
Support for xdg-open
-
Classic confinement
-
What doesn’t work: the snap installed from the snap store, on Ubuntu 19.10
-
What does work: the snap installed from the snap store, on Ubuntu 16-18, including Kubuntu
-
What also works: the .deb created alongside the build that’s on the snap store, on all platforms (including Ubuntu 19.10)
The issue happens only with builds built from our Azure Devops (aka VSTS) CI build servers, and not from our local machines, even when running an identical script. I even created a fresh Ubuntu 18 VM, installed everything from scratch just like our CI script does, and that worked. But for some reason, the CI build consistently causes the crash on Ubuntu 19.10.
I was wondering if anyone had any thoughts. I’m honestly at my wits end, having spent the last 12 hours on this problem along with our other senior engineer. We’re leaning towards removing snap as a download option until we have the mental bandwidth to troubleshoot this. Unfortunately, the only way to test this is to push a build out to the snap store, and then test to see if it breaks, since when we build locally, everything works fine. So having classic confinement for screen-dev would help, but it still wouldn’t solve the problem fully.
It looks like other folks have had similar issues (e.g. Slack crashes on Ubuntu 18.04), but it’s not clear exactly what they did to solve the issue. If anyone has any recommendations on how to fix this, please let us know!