I tend to test the edge core snap at times and sometimes forget to switch back to stable …
Today suddenly all my snap apps stopped opening any links out of the blue … when checking, i recognized i’m running core from edge, so i switched it back to stable and even restarted the apps to make sure i’m back to normal …
Obviously this doesnt help, i can not open any links anymore even with core on stable, the snapd deb on 2.27.5 and snapd-xdg-open installed …
All i’m getting now is:
Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonial.SafeLauncher was not provided by any .service files
while it is fine that this not fully implemented feature is broken in edge, rolling back to stable should definitely get me back to a working system again so something with the channel switching seems to be wrong here …
There was a regression in the core xdg-open, fixed branches for the core build are available here: https://github.com/snapcore/core/pull/57 and a regression test is available here: https://github.com/snapcore/snapd/pull/3905 (the regression test currently fails because it is broken, however one the fix gets merged the test will turn green).
A new core snap with the fix included is in the “beta” channel: snap refresh --beta core should bring it to you. Feedback welcome.
Hey @jsmolka - usually candidate is the right choice and regressions are very rare.
However sometimes those happen, my apology for this. Issues like this usually happen in area were our automatic testing is insufficient and for this class of problems we are now writing a new test that ensures that the snapd-xdg-open launcher works correctly all the time (it will be run as part of each of our code changes).
I think this also highlights that we should look into an idea from @niemeyer to de-couple core filesystem builds from snapd core builds. So that we can “snapshot” the core filesystem for 2.27 and only apply fixes to snapd without filesystem changes. We will definitely look into this as another way to fix issues like this.
As for your question about going to beta - it is probably safer to stay on candidate and I expect the updated core in beta to reach candidate soon (once our internal QA finished).
The update may not work right away because there may be an old mount namespace hanging around (@zyga-snapd can provide more details on this). A workaround is to
sudo umount /run/snapd/ns/test-snapd-tools.mnt
where test-snapd-tools.mnt is the name of your snap (or reboot but that is a bit heavy handed . But hopefully @zyga-snapd can provide more details about this.
Hello, the new 2.27.6 release is now in the candidate channel. Please help testing by snap refresh --candidate core and let us know if everything works as expected.
. But hopefully 