snapd is intentionally broken under WSL and shouldn't be
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
Undecided
|
Edu Gómez Escandell |
Bug Description
This commit:
https:/
causes the snap command to refuse to run on WSL.
I'm a little confused by why I'm bringing this up now, since it's a 2018 commit, but evidently it's only just surfaced, at least in my Debian installation.
This is something of a problem for all those of us who have been running snapd successfully on WSL up to now (either by using the previous method of running systemd in a pid 1 "bottle" or using the brand new systemd support under WSL, which renders the rationale for this change moot), obviously.
It also causes the rather unusual situation in which we are unable to manage snaps (without the snap command), but snaps which we had previously installed continue to work fine - just can't be removed or updated.
Please remove this check.
Changed in snapd: | |
status: | In Progress → Fix Committed |
Changed in snapd: | |
status: | Fix Committed → Fix Released |
This appears to be fixed in the PR https:/ /github. com/snapcore/ snapd/pull/ 12179 . If and when that's merged, please close this bug.