-
Notifications
You must be signed in to change notification settings - Fork 3
wslg support? #6
Comments
Hi, can you say a few words what is the issue? Have you tried running GUI apps in VoidMuslWSL with wslg? I haven't gotten a chance to explore wslg, it is only available in the insider build. I will try once it is shipped with GA bits. However, reading this: https://github.com/microsoft/wslg#wslg-system-distro, I don't know if there is anything we need to change to make it work, but I'd defer to your findings. |
With the bit of testing done by me, neither GTK nor QT appear to be working...
|
Of course, attempting to create a user and using sudo to elevate privileges also appears not to work - an issue I ran into due to dbus (or systemd?) not starting or something like that. Obviously there's no systemd here so that option is invalidated. Alas, everything else works perfectly. |
See am11/VoidWSL#7. Does |
Nope, for neither of the graphics libraries... |
I haven't tried WSLg myself. If it is broken on AlpineWSL - https://git.io/alpwsl - as well, then it could be that some component is musl-libc incompatible? We don't do anything different in VoidWSL build script which is missed out in musl edition (or vice-versa). @StellarOrbit, on a fresh VoidWSL installation, do you remember the minimal steps required to get basic GUI apps working? Would be nice to have this information in README. PRs are welcome. 🙂 |
Theoretically, Void should be able to use its powers to fix the incompatibilities, so this should indeed be a conflict between WSL and musl... Wonder how one would fix that. |
Apologies for the late reply. I know that Gedit doesn't work by default because it is missing something when just installing gedit and it fails to launch but other gui programs launch. I would have to go back and reinstall voidwsl to see what is the errors and how I overcame them. |
No description provided.
The text was updated successfully, but these errors were encountered: