https://bugs.winehq.org/show_bug.cgi?id=51210
Bug ID: 51210 Summary: winediag:nodrv_CreateWindow Unknown error (998) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ZeroBeat@gmx.de Distribution: ArchLinux
Created attachment 70082 --> https://bugs.winehq.org/attachment.cgi?id=70082 WINEDEBUG=+all log
Fresh install of wine: $ pacman -Q | grep wine wine 6.9-1
on Arch Linux: $ uname -r 5.12.8-arch1-1
$ pacman -Q | grep mesa lib32-mesa 21.1.1-1 mesa 21.1.1-1
$ pacman -Q | grep nvidia lib32-nvidia-utils 465.31-1 nvidia 465.31-6 nvidia-settings 465.27-1 nvidia-utils 465.31-1 opencl-nvidia 465.31-1
$ pacman -Q | grep xf86-video xf86-video-intel 1:2.99.917+916+g31486f40-1
running hardware: $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940M] (rev a2) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter
caused winecfg to hang: $ wine winecfg wine: created the configuration directory '/home/zerobeat/.wine' 0048:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0048:err:winediag:nodrv_CreateWindow Unknown error (998). 0048:err:systray:initialize_systray Could not create tray window 0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0048:err:ole:apartment_get_local_server_stream Failed: 0x80004002
winecfg hangs - pressed ctrl+c
0024:err:seh:NtRaiseException Unhandled exception code c000013a flags 0 addr 0xf7fa7549 0050:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0050:err:winediag:nodrv_CreateWindow Unknown error (998). 0050:err:ole:apartment_createwindowifneeded CreateWindow failed with error 0 0050:err:ole:apartment_createwindowifneeded CreateWindow failed with error 0 0050:err:ole:apartment_createwindowifneeded CreateWindow failed with error 14007 0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x800736b7 0050:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x800736b7 0050:err:ole:apartment_get_local_server_stream Failed: 0x800736b7 0050:err:ole:start_rpcss Failed to open RpcSs service
doing a bisect, this commit looks like the faulty one: 145cfce1135a7e59cc4c89cd05b572403f188161 is the first bad commit commit 145cfce1135a7e59cc4c89cd05b572403f188161 Author: Zhiyi Zhang zzhang@codeweavers.com Date: Wed Jun 17 20:02:04 2020 +0800
winex11.drv: Add a Vulkan UUID property for GPUs.
A Vulkan UUID property is used to find the corresponding GPU in SetupAPI.
Signed-off-by: Zhiyi Zhang zzhang@codeweavers.com Signed-off-by: Liam Middlebrook lmiddlebrook@nvidia.com Signed-off-by: Alexandre Julliard julliard@winehq.org
dlls/winex11.drv/display.c | 15 +++++-- dlls/winex11.drv/x11drv.h | 2 + dlls/winex11.drv/xrandr.c | 99 ++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 113 insertions(+), 3 deletions(-)
Latest working release: 5.10 (fresh install) $ winecfg wine: created the configuration directory '/home/zerobeat/.wine' 0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002 0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002 0048:err:ole:get_local_server_stream Failed: 80004002 0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002 0050:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002 0050:err:ole:get_local_server_stream Failed: 80004002 Could not find Wine Gecko. HTML rendering will be disabled. Could not find Wine Gecko. HTML rendering will be disabled. wine: configuration in L"/home/zerobeat/.wine" has been updated.
https://bugs.winehq.org/show_bug.cgi?id=51210
Zhiyi Zhang zzhang@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzhang@codeweavers.com
--- Comment #1 from Zhiyi Zhang zzhang@codeweavers.com --- Looks like it's specific to laptops with both Nvidia and Intel GPU. I don't have such a laptop. Could you help figure up where it hangs? I am guessing somewhere in winex11.drv/xrandr.c get_vulkan_device_uuid(). You can place "FIXME("line: %d\n", __LINE__)" in that function and recompile to figure out the location.
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #2 from Michael ZeroBeat@gmx.de --- Will be not easy to figure out, what exactly went wrong, because at least four parts are involved: wine mesa nvidia linux graphics (xf86-video-intel)
BTW: Disabling either NVIDIA or INTEL, doesn't solve the problem.
It is discussed on Arch Linux, too: https://bugs.archlinux.org/task/68771 and here: https://bbs.archlinux.org/viewtopic.php?id=261004
https://bugs.winehq.org/show_bug.cgi?id=51210
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch
https://bugs.winehq.org/show_bug.cgi?id=51210
Zhiyi Zhang zzhang@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1
https://bugs.winehq.org/show_bug.cgi?id=51210
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=51210
nimbalkar@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nimbalkar@protonmail.com
--- Comment #3 from nimbalkar@protonmail.com --- I'm using a laptop with both NVIDIA and Intel graphics. When running './wine winecfg' after building it from source, I ran into the same issue. I placed two FIXMEs "BEFORE\n" and "AFTER\n" in the beginning and end of get_gpu_properties_from_vulkan() respectively.
Please find the output here: https://pastebin.com/TL8UsMz1
This confirms that wine is hanging in the function get_gpu_properties_from_vulkan() in xrandr.c
I was able to workaround this by exporting the following environment variable:- VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json
Please find my system details below:
On Arch Linux: $ uname -r 5.12.12-arch1-1
$ pacman -Q | grep mesa mesa 21.1.3-1 mesa-demos 8.4.0-4
$ pacman -Q | grep nvidia nvidia 465.31-10 nvidia-settings 465.31-1 nvidia-utils 465.31-1 opencl-nvidia 465.31-1
$ pacman -Q | grep xf86-video xf86-video-intel 1:2.99.917+916+g31486f40-1 xf86-video-vesa 2.5.0-1
$ lspci https://pastebin.com/nrAjXsWj
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #4 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to nimbalkar from comment #3)
I'm using a laptop with both NVIDIA and Intel graphics. When running './wine winecfg' after building it from source, I ran into the same issue. I placed two FIXMEs "BEFORE\n" and "AFTER\n" in the beginning and end of get_gpu_properties_from_vulkan() respectively.
Please find the output here: https://pastebin.com/TL8UsMz1
This confirms that wine is hanging in the function get_gpu_properties_from_vulkan() in xrandr.c
Which line exactly?
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #5 from nimbalkar@protonmail.com --- I could narrow it down to the following line
vr = pvkGetRandROutputDisplayEXT( vk_physical_devices[device_idx], gdi_display, provider_info->outputs[output_idx], &vk_display );
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #6 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to nimbalkar from comment #5)
I could narrow it down to the following line
vr = pvkGetRandROutputDisplayEXT( vk_physical_devices[device_idx], gdi_display, provider_info->outputs[output_idx], &vk_display );
MESA-INTEL: warning: Performance support disabled, consider sysctl >dev.i915.perf_stream_paranoid=0
Please try "sysctl >dev.i915.perf_stream_paranoid=0" as suggested by the warning. There are reports about this as well at https://www.reddit.com/r/wine_gaming/comments/m7ircp/mesaintel_warning_perfo.... Looks like a driver bug.
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #7 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to Zhiyi Zhang from comment #6)
(In reply to nimbalkar from comment #5)
I could narrow it down to the following line
vr = pvkGetRandROutputDisplayEXT( vk_physical_devices[device_idx], gdi_display, provider_info->outputs[output_idx], &vk_display );
MESA-INTEL: warning: Performance support disabled, consider sysctl >dev.i915.perf_stream_paranoid=0
Please try "sysctl >dev.i915.perf_stream_paranoid=0" as suggested by the
sysctl dev.i915.perf_stream_paranoid=0
warning. There are reports about this as well at https://www.reddit.com/r/wine_gaming/comments/m7ircp/ mesaintel_warning_performance_support_disabled/. Looks like a driver bug.
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #8 from nimbalkar@protonmail.com --- By trying "sudo sysctl dev.i915.perf_stream_paranoid=0" I got rid of the MESA-INTEL warning. But it still hanged at the pvkGetRandROutputDisplayEXT function.
Here is the output I received. It includes some of my FIXMEs:
$: ./wine winecfg
wine: created the configuration directory '/home/glitch/.wine' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0048:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0050:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0048:fixme:xrandr:get_gpu_properties_from_vulkan BEFORE 0048:fixme:xrandr:get_gpu_properties_from_vulkan HERE 0048:fixme:xrandr:get_gpu_properties_from_vulkan HERE 0 0048:fixme:xrandr:get_gpu_properties_from_vulkan HERE 1 0048:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0048:err:winediag:nodrv_CreateWindow Unknown error (998). 0048:err:systray:initialize_systray Could not create tray window 0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0048:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0024:err:environ:run_wineboot boot event wait timed out wine: could not load kernel32.dll, status c0000135
https://bugs.winehq.org/show_bug.cgi?id=51210
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |obydux@protonmail.com
--- Comment #9 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- *** Bug 51866 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=51210
Wyatt Ward wyattfward@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wyattfward@gmail.com
--- Comment #10 from Wyatt Ward wyattfward@gmail.com --- I believe have this bug, and am on a system with only Nvidia drivers (it's got an i5-3350p, so there are no integrated graphics to speak of).
I built it using wine-staging 6.21, on Debian Sid. So if that helps to confirm anything, it is impacting me too.
https://bugs.winehq.org/show_bug.cgi?id=51210
Vasily Galkin galkin-vv@ya.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |galkin-vv@ya.ru
--- Comment #11 from Vasily Galkin galkin-vv@ya.ru --- Created attachment 71120 --> https://bugs.winehq.org/attachment.cgi?id=71120 Minimal crash repoducer
TLDR: if wrong vulkan ICD is loaded pvkGetRandROutputDisplayEXT may crash.
I ran into the same problem in a multiseat system with one seat on NVidia gpu and the other seat on AMD gpu (both sessions X11).
Trying to run wine or even winedbg on the X11 DISPLAY on the amd gots this error.
thread log with a part near the crash:
172488.042:0078:007c:trace:vulkan:X11DRV_vkCreateInstance create_info 0x6ace50, allocator (nil), instance 0x6ace40 172488.042:0078:007c:trace:heap:RtlAllocateHeap (0000000000020000,7000006a,00000030): returning 0000000000070BF0 172488.097:0078:007c:trace:heap:RtlFreeHeap (0000000000020000,70000062,0000000000070BF0): returning TRUE 172488.097:0078:007c:trace:vulkan:X11DRV_vkGetInstanceProcAddr 0x7e61ed10, "vkEnumeratePhysicalDevices" 172488.097:0078:007c:trace:vulkan:X11DRV_vkGetInstanceProcAddr 0x7e61ed10, "vkGetPhysicalDeviceProperties2KHR" 172488.097:0078:007c:trace:vulkan:X11DRV_vkGetInstanceProcAddr 0x7e61ed10, "vkGetRandROutputDisplayEXT" 172488.099:0078:007c:trace:heap:RtlAllocateHeap (0000000000020000,7000006a,00000018): returning 0000000000070C40 172488.115:0078:007c:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000000000000 ip=0000000000000000 tid=007c 172488.115:0078:007c:trace:unwind:dispatch_exception info[0]=0000000000000008 172488.115:0078:007c:trace:unwind:dispatch_exception info[1]=0000000000000000 172488.115:0078:007c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised 172488.115:0078:007c:trace:seh:dispatch_exception rax=00007f24aff77340 rbx=00000000006ace48 rcx=00000000006acd60 rdx=00000000006acd2c 172488.115:0078:007c:trace:seh:dispatch_exception rsi=0000000000000055 rdi=000000007e5ebb40 rbp=000000007e8b4420 rsp=00000000006acd18 172488.115:0078:007c:trace:seh:dispatch_exception r8=00000000006ace48 r9=0000000000000004 r10=00007ffdd5f46080 r11=0000000000000246 172488.115:0078:007c:trace:seh:dispatch_exception r12=0000000000000055 r13=000000007e5ebb40 r14=00000000006ace48 r15=00007f24bb1a3870 172488.115:0078:007c:trace:unwind:dwarf_virtual_unwind function 7f24ae851ca0 base 0x7f24ae851c70 cie 0x7f24af0744f8 len 14 id 0 version 3 aug 'zR' code_align 1 data_align -8 retaddr %rip
I investigated it further and found the reason: for DISPLAY containing all AMD-related the NVidia vulkan ICD is loaded, and pvkGetRandROutputDisplayEXT calls into libnvidia-glcore.so.470.86 that crashes for that AMD display.
Attached file is a minimal C source that reproduces the problem.
It runs fine with nvidia DISPLAY=:0 and segfaults with amd DISPLAY=:1
% DISPLAY=:0 ./wine-vk-randr-crash 0x7fadf49c4870 0x7fadf49e3750 0x7fadf49e4210 device_count 3 pvkGetRandROutputDisplayEXT 0x55ce42baf750 pvkGetRandROutputDisplayEXT 0x55ce42baad20 pvkGetRandROutputDisplayEXT 0x55ce42baf5b0 % DISPLAY=:1 ./wine-vk-randr-crash 0x7fb9ee250870 0x7fb9ee26f750 0x7fb9ee270210 device_count 3 pvkGetRandROutputDisplayEXT 0x564206a0bd00 zsh: segmentation fault
Dircet specifying VK_ICD_FILENAMES helps
% VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json DISPLAY=:1 > ./wine-vk-randr-crash 0x7fc07c50c870 0x7fc07c52b750 0x7fc07c52c210 device_count 1 pvkGetRandROutputDisplayEXT 0x556edbb1c320 %
So this minimal representer has behaviour identical to wine.
running DISPLAY=:1 ./wine-vk-randr-crash under gdb gives the stacktrace into libnvidia-glcore.so.470.86 ending with NULL instruction pointer:
pvkGetRandROutputDisplayEXT 0x557c6aba4cf0
Thread 1 "wine-vk-randr-c" received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007f86799ddca0 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.470.86 #2 0x00007f86799d8afd in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.470.86 #3 0x0000557c68a124d8 in main () at wine-vk-randr-crash.c:83
If anyone know how vkCreateInstance can be called in a way that returns ICD that is compatible with specific X11 disaply, this maybe can be used to fix the issue.
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #12 from Vasily Galkin galkin-vv@ya.ru --- Also this may be related to the fix that nvidia done in https://bugs.winehq.org/show_bug.cgi?id=49407
The origin of the SIGSEGV is inside NVidia libs. Calling to nullptr-function (according to a stacktrace I presented above) instead of returning an error MAY be a sign of a bug inside nvidia driver.
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #13 from Vasily Galkin galkin-vv@ya.ru --- Created attachment 71124 --> https://bugs.winehq.org/attachment.cgi?id=71124 code sample for adding vkGetPhysicalDeviceXlibPresentationSupportKHR
If anyone know how vkCreateInstance can be called in a way that returns ICD that is compatible with specific X11 disaply, this maybe can be used to fix the issue.
I was completely wrong here, since I wasn't undestanding how vulkan loader works.
I've started step-by-step debugging with vulkan-loader 1.2.189 and found that pvkGetRandROutputDisplayEXT( vk_physical_devices[device_idx], ... call (in my example or in wine's xrandr.c) initially calls loaders GetRandROutputDisplayEXT that tail-calls terminator_GetRandROutputDisplayEXT that tail-calls into libnvidia-glcore.so.470.86
both GetRandROutputDisplayEXT and terminator_GetRandROutputDisplayEXTdefined in https://github.com/KhronosGroup/Vulkan-Loader/blob/sdk-1.2.189/loader/extens... but are not visible in the stacktrace due to tail-calling.
So my situation is similar to https://bugs.winehq.org/show_bug.cgi?id=49407 But the problem is not "protocol error is returned on bad RROutput" but "crash on non-nvidia Display* ".
Note that 470.86 is the latest driver on 470 "Production" branch, but 470 is NOT the latest branch now. The latest is "NewFeature" 495.44.
I tried to filter out vulkan devices incompatible with a display by adding VK_KHR_xlib_surface to the list of extensions and using vkGetPhysicalDeviceXlibPresentationSupportKHR, that seems to be designed for it according to "Issue 1" in https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_KHR...
This works for filtering out "AMD vulkan device and Nvidia display" combination, but fails to filter out "Nvidia vulkan device and AMD display". It seems that vkGetPhysicalDeviceXlibPresentationSupportKHR incorrectly returns true for Nvidia device.
attaching a partial code sample that I used for vkGetPhysicalDeviceXlibPresentationSupportKHR experiments.
Also see the above khronos link for alternative that can be used after creating window.
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #14 from mirh mirh@protonmail.ch --- Could this help/be related? https://github.com/ValveSoftware/wine/commit/e6e9a2bc52f94732069999861b084f1...
https://bugs.winehq.org/show_bug.cgi?id=51210
--- Comment #15 from Vasily Galkin galkin-vv@ya.ru --- I think the liked above "winex11.drv: Add a GPU for each Vulkan device that was not tied to an XRandR provider" touches realted code, but I'm not sure it is directly connected to this problem.
This bug occurs shile building x11drv_gpu array entries that has id field assigned to xrandr provider id AND vulkan_uuid field assigned to vulkan ID.
And as far as I understand the the linked above - it fills additional gpus that are visible to vulkan, but not visiable to xrandr (or failed to match), so they have ONLY vulkan_uuid, but not id. This greately helps if a single gpu is listed via vulkan, but not via xrandr
https://bugs.winehq.org/show_bug.cgi?id=51210
nj8ne5e16@mozmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nj8ne5e16@mozmail.com
https://bugs.winehq.org/show_bug.cgi?id=51210
Frederick Zhang frederick888@tsundere.moe changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |frederick888@tsundere.moe
https://bugs.winehq.org/show_bug.cgi?id=51210
Michael ZeroBeat@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEEDINFO |CLOSED
--- Comment #16 from Michael ZeroBeat@gmx.de --- I got a solution. Use IGPU as primary GPU and deactivate second GPU.
-
WineHQ Bugzilla