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

add tag for issues of WSL on Intel and ARM64 devices separately. #6817

Closed
mbalcerzyk opened this issue Apr 17, 2021 · 3 comments
Closed

add tag for issues of WSL on Intel and ARM64 devices separately. #6817

mbalcerzyk opened this issue Apr 17, 2021 · 3 comments
Labels

Comments

@mbalcerzyk
Copy link

Is your feature request related to a problem? Please describe.
Some issues of WSL are solved long time ago, but they exist in WSL2 on ARM64 Windows.
Examples:

  1. firefox can be run smoothly on Intel PC with Ubuntu and VcXsrv, however the ARM64 Ubuntu with Xwindows VcXsrv it starts but each tab is crashing. Errors in console show Firefox looking and not finding GPU. Disabling hardware acceleration in settings does not help.
  2. Chromium web browser exists as a build for ARM64 and can be installed on Ubuntu but trying to run chromium-browser requires "snap install chromium", which is not implemented in WSL. On Intel, you can simply install microsoft-edge.

Describe the solution you'd like
Additional tag for WSL on ARM64 Windows.

@DHowett
Copy link
Member

DHowett commented Apr 17, 2021

But.. neither of those seem to be issues with WSL? Missing snap support is well-known, and graphical applications are explicitly unsupported. Filing them again and tagging them with “arm64” will not change those facts. 😄

@craigloewen-msft
Copy link
Member

Our goal is for ARM64 to have the same user experience as x64 with WSL. As Dustin mentioned, both of the problems above are understood, snaps is not yet supported as we don't have systemd support, and GUI apps are (not yet) supported. Those issues are not unique to ARM64 devices. If you do find something ARM64 specific our current mode of operation is to handle that just like any other bug :) I'll close this issue out for our bookkeeping as I don't believe there's anything here actionable for the team, but please feel free to continue the discussion if you like!

@hwine
Copy link

hwine commented Jun 13, 2023

While the OP gave bad examples, the issue of "works everywhere but ARM64" still appears to exist, and consistent labeling would be helpful. Current examples:

I know triaging such a large project is a challenge, but at least the 2 bugs above are both "arm64 doesn't work the same as amd64". There may be more, per this query.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants