I want to preface this that I’m an intermediate Linux user, and until recently I’ve always used full desktop environments until starting to experiment with Sway. So basically, this problem could all be my fault
It is not starting correctly for me. On a Focal system I installed yesterday, this is what I get when I try to start it from a console:
$ which sway
- [sway/server.c:140] Unable to open wayland socket
When I install the Sway deb from the Ubuntu archive it opens and run OK when do the same thing.
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.
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.
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.