qertleather.blogg.se - Xeyes and clockx are work but startx not working

#XEYES AND CLOCKX ARE WORK BUT STARTX NOT WORKING HOW TO#
#XEYES AND CLOCKX ARE WORK BUT STARTX NOT WORKING FULL#
#XEYES AND CLOCKX ARE WORK BUT STARTX NOT WORKING WINDOWS#

Otherwise there are a number of things that just won't work in the meantime.Īgain, to do this "better", use one of the scripts/projects listed above. Note that after trying this out, you really should exit WSL, issue a wsl -terminate and restart it. It might take a few minutes to start up, though. This enters the namespace, and you can now use ps -efH to see that systemd is running as PID 1 in that namespace.Īt that point, there's enough of Systemd running and configured to run gnome-session and have it connect to VcXsrv. Wait a few seconds for Systemd to start up, then: sudo -E nsenter -all -t $(pgrep -xo systemd) runuser -P -l $USER -c "exec $SHELL" The scripts and projects listed above do extra work to get these things working as well.

#XEYES AND CLOCKX ARE WORK BUT STARTX NOT WORKING WINDOWS#

The Windows PATH (which isn't necessary without Windows Interop anyway).

Windows Interop (the ability to run Windows.

Note that this is a "bare minimum" command-line for starting Systemd. However, the "real" PID mapping still exists outside that namespace. Inside that namespace, Systemd will be PID1 (as it must, to function) and own all other processes. This starts Systemd in a new namespace with its own PID mapping. You can see this (and get Ubuntu Desktop running quickly) by executing: sudo -b unshare -pid -fork -mount-proc /lib/systemd/systemd -system-unit=multi-user.target Ultimately, what all of these do is create a new namespace in WSL/Linux where Systemd can run as PID1.

#XEYES AND CLOCKX ARE WORK BUT STARTX NOT WORKING FULL#

You can then decide if you want to go through the full setup. Or, I can show you the "quick and dirty" way of getting up and running. If you'd like to skip the rest of this, you can go straight to those instructions. Let's cover some of the projects that "help" you run Systemd on WSL:Īnd I'll also point out that Genie is used for these instructions on running Ubuntu Desktop.

#XEYES AND CLOCKX ARE WORK BUT STARTX NOT WORKING HOW TO#

) How to run Systemd on WSL2, allowing you to run Ubuntu Desktop on VcXsrv Ok, so now that I've tried to talk you out it and failed. You'll give up the tight integration with Windows that WSL provides, but you'll have an Ubuntu with a fully supported Systemd. If you really want Ubuntu Desktop/Gnome on Windows, then run it in a VM.If you really want a Linux desktop experience on WSL, go with one that doesn't require Systemd, such as Xfce4.Some alternativesīut let me first offer a few alternatives to running Ubuntu Desktop on WSL: So, at a very high-level, I'm going to cover some of that here. While there are projects out there that attempt to do this hackery for you, I still recommend having some understanding of the hows and whys of the changes being made to your WSL instance. You should be comfortable diving fairly deep into the internals of WSL, Linux, and Systemd in order to troubleshoot things that "go wrong". That hackery changes the way a lot of things work in WSL. WSL doesn't support Systemd, at least not without a lot of hackery. The hard part is that Gnome (and thus Ubuntu Desktop) really requires Systemd. What you really need at this point is the session manager - That's gnome-session. You've actually already done that by running VcXsrv. Let's cover the two main problems: The easy partįirst, by issuing startx, you are attempting to start the X server in Linux. There's an "easy part" to your answering your question and, well. I'll cover why as we get into the answer. I've done it, and I'll tell you how to do it, but. Before I get started, let me just say "Don't do that" -).