sileshn/manjarowsl2

Manjaro for WSL2 using wsldl

manjarowsl2's Issues

Can't install some packages through pacman.

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.19045.3324]

Kernel Version

5.15.90.1

Repro Steps

Run sudo pacman -S nasm

Expected Behavior

Nasm being installed.

Actual Behavior

~/s/c/asmtest > sudo pacman -S nasm        
[sudo] password for taitep: 
error: wslutilities: signature from "WSL Utilities Package Signing Key <[email protected]>" is unknown trust
error: database 'wslutilities' is not valid (invalid or corrupted database (PGP signature))

Request dnsutils package be added as part of the base image.

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.22621.1992]

Kernel Version

Kernel version: 5.15.90.1

Repro Steps

Attempt to perform a nslookup with base image.

$ nslookup

Expected Behavior

nslookup should be present and perform the needful lookup

Actual Behavior

The command isn't available in the base MarjaroWSL2 image so you get a command not found error.
This is part of the dnsutils package.

Having these tools available the ability to download packages in order to diagnose DNS related network issues. This is especially important in WSL in environments where you're connection is routed through a VPN. In this case DNS traffic to "normal" DNS servers may be blocked.

GPU integration with ManjaroWSL2

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.22631.2861]

Kernel Version

5.15.146.1-microsoft-standard-WSL2

Repro Steps

I came into this while using hashcat:
hashcat -I
hashcat (v6.2.6) starting in backend information mode

clGetPlatformIDs(): CL_PLATFORM_NOT_FOUND_KHR

ATTENTION! No OpenCL, HIP or CUDA compatible platform found.

You are probably missing the OpenCL, CUDA or HIP runtime installation.

* AMD GPUs on Linux require this driver:
  "AMDGPU" (21.50 or later) and "ROCm" (5.0 or later)
* Intel CPUs require this runtime:
  "OpenCL Runtime for Intel Core and Intel Xeon Processors" (16.1.1 or later)
* NVIDIA GPUs require this runtime and/or driver (both):
  "NVIDIA Driver" (440.64 or later)
  "CUDA Toolkit" (9.0 or later)
  

Despite nvidia-smi finding my 4070 gpu.

Is there a way to apply computation via my host GPU?
Seems Nvidia supports easy installation for Ubuntu, and hints on installing nvidia-toolkit-12-x alone to handle this on other distros.
https://docs.nvidia.com/cuda/wsl-user-guide/index.html#getting-started-with-cuda-on-wsl

Expected Behavior

It would be nice to be able to run GPU processes on the WSL side, might be beneficial for machine learning or hash cracks...

Actual Behavior

I can detect the GPU with nvidia-smi, but cant using clinfo, hashcat, or johntheripper.

Can not open manjaro this time

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.22621.819]

Kernel Version

can not open manjaro

Repro Steps

use wsl.exe to run manjaro.

Expected Behavior

灾难性故障
Error code: Wsl/Service/CreateInstance/E_UNEXPECTED

[已退出进程，代码为 4294967295 (0xffffffff)]

Actual Behavior

manjaro is open

Orphan removal causes ManjaroWSL2 Catastrophic failure

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.19044.2728]

Kernel Version

5.15.90.1-microsoft-standard-WSL2

Repro Steps

1. Use $ sudo pacman -Rs $(pacman -Qdtq) to remove orphans, according to Manjaro official Wiki
2. Shutdown and restart

Expected Behavior

https://wiki.manjaro.org/index.php/Pacman_Overview#Viewing_and_Removing_Orphans

Actual Behavior

I can't run Manjaro

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.19045.2546]

Kernel Version

No response

Repro Steps

Just run Manjaro.exe

Expected Behavior

It should start

Actual Behavior

I get an error:

PS D:\PortablePrograms\Manjaro> .\Manjaro.exe
Processing fstab with mount -a failed.

<3>WSL (9) ERROR: CreateProcessEntryCommon:570: execvpe /bin/bash failed 8
<3>WSL (9) ERROR: CreateProcessEntryCommon:579: Create process not expected to return

fails to update. Also cannot install pamac in the readme. PGP signature is incorrect.

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.22621.1702]

Kernel Version

Linux version 5.15.90.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Fri Jan 27 02:56:13 UTC 2023

Repro Steps

sudo pacman -Syu

Expected Behavior

Installs and updates.

Actual Behavior

[brian@DESKTOP-HMN4M4C ~]$ sudo pacman -Syu
error: wslutilities: signature from "WSL Utilities Package Signing Key [email protected]" is unknown trust
:: Synchronizing package databases...
core 143.6 KiB 49.4 KiB/s 00:03 [##############################################] 100% extra 1636.8 KiB 2.13 MiB/s 00:01 [##############################################] 100% community 7.0 MiB 8.24 MiB/s 00:01 [##############################################] 100% multilib 145.5 KiB 808 KiB/s 00:00 [##############################################] 100% wslutilities 1153.0 B 1098 B/s 00:01 [##############################################] 100%error: wslutilities: key "2D4C887EB08424F157151C493DD50AA7E055D853" is unknown
:: Import PGP key 2D4C887EB08424F157151C493DD50AA7E055D853? [Y/n] Y
error: key "2D4C887EB08424F157151C493DD50AA7E055D853" could not be looked up remotely
error: failed to synchronize all databases (invalid or corrupted database (PGP signature))

Hardware 3D acceleration does not seem to work/be enabled

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.22621.1555]

Kernel Version

5.15.90.1-microsoft-standard-WSL2

Repro Steps

Follow normal installation

Expected Behavior

To see decent performance with 3D acceleration

Actual Behavior

GUI works fine, I can run GUI apps, but they're extremely slow, and as far as I can tell, not using my graphics card?

I tried using glxgears as a benchmark, and would get ~120fps on my computer, but on my laptop that runs Manjaro, I get ~40000fps. My computer that I'm testing this on has a 1080 ti vs a shoddy integrated GPU in my laptop, so this doesn't stack up? I would've tried more benchmarks, but most crashed.
When I check task manager running GUI apps I also see my CPU usage spike, and don't see any GPU usage?

Anyway, I checked neofetch and lspci, and both tell me that my GPU is a 0b26:00:00.0 Microsoft Corporation Basic Render Driver, which I suspect is some kind of software fallback?
Strangely enough, the GL Vendor is set to NVIDIA GeForce GTX 1080 Ti.

OpenGL 4.2
D3D12 (NVIDIA GeForce GTX 1080 Ti): Microsoft Corporation
GLSL version: 4.2

wslutilities key

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Windows version: 10.0.22621.1702

Kernel Version

5.15.90.1

Repro Steps

Install ManjaroWSL2 as per instructions up to
sudo pacman -Syu in "How to setup"

Expected Behavior

sudo pacman -Syu completes successfully.

Actual Behavior

Running this command shows the error:

error: wslutilities: key "2D4C887EB08424F157151C493DD50AA7E055D853" is unknown
:: Import PGP key 2D4C887EB08424F157151C493DD50AA7E055D853? [Y/n]

Type Y

error: key "2D4C887EB08424F157151C493DD50AA7E055D853" could not be looked up remotely
error: failed to synchronize all databases (invalid or corrupted database (PGP signature))

Blue Screen Issue After Setting Up KDE Plasma Desktop and Connecting via RDP

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

10.0.22621.3155

Kernel Version

5.15.133.1-1

Repro Steps

1. Install KDE Plasma and necessary packages with:
   sudo pacman -S plasma kio-extras
   sudo systemctl enable sddm.service --force
   pacman -S xorg xorg-server xrdp
   yay -S xorgxrdp
2. Enable and start xrdp service:
3. sudo systemctl enable xrdp.service
   sudo systemctl start xrdp.service
   sudo systemctl reboot
4. Add the specified code to ~/.xinitrc.
5. Obtain IP address with ip addr | grep eth0.
6. Connect to the RDP server using mstsc with ip:13389 and select the xvnc option.

Expected Behavior

I expected to see the KDE Plasma desktop environment after successfully logging in through the RDP session.

Actual Behavior

After entering my username and password, I am presented with a blue screen, and the desktop environment does not load.

ManjaroWSL2 in any terminal running tmux crashes after a time (seconds to minutes)

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

Microsoft Windows [Version 10.0.22631.3296]

Kernel Version

Linux version 5.15.146.1-microsoft-standard-WSL2 (root@65c757a075e2) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Jan 11 04:09:03 UTC 2024

Repro Steps

Install ManjaroWSL2 following all instructions with careful attention to detail.

pamac install zsh
pamac install tmux

Install your regular zsh/tmux dot files

Open a Manjaro WSL2 session in for example Windows Terminal. Work along as usual for some small period of time at which point an error message flashes something like:

"No session available" and then the tab closes/vanishes.

Expected Behavior

I was running ManjaroWSL2 perfectly for a few months with no issue and this started happening all of a sudden out of the blue.

I never had it kill my terminal tab unexpectedly. That's what I would expect :)

Actual Behavior

Open a Manjaro WSL2 session in for example Windows Terminal. Work along as usual for some small period of time at which point an error message flashes something like:

"No session available" and then the tab closes/vanishes.

gpu not used by mesa driver

Requirements

• Yes
• No

WSL Version

• WSL 2
• WSL 1

Version

10.0.22621.819

Kernel Version

5.15.74.2

Repro Steps

WSL Version: 1.0.0.0
kernel Version: 5.15.74.2
WSLg Version: 1.0.47
MSRDC Version: 1.2.3575
Direct3D Version: 1.606.4
DXCore Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows Version: 10.0.22621.819

---

pacman -S mesa mesa-utils
glxgears

check on windows taskmanager to see if the gpu is being used.

Expected Behavior

the gpu is used to render glxgears

Actual Behavior

glxgears is rendered using cpu

---

additional info:

❯ glxinfo | grep -i opengl
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 14.0.6, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.2.3
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.2.3
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.2.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

❯ lspci
94ed:00:00.0 3D controller: Microsoft Corporation Basic Render Driver