Skip to content

x stops working shortly after restart on WSL2/Win10 #12260

Open

Description

Windows Version

10.0.19045.5011

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.10 (Oracular Oriole)

Other Software

No response

Repro Steps

For the past year or two, I've been using X/wslg with no problem. Starting recently, however, I observe different behavior. I'm not sure if this is from a WSL update or perhaps an Ubuntu update--I haven't changed anything else on my system that I'm aware of.

When I launch WSL2, I'm able to open X apps from the command-line without a problem. After a few minutes, though, I get Error: Can't open display: :0. Restarting WSL fixes the issue for a short while and then it reverts again.

Where can I look to narrow down the issue?

Some older postings suggest looking at firewall rules but disabling Windows Defender on the vEthernet NICs does not help, and I don't see any inbound rules for VcXsrv (nor any active VcXsrv pids).

Expected Behavior

X app should open

Actual Behavior

X app does not open

Diagnostic Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions