I have been able to use win-kex for a long time until today. Now I am having an issue where running kex gives me the following error:
However, I am able to run sudo kex and it works fine, minus that I am now logged in as root. Weirdly as well, I am able to run kex --esm with very poor performance. It seems like such a weird error that I figured it can't hurt to ask here. Thank you in advance for the help!
-
See unix.meta.stackexchange.com/questions/5360/….– Archisman PanigrahiOct 16, 2022 at 20:51
-
1@ArchismanPanigrahi The issue in the question does not seem to be related to their inability to use basic Linux tools. The issue appears to be a change in behaviour in a utility that has been working for some time.– Kusalananda ♦Oct 18, 2022 at 6:48
Add a comment
|
2 Answers
Try this:
sudo kex kill
sudo kex start
Now you must know what your KeX type is, then look here and go to down in "Run Win-KeX":
https://www.kali.org/docs/wsl/win-kex/#optional-steps
My KeX type, for example, is: kex --esm --ip -s
(ESM = Enhanced Session Mode),
but your KeX can be different.
-
Why do you tell the user to look in the “Run Win-KeX” section of the document, but then link to the “Optional Steps” section? And how does knowing the “KeX type” relate to your answer? … … … … … … … … Please do not respond in comments; edit your answer to make it clearer and more complete. Dec 26, 2022 at 20:40
I was able to fix it on my own by modifying the executable for KeX. For some unknown reason the virtual "screen" had become locked by TigerVNC. The fix was to change the screen variable from defaulting to 1, to defaulting to 2. This may be a bad workaround, but I was tired and it worked. Will update if that changes.