installing gnome desktop (and its dependencies) breaks login (and potentially other commands)

[c4artisan]

Windows version (build number):
Windows 10 Pro 19044.1806 (21H1)

Linux distribution:
ubuntu jammy

Kernel version:
5.10.102.1-microsoft-standard-WSL2

Genie version:
genie 2.4

Describe the bug
after installing gnome desktop (ubuntu-desktop gnome), the login command is broken and wont output anything

Confirm that you are running inside the bottle:
outside
To Reproduce
Steps to reproduce the behavior:

1. install package "ubuntu-desktop gnome"
2. restart the ubuntu enviroment
3. initialize the bottle (which will get stuck on the first seconds) and then try to login
4. the command will take an absurd amount of time and then output "systemd state "unknown" (or something like that?)

Expected behavior
command -l / --login outputs the username and password

Screenshots

Additional context
i tried purging the package and its dependencies, didnt do anything

I confirm that I have read the ENTIRE supplied readme file and checked for relevant information on the repository wiki before raising this issue, and that if the solution to this issue is found in either location, it will be closed without further comment:

yes

[cerebrate]

Yeah, it's likely that trying to install the full Gnome desktop environment will configure a whole bunch of services, etc., that aren't going to be happy trying to run under WSL.

What's the output of systemctl status when the system is in the state where the error occurs?

Also, what's the output of systemctl get-default?

[c4artisan]

Yeah, it's likely that trying to install the full Gnome desktop environment will configure a whole bunch of services, etc., that aren't going to be happy trying to run under WSL.

What's the output of systemctl status when the system is in the state where the error occurs?

Also, what's the output of systemctl get-default?

ouch..... that's gonna be hard to respond, as i deleted the vm (however, i made another one) the enviroment was put in.
however, im willing to do it again, ill respond whenever im ready

[c4artisan]

Yeah, it's likely that trying to install the full Gnome desktop environment will configure a whole bunch of services, etc., that aren't going to be happy trying to run under WSL.

What's the output of systemctl status when the system is in the state where the error occurs?

Also, what's the output of `systemctl get-default?

"systemctl status" gave "Failed to read server status: Transport endpoint is not connected"
systemctl get-default gave "Failed to get default target: Transport endpoint is not connected"

[NotTheDr01ds]

@c4artisan Try:

sudo systemctl mask acpid

That looks to be the culprit to me. I'm not running Genie, but I can reproduce the same problem with a generic Systemd bottle on WSL2.