Hello, I do not know much about WINE, nor this page, but I have found a really cool project that makes WINE run native in Wayland (without the need of XWayland): https://github.com/varmd/wine-wayland. I am wondering if someone can take care of it and add it in the page.
- This project does not seem to be packaged in Arch. -- Blackteahamburger (talk) 09:49, 23 June 2020 (UTC)
- I added a category for this to the Usage section. Blackteahamburger is right, there is no package in the Repos or AUR, but the upstream dev/maintainer provides PKGBUILDs directly for Arch. Thus it would be quite easy to include it in AUR.
- I also added a new effort to support Wayland upstream.
- G3ro (talk) 15:09, 10 March 2021 (UTC)
Sound - Move part?
Should this part maybe be moved to Troubleshooting instead?
If winecfg still fails to detect the audio driver (Selected driver: (none)), configure it via the registry. For example, in a case where the microphone was not working in a 32-bit Windows application on a 64-bit stock install of wine-1.9.7, this provided full access to the sound hardware (sound playback and mic): open regedit, look for the key HKEY_CURRENT_USER → Software → Wine → Drivers, and add a string called Audio and give it the value alsa. Also, it may help to recreate the prefix.
Sound - lib32-pulse for PipeWire
As I'm using PipeWire for audio instead of PulseAudio, I didn't even think about installing lib32-pulse, but only after that sound worked (in fact it works without lib32-pipewire). It would take way too much time for me to research and fully understand this, but is the following conclusion correct?
Wine wants PulseAudio (or ALSA) for sound (hence the opt. deps on both, and none on pipewire), so the the wiki should actually state that you need the PulseAudio libs for using PipeWire (or maybe even the ALSA libs for going the pipewire-alsa route?). Totally above my paygrade here.. Rumsbums (talk) 13:05, 26 August 2021 (UTC)
- We need to confirm this once more, but my first search shows that you are correct (Official Wine wiki only mentions Pulse and Alsa, Wine commit search shows no results for "pipewire" etc.). There does not seem to be direct support for Pipewire yet, so you need to install lib32-pulse (or the alsa variant I suppose) instead. The wiki article should reflect that, if it is correct.
- G3ro (talk) 13:54, 26 August 2021 (UTC)
This page is in "emulation" category
- To give the "obvious" answer: so that it can be found. People searching for ways of emulation "should" also find wine.
- I also think that the word "emulation" is open to interpretation. In the end wine provides a functionality that lets you use a software on a different operating system, so that could qualify as emulation imho.
- G3ro (talk) 18:23, 3 October 2021 (UTC)
CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.
Add to troubleshooting: In case of the following error CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly.: Install the package xorg-xhost
Performance issue due to falling back to RandR 1.0 when using NVIDIA
Using Wine 7 and NVIDIA proprietary driver 520.56.06, opening any program, even just
winecfg, renders the whole Xorg extremely laggy if you have monitors with more than one modes. In logs, there are lots of warnings like:
0064:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 0064:fixme:xrandr:xrandr10_get_current_mode Non-primary adapters are unsupported.
This is due to the fallback logic in Wine to support non-native modes. You can either remove all modes except the ones you use for all monitors, or remove the fallback logic using this Proton patch if this case doesn't concern you.
See also Wine forum discussion.