Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't use WLSg at all, apps freeze or are not responsible #643

Open
alansikora opened this issue Jan 25, 2022 · 55 comments
Open

Can't use WLSg at all, apps freeze or are not responsible #643

alansikora opened this issue Jan 25, 2022 · 55 comments
Labels
bug Something isn't working window-management Window management issue

Comments

@alansikora
Copy link

alansikora commented Jan 25, 2022

Environment

Windows build number: 10.0.22000.0
Your Distribution version: Ubuntu 21.04
Your WSLg version: Windows Subsystem for Linux WSLg Preview 1.0.26 (is this it?)

Steps to reproduce

Microsoft Edge:

It runs full screen, and everything works, the I try exiting full screen/resizing, and I can't input anything anymore. It just hangs and I need to close it.

Firefox:

  • sudo apt install firefox
  • firefox (or MOZ_ENABLE_WAYLAND=1 firefox)

It usually works, but it always freezes before I finish my work, it just stops accepting input then the WSL GUI Window can't be moved or closed. The only way to fix it is wsl --shutdown

Firefox WSL logs:

weston.log
pulseaudio.log
versions.txt.txt

Others

I also tried to run other GUI apps, they all evetually freeze.

Expected behavior

Not freeze.

Actual behavior

Freezing.

@alansikora alansikora added the bug Something isn't working label Jan 25, 2022
@hideyukn88
Copy link
Member

@alansikora, thanks for reporting the issue. Regarding to the issue with Edge, it sounds close to #272, if you haven't tried, try disabling GPU or run in Wayland native mode. For firefox, I have not heard/experienced such issue. If it only freeze firefox, please take core dump of firefox, or if entire WSLg is freezing (including other Linux GUI app), please do below to take core dump of weston running system-distro.

1: From Windows's command prompt, run "wsl --system" (note it's double minus)
2: It launch bash in system-distro, type "tdnf install gdb"
3: then find pid of /usr/bin/weston from "ps -aux"
4: then "gcore [weston's pid]".

Thanks!

@f-liva
Copy link

f-liva commented Feb 9, 2022

I also have the same problem with GitKraken. Every now and then it doesn't respond. I notice this because the context menus usually opened by right click no longer open. At that point the GUI stops responding and if I try to close the window it won't close. Only solution: wsl --shutdown.

I followed the steps described and this is the output shown by the console. Did I do this correctly?

[New LWP 19]
[New LWP 33]
[New LWP 34]
[New LWP 35]
[New LWP 36]
[New LWP 37]
[New LWP 38]
[New LWP 39]
[New LWP 40]
[New LWP 41]
[New LWP 42]
[New LWP 43]
[New LWP 44]
[New LWP 45]
[New LWP 46]
[New LWP 47]
[New LWP 48]
[New LWP 49]
[New LWP 50]
[New LWP 51]
[New LWP 52]
[New LWP 54]
[New LWP 55]
[New LWP 56]
[New LWP 57]
[New LWP 58]
[New LWP 59]
[New LWP 60]
[New LWP 61]
[New LWP 63]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
0x00007fb47af9fb6e in epoll_wait () from /lib/libc.so.6
warning: target file /proc/8/cmdline contained unexpected null characters
Saved corefile core.8
[Inferior 1 (process 8) detached]

@yangli2014
Copy link

Same problem with IntelliJ. I am running Windows 11.

@hideyukn88
Copy link
Member

@f-liva, yes, would you please share the core file with us, thanks!

@polypixeldev
Copy link

I am having this same issue with Firefox on WSL on Windows 11

@f-liva
Copy link

f-liva commented Feb 14, 2022

core.zip

@hideyukn88 here it is!

@ghost
Copy link

ghost commented Mar 21, 2022

I'm seeing this in VS Code also. Usually my menus stop working first (top bar menus and right click menus), but eventually things will just completely freeze up.

@slagbat
Copy link

slagbat commented Mar 23, 2022

I also have the same problem with GitKraken. Every now and then it doesn't respond. I notice this because the context menus usually opened by right click no longer open. At that point the GUI stops responding and if I try to close the window it won't close. Only solution: wsl --shutdown.

I followed the steps described and this is the output shown by the console. Did I do this correctly?

[New LWP 19]
[New LWP 33]
[New LWP 34]
[New LWP 35]
[New LWP 36]
[New LWP 37]
[New LWP 38]
[New LWP 39]
[New LWP 40]
[New LWP 41]
[New LWP 42]
[New LWP 43]
[New LWP 44]
[New LWP 45]
[New LWP 46]
[New LWP 47]
[New LWP 48]
[New LWP 49]
[New LWP 50]
[New LWP 51]
[New LWP 52]
[New LWP 54]
[New LWP 55]
[New LWP 56]
[New LWP 57]
[New LWP 58]
[New LWP 59]
[New LWP 60]
[New LWP 61]
[New LWP 63]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
0x00007fb47af9fb6e in epoll_wait () from /lib/libc.so.6
warning: target file /proc/8/cmdline contained unexpected null characters
Saved corefile core.8
[Inferior 1 (process 8) detached]

GitKraken does this for me too

@hideyukn88
Copy link
Member

@slagbat @f-liva, do you mean right click context menu is the one in below screen shot? I looked at core dump at #643 (comment), but unfortunately, I didn't find any clue.

@Poly-Pixel, @alansikora, I can't reproduce the issue with firefox or Edge either.

image

@ashikns
Copy link

ashikns commented Mar 23, 2022

+1 facing the same issue on Win11 while running Firefox

@slagbat
Copy link

slagbat commented Mar 23, 2022

@slagbat @f-liva, do you mean right click context menu is the one in below screen shot? I looked at core dump at #643 (comment), but unfortunately, I didn't find any clue.

@Poly-Pixel, @alansikora, I can't reproduce the issue with firefox or Edge either.

image

For me, I can use GitKraken for a short period of time and then it'll just stop working. I won't be able to move or resize the window or use any of its features. This also happens with Chrome too so I think it's just a general issue for me.

Update:

@hideyukn88 GitKraken just crashed on me so I tried to do a core dump but it's frozen doing that too! Sorry, I know that's probably no help at all!

@mquenzer
Copy link

mquenzer commented Mar 25, 2022

To me this seems to be a random effect which only occur on mouse right-clicks. I use Firefox, Eclipse and Smartgit in WSL-ubuntu. When the problem occures, all currently open wsl windows freeze and cannot be closed. The only way to get rid of them is to restart wsl.
I use ubuntu 20 and windows 11.

@yangli2014
Copy link

I gave up WSLg and use Kali Linux Win-KeX and it works much better than wslg.

@slagbat
Copy link

slagbat commented Apr 1, 2022

On further investigation this does only seem to happen to me when I right click for the context menu in Gitkraken and then select an option on said menu with a left click. Then everything freezes on all WSL GUI apps!

@hideyukn88
Copy link
Member

@slagbat, when everything freezes, would you please share the core file following instruction at #643 (comment)? Thanks!

@hideyukn88 hideyukn88 added the window-management Window management issue label Apr 1, 2022
@ferjul17
Copy link

I have the same problem. I tried to take a core dump, but it hangs... I tried to kill the core dump and restart it without any result.

In a first "wsl --system" session:

# ps -aux | grep weston
wslg        11  0.9  0.3 948232 60832 ?        Dl   09:39   0:23 /usr/bin/weston --backend=rdp-backend.so --xwayland --socket=wayland-0 --shell=rdprail-shell.so --logger-scopes=log,rdp-backend,rdprail-shell --log=/mnt/wslg/weston.log
wslg        22  0.0  0.0  15320  7692 ?        S    09:39   0:00 /usr/libexec/weston-rdprail-shell

# gcore 11 <-- It hangs...

I closed the terminal and reopen a new "wsl --system" session:

# gcore 11
warning: process 11 is already traced by process 3806
ptrace: Operation not permitted.
You can't do that without a process to debug.
The program is not being run.
gcore: failed to create core.11

# ps -aux | grep 3806
root      3806  0.0  0.1  23664 18540 ?        S    10:17   0:00 /usr/bin/gdb --nx --batch --readnever -ex set pagination off -ex set height 0 -ex set width 0 -ex attach 11 -ex gcore core.11 -ex detach -ex quit

# kill 3806

# ps -aux | grep 3806
root      3806  0.0  0.1  23664 18540 ?        S    10:17   0:00 /usr/bin/gdb --nx --batch --readnever -ex set pagination off -ex set height 0 -ex set width 0 -ex attach 11 -ex gcore core.11 -ex detach -ex quit

# kill -9 3806

# ps -aux | grep 3806

# gcore 11 <-- It hangs...

@UltraCakeBakery
Copy link

This issue has become the biggest blocker for continuing using WSLG for me. How can I contribute to debugging the root cause of this? It happens to me every time I try to resize my windows that are running in almost 4k resolution. I feel like there must be some overflow, race condition or bandwidth issue.

@ParhamG
Copy link

ParhamG commented Jun 14, 2022

WSLG is also freezing for me from time to time, mostly using JetBrains's PhpStorm, but when it freezes, it is all WSLG apps and not only JetBrain (e.g. Files as well). Also gcore [weston pid] hangs with no output.

@hideyukn88
Copy link
Member

@ParhamG, would you please share output from dmesg? thanks!

@slagbat
Copy link

slagbat commented Jun 15, 2022

@slagbat, when everything freezes, would you please share the core file following instruction at #643 (comment)? Thanks!

@hideyukn88 ...

I've tried this again with the same result as before and that is getting the gcore output is frozen on the command line. Here's a screenshot for good measure:

image

I don't know if this important but I also has an XWayland process running:

image

@gabepack
Copy link

I gave up WSLg and use Kali Linux Win-KeX and it works much better than wslg.

@yangli2014 thanks for the tip! I've been having tons of issues with WSLg, similar to those described in this issue. I'm spinning up on Win-KeX now. So far, so good.

https://www.kali.org/docs/wsl/win-kex/

@LionH
Copy link

LionH commented Jul 8, 2022

Have the same issue with IntelliJ, only fix is wsl --shutdown unfortunately

@f-liva
Copy link

f-liva commented Jul 9, 2022

I started using GWSL instead of WSLG and it works like a charm without ANY of WSLG issues. Give a try!

@SFurnace
Copy link

SFurnace commented Aug 8, 2022

Not sure whether it is the same issue. When I use PHPStorm or Goland in wslg, they often stuck on mouse event when I open a new IDE window, but I still can use keyboard to control them. Only fix is wsl --shutdown.

@lucasctd
Copy link

@SFurnace > Not sure whether it is the same issue. When I use PHPStorm or Goland in wslg, they often stuck on mouse event when I open a new IDE window, but I still can use keyboard to control them. Only fix is wsl --shutdown.

Same issue here, when I open PHPStorm/WebStorm it does not freeze but I can't do anything with my mouse, If I press "Tab" or run any keyboard shortcut the application will respond, but clicking on anything with my mouse will not work.
Tried on Ubuntu 20.04, 22.04 and 22.10.

@vermi0ffh
Copy link

I have the same issue, sometimes everything works fine for a whole day, sometimes it's a nightmare.
I'm using PHPStorm on Ubuntu 22.04 with docker.

@hideyukn88
Copy link
Member

@SFurnace, @lucasctd, @vermi0ffh, I have a few questions, when the mouse issue occurs, 1) does mouse still work with other Linux GUI applications? 2) Is the PHPStorm IDE window maximized? 3) Do you see any mouse activity with xev or xtrace? thanks!

@slagbat
Copy link

slagbat commented Sep 6, 2022

@SFurnace, @lucasctd, @vermi0ffh, I have a few questions, when the mouse issue occurs, 1) does mouse still work with other Linux GUI applications? 2) Is the PHPStorm IDE window maximized? 3) Do you see any mouse activity with xev or xtrace? thanks!

For me personally, once the issue happens all Linux GUI apps stop responding. I normally only have Gitkraken and Chrome running as Linux apps but both become unresponsive and I'm unable to close either of them.

I'm not sure how to see the mouse activity with xev or xtrace as I'm a bit of a Linux novice!

@hideyukn88
Copy link
Member

@slagbat, I'm feeling your case is different as I believe app won't respond on keyboard input either in your case, would you please share output from dmesg? thanks!

@vermi0ffh
Copy link

It looks like I have a really more stable WSLg recently. Since the begining of the week, no freeze at all.
I have some problems of stuck keys (I clic on a window, and a key I pressed keep repeating spontaneously. I juste press it a few times, and it stopped).

For the interface freeze, I removed some strange wacom driver present on my computer. It was an old driver (2009). Since it's removed, no more freeze (yet). I'll comment if it happens again, but maybe de problem is driver-related !

@RiccardoManzan
Copy link

I observed that if you launch docker desktop and your containers before launching intellij (or phpstorm or whatever) the freeze it's less likely for everything to stop.
I am trying to keep a gedit window open while using intellij in order to check if all apps stop working or if just intellij does.

@ParhamG
Copy link

ParhamG commented Sep 8, 2022

For me, it was not only freezes with PHPStorm but also other issues like menus not staying open and having to keep the mouse pressed down and then move to a submenu item and release it, and some other random issues. I switched back to WSLD+VcXsrv and that has been working perfectly fine.

@vermi0ffh
Copy link

I just had a freeze. Phpstorm was fullscreen, and I clicked the button to make it windowed. Just after that, it froze.
I tried to launch firefox from the prompt, it did not work.

Here is the dmesg of both the system vm and the ubuntu VM running PhpStorm :
ubuntu.dmesg.freeze.txt
system.dmesg.freeze.txt

@unixdaddy
Copy link

Wslg is unusable on 32GB Dell xps - it kills my machine everything hangs.

@JuradoBruno
Copy link

JuradoBruno commented Nov 10, 2022

🟢 I had the same problem and finally found a brilliant solution:

  • Follow this very easy tutorial to setup an X server on your machine: https://chuckdries.medium.com/installing-gitkraken-in-wsl-2-15bf6459f823 -> I personally skipped the firewall part, it took me 15 minutes max.

  • Open a cmd shell (Win+R), type shell:startup and put the config.xlaunch file that was created previously in the startup folder that opened. This will execute the file automatically on startup, starting your X server👏

  • that's it, no more pain.

So in the end, in the /home directory of my Ubuntu file system I added 3 lines in the .bashrc: file :

export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0
export GDK_SCALE=1
alias gk='gitkraken' # Cadeau 🎁

The result is actually better than the wslg proposed by Windows, now your Linux apps eg: Gitkraken will use your usual Windows UI and resize/snap perfectly 👌
I did the change one week ago and I had ZERO issues since then while working 9 hours a day.
Before that, my Gitkraken would freeze at least once a day and I had to shutdown my WSL. To then painfully restart all my npm commands again.

There's no reason this solution doesn't work for you, give it a try,
Commenting your results here would be nice 🎯

ℹ️
The X server is typically the provider of graphics resources and keyboard/mouse events to X clients, meaning that the X server is usually running on the computer in front of a human user, while the X client applications run anywhere on the network and communicate with the user's computer to request the rendering of ..

@azinsharaf
Copy link

azinsharaf commented Apr 25, 2023

@JuradoBruno Thanks for this. I have a question. I have configured the xserver as mentioned but when i launch the Linux apps on WSL2 it seems it still wslg is being involved since it is still freezing. How did you force the apps to use xserver?

EDIT: I noticed if i launnch the app from start menu ( i tested qutebrowser) it used wslg but if I run it from terminal it uses this new xserver. But i prefer to run it from start menu because for some reason when i launch it from terminal then the terminal is busy and i have to create a tab and keep it open for each app i wanna use.

@xiy73986
Copy link

I think Microsoft doesn't want to fix this issue. The WSL2 is designed to work in terminal mode. Microsoft doesn't want to drive the applications development of linux destop. So if you want to use WSL2, but only use it in terminal.

@foinf
Copy link

foinf commented Dec 19, 2023

I think Microsoft doesn't want to fix this issue. The WSL2 is designed to work in terminal mode. Microsoft doesn't want to drive the applications development of linux destop. So if you want to use WSL2, but only use it in terminal.

Yeah I gave up as well. My use case was running a linux music app called sublime-music. Due to a very specific usecase, I needed to be able to run that. It does run but then it just hangs and nothing responds. All I can do it kill entire wsl2 for that reason only.

Anyone has any other ideas (short of running a full VM ) ?

@yangli2014
Copy link

Try Kali Linux as wsl2 distro

@hideyukn88
Copy link
Member

@xiy73986, @foinf, thanks for keep updating and we understand your frustration, and of course, we would like to address this issue, but due to luck of the scenario to reproduce in house, blocks us to investigate further. If you could share any clue, very much appreciated, thanks!

@eric-gitta-moore
Copy link

I gave up WSLg and use Kali Linux Win-KeX and it works much better than wslg.

Sorry to interrupt, but I'm using kex, too. But I can't seem to call the NVIDIA graphics card

@yangli2014
Copy link

yangli2014 commented Jan 8, 2024 via email

@eric-gitta-moore
Copy link

Let me check my environment. I am using Nvidia too.

On Sun, Jan 7, 2024, 23:26 Nancy Harris @.> wrote: I gave up WSLg and use Kali Linux Win-KeX and it works much better than wslg. Sorry to interrupt, but I'm using kex, too. But I can't seem to call the NVIDIA graphics card — Reply to this email directly, view it on GitHub <#643 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEXQGXAJEXB5DBSQEH24XDYNNYQXAVCNFSM5MZEBVR2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBYGAZTMOJRGQZA . You are receiving this because you were mentioned.Message ID: @.>

Thank you very much for your time.

I just checked google chrome's video decoding capabilities and OpenGL support.

Here are my results.

❯ google-chrome                                                                                                                                                                   
[5119:5214:0108/211915.737417:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[5119:5214:0108/211915.737665:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[5119:5214:0108/211915.737872:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[5155:5155:0108/211916.786292:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
[5155:5155:0108/211916.786534:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Invalid visual ID requested.
[5155:5155:0108/211916.786622:ERROR:gl_display.cc(786)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[5155:5155:0108/211916.787945:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
[5155:5155:0108/211916.788489:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Invalid visual ID requested.
[5155:5155:0108/211916.788573:ERROR:gl_display.cc(786)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[5155:5155:0108/211916.788688:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
[5155:5155:0108/211916.788768:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[5155:5155:0108/211916.798631:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
[5155:5155:0108/211916.798730:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Invalid visual ID requested.
[5155:5155:0108/211916.798819:ERROR:gl_display.cc(786)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[5155:5155:0108/211916.799208:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Invalid visual ID requested.
[5155:5155:0108/211916.799277:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Invalid visual ID requested.
[5155:5155:0108/211916.799335:ERROR:gl_display.cc(786)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[5155:5155:0108/211916.799398:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
[5155:5155:0108/211916.799455:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[5155:5155:0108/211916.844923:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[5195:7:0108/211916.967385:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[5159:5164:0108/211917.270316:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -100
[5159:5164:0108/211917.557519:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -100
[5159:5164:0108/211920.058329:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -100
[5159:5164:0108/211920.309383:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -100
[5159:5164:0108/211920.364844:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -100
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_intel.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so supports Vulkan 1.1, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: Layer VK_LAYER_MESA_device_select uses API version 1.2 which is older than the application specified API version of 1.3. May cause issues.
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.

image

@yangli2014
Copy link

yangli2014 commented Jan 8, 2024 via email

@eric-gitta-moore
Copy link

@yangli2014 Sorry, the message I saw on github was [image: image.png] , not image. 😥

@yangli2014
Copy link

image

@yangli2014
Copy link

yangli2014 commented Jan 8, 2024 via email

@eric-gitta-moore
Copy link

eric-gitta-moore commented Jan 8, 2024

image

Thank you very much. I can see that. It's pretty awesome. Could I please confirm how you started VcXsrv?

  1. vcxsrv.exe -ac -multiwindow -clipboard
  2. run export DISPLAY=$(grep -m 1 nameserver /etc/resolv.conf | awk '{print $2}'):0.0
  3. type google-chrome to start chrome
  4. type url chrome://gpu then tap enter
  5. Now I see the screenshot I uploaded earlier

my env
wsl:

❯ cat /etc/os-release      
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

window:

(base) PS C:\Users\win> wsl -v
WSL version: 2.0.14.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2861

@yangli2014
Copy link

yangli2014 commented Jan 8, 2024 via email

@eric-gitta-moore
Copy link

I will get back to you later. I start working now. I am in the Ontarion Canada

On Mon, Jan 8, 2024 at 9:15 AM Nancy Harris @.> wrote: [image: image] https://private-user-images.githubusercontent.com/9009178/294926812-6d269cb8-5c76-4093-b929-330aee0d9dcc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQ3MjMxMjMsIm5iZiI6MTcwNDcyMjgyMywicGF0aCI6Ii85MDA5MTc4LzI5NDkyNjgxMi02ZDI2OWNiOC01Yzc2LTQwOTMtYjkyOS0zMzBhZWUwZDlkY2MucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDEwOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDAxMDhUMTQwNzAzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTNkNDI0OWZiMWUyZjA3ODJiOTczNTBkNmQ1OTBjMGEyYjZjNDAzZjIwYWM4ZjQyODg4NDM2MzFmNjk4YzgzOCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.sugDloh0MBUAiPWc_zkGB6wY02XFCKazUMqbaeJArts Thank you very much. I can see that. It's pretty awesome. Could I please confirm how you started VcXsrv? 1. vcxsrv.exe -ac -multiwindow -clipboard 2. type google-chrome to start chrome 3. type url chrome://gpu then tap enter 4. Now I see the screenshot I uploaded earlier my env wsl: ❯ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.6 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.6 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal window: (base) PS C:\Users\win> wsl -v WSL version: 2.0.14.0 Kernel version: 5.15.133.1-1 WSLg version: 1.0.59 MSRDC version: 1.2.4677 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22621.2861 — Reply to this email directly, view it on GitHub <#643 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEXQGS57LVXIYT23E7B5F3YNP5PXAVCNFSM5MZEBVR2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBYGEYDSMZRGA4Q . You are receiving this because you were mentioned.Message ID: @.>
-- Yang Li Kanata ON Canada

Okay, thanks for your time. Good luck.

@yangli2014
Copy link

yangli2014 commented Jan 9, 2024

My system is Windows 11 Pro with WSL2

└─$ cat /etc/os-release
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION_ID="2023.4"
VERSION="2023.4"
VERSION_CODENAME=kali-rolling
ID=kali
ID_LIKE=debian
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
ANSI_COLOR="1;31"
C:\Cmder
wsl -l -v
  NAME                   STATE           VERSION
* kali-linux             Running         2
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

@eric-gitta-moore
Copy link

My system is Windows 11 Pro with WSL2

└─$ cat /etc/os-release
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION_ID="2023.4"
VERSION="2023.4"
VERSION_CODENAME=kali-rolling
ID=kali
ID_LIKE=debian
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
ANSI_COLOR="1;31"
C:\Cmder
wsl -l -v
  NAME                   STATE           VERSION
* kali-linux             Running         2
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

I got it. Hardware acceleration cannot be turned on using seamless mode, and I have no problem using enhanced session.

@eric-gitta-moore
Copy link

My system is Windows 11 Pro with WSL2

└─$ cat /etc/os-release
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION_ID="2023.4"
VERSION="2023.4"
VERSION_CODENAME=kali-rolling
ID=kali
ID_LIKE=debian
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
ANSI_COLOR="1;31"
C:\Cmder
wsl -l -v
  NAME                   STATE           VERSION
* kali-linux             Running         2
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

I got it. Hardware acceleration cannot be turned on using seamless mode, and I have no problem using enhanced session.

I'm guessing if your seamless mode supports hardware acceleration, your chrome browser probably has a white ring around it, which should be displayed via wslg. In Task Manager, you can locate the display as msrdc.exe

@yangli2014
Copy link

yangli2014 commented Jan 9, 2024 via email

@eric-gitta-moore
Copy link

@yangli2014 Since my default development environment is Ubuntu wsl2, but after seeing your wsl environment and suspecting that Ubuntu does not support hardware acceleration, I also downloaded a kali test. It turns out the same is true for kali and Ubuntu. Only seamless Windows displayed through wslg have hardware decoding capabilities. In addition, enhanced mode and vnc mode using win-kex under kali linux also support hardware decoding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working window-management Window management issue
Projects
None yet
Development

No branches or pull requests