Your question means that I didn't clarify enough the test I followed and
how it related to the original test plan proposed. The gap in
understanding is more due WSL specifics than cloud-init itself.
The fundamental difference between what is proposed in the bug report
and what I applied manually
Tested the version 0.5.3~24.04 from noble-proposed as described below:
- Disable cloud-init via WSL2 kernel command line.
- Create a new instance without a default user with command: `ubuntu2404.exe
install --root`.
- Boot into the instance, enabled proposed and installed *only* wsl-setup via:
** Patch added: "Attached debdiff for wsl-setup 0.5.3 for Noble"
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2065349/+attachment/5776855/+files/wsl-setup_0.5.3~24.04.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
[Context]
wsl-setup is a package to carry pieces of configuration specifically
implemented for a better experience with Ubuntu WSL.
A bug reported originally by Microsoft engineers, made public via
https://github.com/ubuntu/WSL/issues/468, **prevents any GUI application
Specifically adressing @iosifache concern
> 3. Command execution inside the Windows host:
With USB/IP the WSL instance gets low level access to a USB device as if it was
actually attached to the USB bus. I won't go into the details of how to get
that done, but it suffices to say that:
1. It
I attempted doing a similar install with Kinetic and Jammy, both crashed
in the very same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943386
Title:
Installer crashed while attempting btrfs
Public bug reported:
Since in WSL we don't have a real complete snap setup and the Flutter UI
sets the window title by using GTK+ API, it's necessary to make the
fonts-ubuntu package available in the system to avoid the bad user
experience of not being able to display the window title.
**
