-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snap: build against 20.04 #267
Comments
The player won't start: |
What if you remove UPD: |
OK, for some reason snap image ( |
I did try a complete reinstall, but same results.
I reverted I then tried the refresh on another machine and this time it worked.
There aren't any options for that in the store UI.
Yes this looks to be exactly right, if it list connections there are empty slots. I am not at that machine now, but I can get the output of |
On the working player, none of the web based content works, the browser renders with the following error inside it:
|
That happened due to snap environment probably... On my machine, everything works as expected, including web rendering. It's pretty weird how sandboxed environment produces very different behaviour every time Potential dirty fix: https://forum.snapcraft.io/t/help-gdbus-error-this-call-is-not-available-inside-the-sandbox/29969 |
Here is the output for
And here is the output for gnome from snap list:
I also tried running, to try and link the same interface/plug as on the working laptop.
|
I did a complete reinstall again, and this time the same PC to generate the above output, worked fine on Updated connections:
I can't explain why a reinstall did not work the first time around, but has worked this time. Edit: web content works too! |
I've tried a complete reinstall under Wayland, and the tricks you linked above, and I can't get past:
|
Have fixed it by add the network-status plug...
done :) [EDIT] |
We still build against 18.04 when snapping, but we're using 20.04 in our dev container. Investigate whether we can no build against 20.04 and see if that enables us to reduce some of our compilation requirements.
The text was updated successfully, but these errors were encountered: