unconfinePointer / GLFW_CURSOR_DISABLED

[User65-87-11]

Windows Version

Windows 11 10.0.26100 N/A Build 26100

WSL Version

WSL version: 2.6.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Debian

Other Software

No response

Repro Steps

Using glfw

glfwSetInputMode(window, GLFW_CURSOR, GLFW_CURSOR_DISABLED);

glfwSetCursorPosCallback(window, mouseCallback);

void mouseCallback(GLFWwindow* window, double xposIn, double yposIn){
printf("Coords: %f, %f\n",xposIn,yposIn);
}

Expected Behavior

Expected the function to be called with cursor coordinates.

Actual Behavior

no input is printed, the function isn't called.

Diagnostic Logs

No response

[github-actions]

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-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[User65-87-11]

/question

yeah it's kind of question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[User65-87-11]

/question

…

On Thu, Apr 2, 2026 at 12:36 PM github-actions[bot] < ***@***.***> wrote: *github-actions[bot]* left a comment (microsoft/WSL#40073) <#40073 (comment)> 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 <https://github.com/Microsoft/WSL/blob/master/diagnostics/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-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues <https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues> Once completed please upload the output files to this GitHub issue. See Collect WSL logs (recommended method) <https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method> . If you choose to email these logs instead of attaching them to the bug, please send them to ***@***.*** with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'. — Reply to this email directly, view it on GitHub <#40073?email_source=notifications&email_token=BB3CH666UEQYHUVFVDM2NET4TYYB3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJXGU4TKNZYGM42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4175957839>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BB3CH6ZDUMI4KOCU56O4GEL4TYYB3AVCNFSM6AAAAACXKLH2L6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNZVHE2TOOBTHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Andrei Svetlov

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[chemwolf6922]

Hi @User65-87-11, This is likely a limitation of WSLg. Could you please transfer this to the https://github.com/microsoft/wslg repo so they may help take a look? Thanks.

[User65-87-11]

Ok