Created attachment 131437 [details] bug I have wine game that corrupts monitor after entering fullscreen. Windowed uses GDI but fullscreen is DirectX. Overriding GL versions help as workaround. MESA_GLSL_VERSION_OVERRIDE=110 (MUST be 110) MESA_GL_VERSION_OVERRIDE=3.0 (must be <= 3.0) This happens with softpipe and llvmpipe too and without override they show black screen and output: fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "Gallium 0.4 on softpipe"). Game enters fullscreen with something like IDirectDraw2::SetCooperativeLevel -> IDirectDraw2::SetVideoMode. Original bug: bugs.winehq.org/show_bug.cgi?id=41283. Graphics: Card: Advanced Micro Devices [AMD/ATI] Tonga PRO [Radeon R9 285/380] Display Server: X.Org 1.19.3 driver: amdgpu Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz GLX Renderer: Gallium 0.4 on AMD TONGA (DRM 3.15.0 / 4.12.0-rc1-g2ea659a9ef48, LLVM 5.0.0) GLX Version: 3.0 Mesa 17.2.0-devel (git-1586768e74)
Created attachment 131438 [details] without override
Created attachment 131439 [details] log with override
(FYI: Switched back to 4.11 and mesa 17.1.0 week ago, since newer kernel and mesa didn't help) I installed latest batch of updates today: gcc 7.1, glibc 2.25, linux 4.11, linux-firmware among others but no mesa or wine updates. Two programs that have this problem started working including one in first post! I don't know which package did it, but now there's only one wine program that still needs oMESA_GLSL_VERSION_OVERRIDE=110.
This looks like an issue with compat profile which until recently was limited to OpenGL 3.0 (radeonsi now supports 3.1). You seem to be working around it by forcing a lower GLSL version. Recent Wine versions now use Core profile when they detect Mesa, either way I don't think this is a Mesa bug. Future Mesa version will likely support higher compat versions, but Apps (and Wine) need to properly check supported features.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.