hello elcste,
no, it is not your fault 
I have the same problem here and try to find a solution.
Until now there are 4 different error case’s.
And of course, there are 4 different error-messages 
hopefully the error does not hide too long
In general I’d get grumpy at people suggesting to install things with --devmode, as that invites copy-paste of dangerous commands, but I think you’ve done a good job of making it scary enough in this case so it’s alright.
Just commenting so that other people who I’ve told off for --devmode can’t point at this as a counterexample.
you right i will change devmode to classic soon
Sorry the upload, still not works because of the approval.
Just figured out, that the config “grade: devel” and classic will not upload to the snapstore.
So, i switched back to devmode.
Hope i can now upload again.
As discussed on IRC, the use of ‘classic’ requires a manual review and you must follow Process for reviewing classic confinement snaps.
I’ve taken a look at the snap and there are older revisions that are hanging up later revisions. I’m working through unclogging those since later revisions seem to address the issues.
As an aside: if you are doing a lot of changes to your snap, you may want to use the review-tools to verify before upload. Eg, snap install review-tools ; snap-review /path/to/your/snap
As another aside: packaging sway as a snap is a very interesting idea. I’ve wanted to try sway myself, but haven’t yet. It is going to need to be classic for the time being, but @alan_g has been working through various items for making desktop shells work under strict mode, so some day it may be able to be strict mode.
Thank you.
I will look at the review tools.
Maybe i can help to build strict desktops
Yay! I actually tried doing this myself a year ago and failed Building a snap for a wayland compositor
Very glad to see this and will be giving it a try soon – assuming it is supposed to work as is with --classic right now? It is unclear from the discussion above.
Thanks!
Hi @tsloughter,
yes, the version described above was tested in classic mode.
I will right now start to upload a new edge version, which starts in “devmode”.
“jailmode” and “strict” is still not worked.
A confined snap launching another snap? Slow.
There have been some discussions around the PR: some resolved with actions (e.g. I need to change the interface name) some not resolved yet.
Don’t expect anything you can use soon, as the initial proposal is intentionally very limited in scope to minimize the security “surface” exposed. Even so, it is taking time to ensure things are secure.
oh, that’s odd.
I’ll see if I can find the PRs.
Hmm. What they want to do? Write a protocol filter for the X11 socket?
An external application like a terminal only needs the graphic output, right?,
I also asked here for details:
I’m not sure, but I’m fine with classic.
I’m not sure. I guess it would be cool if it worked with strict but I’m not sure what all it needs access to and if that is worth it.
hi,
@tsloughter
now it’s difficult to mention, if you would use preinstalled drm and opengl packages. Or what should classic include?
What is your setup ? Did you already have a desktop (as backup) installed ?
I’m not sure what you mean?
Currently, I run sway by installing it and wlroots from source manually.
Inside of sway i had to add all needed libraries.
Then every machine has different gpu’s with different needed packages.
Should i add all of them inside the snap or just use the libraries which are on the host.
Not sure.
You cannot safely use libraries from the host. Assuming you use core18 you will be linked against libraries from Ubuntu 18.04, if your snap is installed on Arch, then there is no reason to expect the host libraries and their dependencies to be ABI compatible.
You have to ensure that you have all the userspace libraries you need from the snap. (And also ensure that any executable from the you launch doesn’t pick up anything from the snap - so be careful with environment variables that affect this.)
