#Typestatus posix connection refused full

So I checked a full installation into an actual vm of ubuntu and I noticed that the file was owned by root:root and the mode was 1777 '_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root' and that we're not in a systemd init environment.Д¬hecked the logs again, and I was getting a dbus session, which was progress, so I went to the next error in the list. Kind of beside the point, as wsl doesn't use systemd, but the 'user not found' part of that message is very intersting. 'dbus-update-activation-environment: systemd -user not found, ignoring -systemd argument'

xsessionerrors file in ~ I saw repeated messages akin to What I noticed was that DBUS didn't seem to know anything about me. There's a crazy interplay of xfce components at work here. I tried everything in these suggestions, and nothing worked. Being a regular user while using hacking tools is a very good idea, and it's a good idea anyway. You don't wanna be messing around with some of these tools and unwittingly jack your entire box up because you owned yourself, and that stuff happens for many reasons.Д«een up for a long time, too much coffee, not enough coffee, yadda yadda. The error occurs when trying to start kex/xfce as a non administrator.Д«ecause that's what you're supposed to do. Running it with sudo, or as root is NOT a solution. To be clear, the problem as defined is not being able to run kex as a NON-ADMIN. Ok, took some sleuthing, but there was a lot going on with this error. This solution worked perfectly for me without a single error or event being thrown. Works fine, but VNC borked and I got same Refused errors. Did a WSL 2 Kali reinstall and closed the initial newuser prompt dialog before completion as I only want root access to two things.

#Typestatus posix connection refused update

Straggler here, just did the Win 11 update and, well, Windows gonna Windows/break stuff. Following the logs from vncserver stating: I recommend posting this discussion as a bug report to the Kali Community and/or appropriate KeX developers.Д«eta Was this translation helpful? Give feedback.ДЄdding to the solution found by I was able to recreate this. If the server fails to start, please try 'kex kill' or restart your WSL2 session and try again. Please try 'kex start' to start the service. However, this creates another potential issue: The KeX GUI environment's login will be root.ДЄttempting to launch KeX using the user you create during initial setup causes the recurring error quoted above until KeX times out and throws As best I can tell, the only way to launch a KeX environment right now is to do so as root. I haven't done extensive testing, but I believe the issue resides in the way that the Standard User and associated permissions are created during initial setup through WSL2. Vncext: Listening for VNC connections on all interface(s), port 5901Д¬omparingUpdateTracker: 0 pixels in / 0 pixels out Underlying X server release 12010000, The X.Org Foundation _XSERVTransMakeAllCOTSServerListeners: failed to create listener for unixД¬opyright (C) 1999-2020 TigerVNC Team and many others (see README.rst) _XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 11 Adding to the solution found by was able to recreate this.