| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006665 | Kali Linux | General Bug | public | 2020-08-20 08:00 | 2021-06-24 19:12 |
| Reporter | W0mbl3 | Assigned To | steev | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 2020.3 | ||||
| Summary | 0006665: kex command will not launch desktop | ||||
| Description | Having updated to 2020.3 I had no initial issues lauching the Kali desktop environment in WSL using the "kex" command. However having restarted the VM in WSL I now cannot open the desktop and get the error "unable to connect to socket: No connection could be made because the target machine actively refused it. (10061)" | ||||
| Steps To Reproduce | Just type open instance in WSL and then type kex | ||||
 |
Problem solved. Had to issue the "kex stop" command and then kex to use GUI environment after closing WSL instance. |
 |
Add a line with 'cd "$HOME" ' at the start of function 'start-kex' in the script /usr/bin/kex Happened to me. When I web searched, this problem seems to be happening a lot: Tiger: won't read password, won't connect etc If you open the Windows Terminal & open a Kali tab, it will open into Windows $HOME eg /mnt/c/Users/Username Somewhere, in one of the loaders, $HOME or $PWD seem to be getting muddled. Alternatively, type 'cd ~' every time you start .... |
|
|
Update: Needed to reboot Windows today, to get this to work .... ? |
 |
This is fixed in the latest release kali-win-kex release. |
