This bug was fixed in the package wsl-setup - 0.5.9
---------------
wsl-setup (0.5.9) plucky; urgency=medium
* Fix dependency on cloud-init.service: (LP: #2104307)
- The wsl-setup script was supposed to sync with cloud-init
- It checked if the cloud-init.service was enabled.
- That unit no longer exists on Plucky.
- It now checks for cloud-init-local.service, which exists
on plucky and prior releases as well.
-- Carlos Nihelton <cnihel...@ubuntu.com> Thu, 27 Mar 2025 10:22:28
-0300
** Changed in: wsl-setup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wsl-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2104307
Title:
wsl-setup script not waiting for cloud-init to finish on plucky
Status in wsl-setup package in Ubuntu:
Fix Released
Bug description:
This bug is fixed upstream already but not yet released to Ubuntu. The
wsl-setup script should detect whether cloud-init is supposed to run
or not, and if so wait for it to complete before proceeding with its
other business. That's the behaviour observed on Noble but not on
Plucky. That's because the unit cloud-init.service is no longer
present. We need a new release of wsl-setup with the fix for this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2104307/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
