http://bugs.winehq.org/show_bug.cgi?id=59617 --- Comment #33 from Paul Gofman <pgofman@codeweavers.com> --- (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. 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). -- 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.