You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cursor disappearing on multi monitor configuration #160
When I open a WSL GUI app and move the app to a different monitor I should be able see my mouse cursor and continue to interact with the app.
Actual behavior
I have a monitor configuration like this:
where monitor 4 is my primary monitor.
When I open a WSL app (tested with gedit and others), it open as expected and I can interact and use it as expected. However, if I move the application (by dragging it) to either of my monitors on the left side (2 and 3), the mouse cursor no longer appears over the application. The mouse cursor still interacts with the application but I just can't see the cursor. If I move the application back to either of the monitors on the right side (4 and 1) the mouse cursor is visible again when over the top of the application.
Josh (@joshward) , thanks for reporting the issue. Unfortunately I don't have 4 monitors on hand, so I can't try on exact your condition, but relocating around 3 monitors in any way, it's working for me. Thus, I would like to ask a few questions to help narrow down the cause.
1: Keeping all 4 monitors enabled, but change the primary to the most upper-left monitor, 3 in your picture, so all coordinate (in Windows side) become positive space, does mouse disappear on any monitor ?
2: Keeping 4 as your primary monitor and you disabled monitors at negative Y space, which is 3 and 1, and keeping 2 and 4 enabled, then moving a window to 2, does mouse cursor disappears ? And same to negative X space, disabling 3 and 2, and moving a window to 1 makes cursor disappears ?
3: do you install any sort of mouse driver or tools (such as Logitech Options) in Windows side or have some accessibility software running ?
Thanks for looking into this. Here's the follow up to your tests:
Changing my primary monitor to the upper left (3) monitor corrects the issue.
Just to try more things, I made my lower left monitor (2) the primary and it also corrected the issue. However, making the upper right monitor (1) the primary does not correct the issue.
Disabling monitors 1 and 3 and only leaving 2 and 4 enabled with 4 being the primary also corrects the issue. Likewise, there is no issue when I only have 1 and 4 enabled with 4 being my primary.
Just to try more things, I disabled only 3 (4 still being primary) and still had the issue. However, oddly enough disabling only 2 with 4 still being primary solves the issue.
I don't have any specialty mouse drivers/tools or accessibility software running. The only thing that I can think of that might cause issues is Ultramon; just to be sure I closed the application but still had the issue.
Thanks for looking at this, I'm happy to help continue to diagnose anything else.
Josh (@joshward) , I'm still not able to reproduce this problem locally, so please do following
1: launch gedit.
2: move gedit to the monitor where has pointer visible issue.
3: while gedit has input focus, press L-CTRL then L-SHIFT (while holding L-CTRL) then SPACE (while holding L-CTRL and L-SHIFT) , then release all key, then press 'w' key.
4: please check /mnt/wslg/weston.log and it should have "rdp debug binding 'W' - dump all window from window hash_table." and all information about window. If you don't see this, please try key combo at 3 again.
5: please send entire that debug section to me.
I can confirm, this happens to me too on a 3 Monitor side by side configuration. Since I am going over usb-c for 2 of the monitors I suspect Displaylink to be the culprit, though. Will also try to get the logs.
Here is my weston.log (I tested using google-chrome from within wsl).
Note the mouse works in chrome, but not on the surrounding container window, so once I move the window to one of the other screens, I can no longer move it, minimize, maximize or resize the window as the mouse disappears in those regions.
Stefan Rybacki (@stefanrybacki), we changed the way update works when "pre-release" builds are currently installed, 1.0.21 is the one of those "pre-release" build. (see #302). At this point, you have two options, you can install 1.0.23 (or 1.0.24) from our release page by downloading MSI https://github.com/microsoft/wslg/releases, or wait 1.0.24 become official release, then wsl --update should work. thanks!.
Activity
hideyukn88 commentedon May 13, 2021
Josh (@joshward) , thanks for reporting the issue. Unfortunately I don't have 4 monitors on hand, so I can't try on exact your condition, but relocating around 3 monitors in any way, it's working for me. Thus, I would like to ask a few questions to help narrow down the cause.
1: Keeping all 4 monitors enabled, but change the primary to the most upper-left monitor, 3 in your picture, so all coordinate (in Windows side) become positive space, does mouse disappear on any monitor ?
2: Keeping 4 as your primary monitor and you disabled monitors at negative Y space, which is 3 and 1, and keeping 2 and 4 enabled, then moving a window to 2, does mouse cursor disappears ? And same to negative X space, disabling 3 and 2, and moving a window to 1 makes cursor disappears ?
3: do you install any sort of mouse driver or tools (such as Logitech Options) in Windows side or have some accessibility software running ?
Thanks!
joshward commentedon May 14, 2021
Hideyuki Nagase (@hideyukn88)
Thanks for looking into this. Here's the follow up to your tests:
Changing my primary monitor to the upper left (3) monitor corrects the issue.
Just to try more things, I made my lower left monitor (2) the primary and it also corrected the issue. However, making the upper right monitor (1) the primary does not correct the issue.
Disabling monitors 1 and 3 and only leaving 2 and 4 enabled with 4 being the primary also corrects the issue. Likewise, there is no issue when I only have 1 and 4 enabled with 4 being my primary.
Just to try more things, I disabled only 3 (4 still being primary) and still had the issue. However, oddly enough disabling only 2 with 4 still being primary solves the issue.
I don't have any specialty mouse drivers/tools or accessibility software running. The only thing that I can think of that might cause issues is Ultramon; just to be sure I closed the application but still had the issue.
Thanks for looking at this, I'm happy to help continue to diagnose anything else.
hideyukn88 commentedon May 24, 2021
Josh (@joshward) , I'm still not able to reproduce this problem locally, so please do following
1: launch gedit.
2: move gedit to the monitor where has pointer visible issue.
3: while gedit has input focus, press L-CTRL then L-SHIFT (while holding L-CTRL) then SPACE (while holding L-CTRL and L-SHIFT) , then release all key, then press 'w' key.
4: please check /mnt/wslg/weston.log and it should have "rdp debug binding 'W' - dump all window from window hash_table." and all information about window. If you don't see this, please try key combo at 3 again.
5: please send entire that debug section to me.
Thanks!
stefanrybacki commentedon May 24, 2021
I can confirm, this happens to me too on a 3 Monitor side by side configuration. Since I am going over usb-c for 2 of the monitors I suspect Displaylink to be the culprit, though. Will also try to get the logs.
joshward commentedon May 24, 2021
Hideyuki Nagase (@hideyukn88)
Here is the log file you requested.
weston.log
stefanrybacki commentedon May 27, 2021
Here is my weston.log (I tested using google-chrome from within wsl).
Note the mouse works in chrome, but not on the surrounding container window, so once I move the window to one of the other screens, I can no longer move it, minimize, maximize or resize the window as the mouse disappears in those regions.
weston.log
amivanoff commentedon May 29, 2021
The same issue on latest Ubuntu 20.04 with 3 monitors. Mouse pointer works on 1st (main) and 3rd monitors and disappears on 2nd monitor.

hideyukn88 commentedon Jun 9, 2021
Hi, all. Would you please try WSLg 1.0.23, https://github.com/microsoft/wslg/releases/tag/v1.0.23, to check if this issue is fixed? thanks!
joshward commentedon Jun 10, 2021
Hideyuki Nagase (@hideyukn88) Confirmed! 1.0.23 fixes the issue for me. Thank you!
hideyukn88 commentedon Jun 10, 2021
Josh (@joshward), thank you very much for confirming it. I think microsoft/weston-mirror#16 addresses this, thanks!
stefanrybacki commentedon Jun 11, 2021
It is not fixed for me. How can I confirm, I installed 1.0.23 correctly, to make sure the fix is actually running?
hideyukn88 commentedon Jun 11, 2021
Stefan Rybacki (@stefanrybacki) , you can check /mnt/wslg/versions.txt. thanks!
WSLg ( aarch64 ): 1.0.23+Branch.main
stefanrybacki commentedon Jun 21, 2021
Hideyuki Nagase (@hideyukn88) ok it shows 1.0.21, how to I update to 1.0.23 or higher,
wsl --updatethrows an error.hideyukn88 commentedon Jun 21, 2021
Stefan Rybacki (@stefanrybacki), we changed the way update works when "pre-release" builds are currently installed, 1.0.21 is the one of those "pre-release" build. (see #302). At this point, you have two options, you can install 1.0.23 (or 1.0.24) from our release page by downloading MSI https://github.com/microsoft/wslg/releases, or wait 1.0.24 become official release, then wsl --update should work. thanks!.
stefanrybacki commentedon Jun 21, 2021
Hideyuki Nagase (@hideyukn88) thanks for the information, however I ran the 1.0.24 x64 msi, restarted but still see this in the versions.txt file:
And then I see this also under installed apps and features:

So something is wrong. Any ideas what is going on?
Never mind
I uninstalled wslg using apps and features shown above and ran the msi again and now it is showing 1.0.24 installed.
stefanrybacki commentedon Jun 21, 2021
I can now also confirm the mouse problem is gone for me too, thanks for fixing this.