Run Linux GUI apps on the Windows Subsystem for Linux not working
Windows Version
10.0.26100.4202
WSL Version
2.5.7.0
Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
Kernel Version
6.6.87.1
Distro Version
kali linux
Other Software
spronovo@OFFICE:~$: command not found
-bash: syntax error near unexpected token `x86_64'
Mariner:: command not found
FreeRDP:: command not found
Command 'weston:' not found, did you mean:
command 'weston' from deb weston
Try: sudo apt install
Repro Steps
just try to follow the steps
Expected Behavior
i expected to see it go smoothly
Actual Behavior
Script started on 2025-06-10 03:42:25-07:00 [TERM="xterm-256color" TTY="/dev/pts/0" COLUMNS="98" LINES="49"] [?2004h]0;julesverne@nevada: ~ [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m~[;32m] [;32m└─[1;34m$[0m [7mscriptreplay timing.log session.log[27m [C[C[C[Cscriptreplay timing.log session.log [?2004l
[?2004h]0;julesverne@nevada: ~ [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m~[;32m] [;32m└─[1;34m$[0m find [7mtiming.log session.log[27m [C[C[C[C[C[C[C[C[Ctiming.log session.log [?2004l timing.log session.log
[?2004h]0;julesverne@nevada: ~ [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m~[;32m] [;32m└─[1;34m$[0m find [7mtiming.log[27mtiming.log [?2004l timing.log
[?2004h]0;julesverne@nevada: ~ [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m~[;32m] [;32m└─[1;34m$[0m find --help [?2004l Usage: find [-H] [-L] [-P] [-Olevel] [-D debugopts] [path...] [expression]
Default path is the current directory; default expression is -print. Expression may consist of: operators, options, tests, and actions.
Operators (decreasing precedence; -and is implicit where no others are given): ( EXPR ) ! EXPR -not EXPR EXPR1 -a EXPR2 EXPR1 -and EXPR2 EXPR1 -o EXPR2 EXPR1 -or EXPR2 EXPR1 , EXPR2
Positional options (always true): -daystart -follow -nowarn -regextype -warn
Normal options (always true, specified before other expressions): -depth -files0-from FILE -maxdepth LEVELS -mindepth LEVELS -mount -noleaf -xdev -ignore_readdir_race -noignore_readdir_race
Tests (N can be +N or -N or N): -amin N -anewer FILE -atime N -cmin N -cnewer FILE -context CONTEXT -ctime N -empty -false -fstype TYPE -gid N -group NAME -ilname PATTERN -iname PATTERN -inum N -iwholename PATTERN -iregex PATTERN -links N -lname PATTERN -mmin N -mtime N -name PATTERN -newer FILE -nouser -nogroup -path PATTERN -perm [-/]MODE -regex PATTERN -readable -writable -executable -wholename PATTERN -size N[bcwkMG] -true -type [bcdpflsD] -uid N -used N -user NAME -xtype [bcdpfls]
Actions: -delete -print0 -printf FORMAT -fprintf FILE FORMAT -print -fprint0 FILE -fprint FILE -ls -fls FILE -prune -quit -exec COMMAND ; -exec COMMAND {} + -ok COMMAND ; -execdir COMMAND ; -execdir COMMAND {} + -okdir COMMAND ;
Other common options: --help display this help and exit --version output version information and exit
Valid arguments for -D: exec, opt, rates, search, stat, time, tree, all, help Use '-D help' for a description of the options, or see find(1)
Please see also the documentation at https://www.gnu.org/software/findutils/. You can report (and track progress on fixing) bugs in the "find" program via the GNU findutils bug-reporting page at https://savannah.gnu.org/bugs/?group=findutils or, if you have no web access, by sending email to [email protected].
[?2004h]0;julesverne@nevada: ~ [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m~[;32m] [;32m└─[1;34m$[0m look [7mtiming.log[27mtiming.log [?2004l [?2004h]0;julesverne@nevada: ~ [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m~[;32m] [;32m└─[1;34m$[0m cd / [?2004l [?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m ls [?2004l [0m[01;36mbin[0m [01;34mdev[0m [01;34mhome[0m [01;36mlib[0m [01;34mlost+found[0m [01;34mmnt[0m [01;34mproc[0m [01;34mrun[0m [01;34msrv[0m [30;42mtmp[0m [01;34mvar[0m [01;34mboot[0m [01;34metc[0m [01;32minit[0m [01;36mlib64[0m [01;34mmedia[0m [01;34mopt[0m [01;34mroot[0m [01;36msbin[0m [01;34msys[0m [01;34musr[0m
[?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd tmp [?2004l [?2004h]0;julesverne@nevada: /tmp [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/tmp[;32m] [;32m└─[1;34m$[0m ls [?2004l [0m[01;34mhsperfdata_root[0m [01;34msystemd-private-03ddba0e11be416c8b4748f6f9d88bb1-systemd-logind.service-UncLI9[0m [01;34msystemd-private-173eb544d67d4baeb421e400bbd54559-systemd-logind.service-IPCZ09[0m [01;34msystemd-private-32c9b8d41981458d96573e416b81f04a-systemd-logind.service-g5AzHX[0m [01;34msystemd-private-5080b842747647f3b4621ab67c1c4a05-systemd-logind.service-jBCr1L[0m [01;34msystemd-private-85ffe9806ccc4f3e936106bfecb8afc1-polkit.service-oG1w80[0m [01;34msystemd-private-85ffe9806ccc4f3e936106bfecb8afc1-power-profiles-daemon.service-k1zuYo[0m [01;34msystemd-private-85ffe9806ccc4f3e936106bfecb8afc1-systemd-logind.service-y074mm[0m [01;34msystemd-private-85ffe9806ccc4f3e936106bfecb8afc1-upower.service-gFY7Rf[0m [01;34msystemd-private-a9a647d2fedb4a7e985f77c479ef9ece-systemd-logind.service-mXhwaG[0m [01;34mtmp.PLY4mgUKeX[0m
[?2004h]0;julesverne@nevada: /tmp [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/tmp[;32m] [;32m└─[1;34m$[0m cd / [?2004l [?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd init [?2004l bash: cd: init: Not a directory
[?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd init[K[K[K[Kmedia [?2004l [?2004h]0;julesverne@nevada: /media [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/media[;32m] [;32m└─[1;34m$[0m ls [?2004l [?2004h]0;julesverne@nevada: /media [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/media[;32m] [;32m└─[1;34m$[0m lscd media[1Pinit/[K [?2004l [?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd home/users/me [?2004l bash: cd: home/users/me: No such file or directory
[?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd home/users/me[1P/me [?2004l bash: cd: home/user/me: No such file or directory
[?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd home/user/me/home/user/me [C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[Cs/mecusers/me/users/me [?2004l bash: cd: /home/c/users/me: No such file or directory
[?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd /home/c/users/me[C[1P/me [?2004l bash: cd: /home/c/user/me: No such file or directory
[?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd /home/c/user/me[K[K[K[K[K[K[K[K [?2004l bash: cd: /home/c: No such file or directory
[?2004h]0;julesverne@nevada: / [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/[;32m] [;32m└─[1;34m$[0m cd /home/c[K[K [?2004l [?2004h]0;julesverne@nevada: /home [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/home[;32m] [;32m└─[1;34m$[0m ls [?2004l [0m[01;34mjulesverne[0m
[?2004h]0;julesverne@nevada: /home [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/home[;32m] [;32m└─[1;34m$[0m lscd /home/julesverne/c [?2004l bash: cd: /home/julesverne/c: No such file or directory
[?2004h]0;julesverne@nevada: /home [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m/home[;32m] [;32m└─[1;34m$[0m cd /home/julesverne/c[K[K [?2004l [?2004h]0;julesverne@nevada: ~ [;32m┌──([1;34mjulesverne㉿nevada[;32m)-[[0;1m~[;32m] [;32m└─[1;34m$[0m ls [?2004l cuda_12.9.1_575.57.08_linux.run [0m[01;34mDesktop[0m [01;34mDownloads[0m [01;34mPictures[0m session.log timing.log [01;34mVideos
Diagnostic Logs
No response
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1
The script will output the path of the log file once done.
If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here
Once completed please upload the output files to this Github issue.
Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
Hi @ngoodwill22, what are you trying to run? It's not clear from your issue.
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.
Thank you!