http://bugs.winehq.org/show_bug.cgi?id=59617 --- Comment #35 from otigkd@gmail.com --- (In reply to Paul Gofman from comment #33)
(In reply to otigkd from comment #31)
Created attachment 80716 [details] new log with debug patch
Added new log
So it crashes inside host Vulkan library vkGetRandROutputDisplayEXT call (and our pointer to that is not NULL, debug output prints that). I can see how that could change with the patch, it apparently crashes when called for NVidia device with xrandr output 0 and before the patch it was first called with Intel device, that wasn't crashing and was reporting the connection between those and another call for vkGetRandROutputDisplayEXT( NVidia / xrandr output 0 ) was never made.
One weird thing I noticed is that xrandr output linked above reports two connections (probably for the same 1920x1200 monitor), on eDP-1 and DP-1. Is there any special / manual in monitor confifuration? But that can also be not a problem and just specifics of the particular Optimus setup.
all 3 machines, where i have gentoo with this issue have a few things in common (as mentioned before, the issue reproduces on all of them, regardless if the open-source AMDGPU is in use or the closed-source nvidia): - all of them are notebooks, with integrated corei7 GPUs and dedicated AMD or nvidia GPU - all of them are used as "desktop" machines: lid closed, mouse and keyboard connected - dedicated GPU acceleration is not on by default, meaning i have to do "DRI_PRIME=1 [application name]" on the AMD machines and "prime-run [application name]" on the nvidia machines to have the application be run trough the dedicated card, instead of the integrated Since I like doing things manually, nvidia optimus and such are turned off. Out of curiosity, I tried to run a winecfg with the external monitor disconnected, using the notebook's own monitor, but the issue reproduces the same.
That looks like either NVidia drivers bug or host configuration problem. I am not sure we can do anything reasonable if the call to vkGetRandROutputDisplayEXT just crashes (not even gives X error as it was happening once with NV driver and for such a behaviour we temporary had a workaround).
Most likely a configuration problem, but it's really strange as absolutely no other game/application has this issue, be it native linux application or any game on older wine, that i could run -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.