I've got 99 issues but a degraded status ain't one.
After switching from `systemd-genie` to `bottle-imp`, I get this failed unit:
```
# systemctl status snapd.seeded.service
× snapd.seeded.service - Wait until snapd is fully seeded
Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-10-22 17:49:06 PDT; 2min 48s ago
Process: 617 ExecStart=/usr/bin/snap wait system seed.loaded (code=exited, status=1/FAILURE)
Main PID: 617 (code=exited, status=1/FAILURE)
Oct 22 17:49:06 hostname systemd[1]: Starting Wait until snapd is fully seeded...
Oct 22 17:49:06 hostname snap[617]: Interacting with snapd is not yet supported on Windows Subsystem for Linux.
Oct 22 17:49:06 hostname snap[617]: This command has been left available for documentation purposes only.
Oct 22 17:49:06 hostname systemd[1]: snapd.seeded.service: Main process exited, code=exited, status=1/FAILURE
Oct 22 17:49:06 hostname systemd[1]: snapd.seeded.service: Failed with result 'exit-code'.
Oct 22 17:49:06 hostname systemd[1]: Failed to start Wait until snapd is fully seeded.
Maybe should be added? I'd also love to know if there are any workarounds cause my quick searching hasn't found anything.
Turns out this is a problem that just started happening when snapd fixed a bug. Fortunately, there's a workaround now and a fix forthcoming.
See my new post here - https://randombytes.substack.com/p/snapd-failing-under-wsl-suddenly - for all the details and the fixes.
After switching from `systemd-genie` to `bottle-imp`, I get this failed unit:
```
# systemctl status snapd.seeded.service
× snapd.seeded.service - Wait until snapd is fully seeded
Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-10-22 17:49:06 PDT; 2min 48s ago
Process: 617 ExecStart=/usr/bin/snap wait system seed.loaded (code=exited, status=1/FAILURE)
Main PID: 617 (code=exited, status=1/FAILURE)
Oct 22 17:49:06 hostname systemd[1]: Starting Wait until snapd is fully seeded...
Oct 22 17:49:06 hostname snap[617]: Interacting with snapd is not yet supported on Windows Subsystem for Linux.
Oct 22 17:49:06 hostname snap[617]: This command has been left available for documentation purposes only.
Oct 22 17:49:06 hostname systemd[1]: snapd.seeded.service: Main process exited, code=exited, status=1/FAILURE
Oct 22 17:49:06 hostname systemd[1]: snapd.seeded.service: Failed with result 'exit-code'.
Oct 22 17:49:06 hostname systemd[1]: Failed to start Wait until snapd is fully seeded.
```
Maybe should be added? I'd also love to know if there are any workarounds cause my quick searching hasn't found anything.
Turns out this is a problem that just started happening when snapd fixed a bug. Fortunately, there's a workaround now and a fix forthcoming.
See my new post here - https://randombytes.substack.com/p/snapd-failing-under-wsl-suddenly - for all the details and the fixes.