May 2026 - Wine-Bugs - list.winehq.org

[Bug 59078] 8 low-res old GOG-Games don't work being extremely scaled (i.e. blurred) and show less than 1/4 part of normal screen output - thus options menu not reachable

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59078 --- Comment #11 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to JMB9 from comment #1) > I am using 4k screen with DPI factor 256 and I thought changing > one or both - scaling and resolution - would do the job. > But the small part of the game output visible does not even > change in any way when using FHD (1920x1080) res. These tests were performed on regular laptop display with default settings so if bugs persist then it may be related to 4k screen with DPI settings specifically. Please retest with later version such as wine-11.9 and post more screenshots if bugs persist. -- 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.

May 18, 2026

[Bug 59078] 8 low-res old GOG-Games don't work being extremely scaled (i.e. blurred) and show less than 1/4 part of normal screen output - thus options menu not reachable

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59078 --- Comment #10 from Stian Low <wineryyyyy(a)gmail.com> --- Created attachment 80965 --> http://bugs.winehq.org/attachment.cgi?id=80965 Worms Revolution screenshot showing OpenGL renderer for MANGOHUD MANGOHUD showing OpenGL for Worms Revolution missing from first screenshots -- 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.

May 18, 2026

[Bug 59078] 8 low-res old GOG-Games don't work being extremely scaled (i.e. blurred) and show less than 1/4 part of normal screen output - thus options menu not reachable

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59078 --- Comment #9 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Stian Low from comment #8) > *** Nine Parchments > WINED3D/gl only works (DAMAVAND/vk crashes with backtrace) Otherwise game works well. -- 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.

May 18, 2026

[Bug 59078] 8 low-res old GOG-Games don't work being extremely scaled (i.e. blurred) and show less than 1/4 part of normal screen output - thus options menu not reachable

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59078 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #8 from Stian Low <wineryyyyy(a)gmail.com> --- Created attachment 80964 --> http://bugs.winehq.org/attachment.cgi?id=80964 Screenshots of games tested Attached are screenshots of the following games tested (all GOG versions): Nine Parchments Worms Revolution Samorost 2 Tower 57 PixelJunk Monsters HD Vertical Drop Heroes HD Tested for both wayland and x11 for wine-11.8-0c0d2643208 for Debian 13 AMD. Unable to reproduce any major bugs with consistency except for PixelJunk Monsters HD. Various rendering backends are used across these games so behavior may vary. Unable to reproduced blurred graphics for any of the games. 1/4 screen rendering seems fairly common for older games for wine and adjusting in-game display settings often works around undesirable any default settings. ** Test Results: *** Nine Parchments WINED3D/gl only works (DAMAVAND/vk crashes with backtrace) *** Worms Revolution OpenGL reported by MANGOHUD so appears not be use D3D backend Directx9c is part of installer process but MANGOHUD reports OPENGL for both renderer=gl and vk. fixme:cryptasn logs appear during d3d9 install so unclear if anything malfunctioned for d3d9: fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder logs appeared during directx9c during install so unclear if OpenGL Regardless OpenGL renderer seems to works well even if as a fallback for d3d9 but OpenGL seems intended as primary renderer based on root dir containing GL files (cgGL.dll, glut32.dll) *** Samorost 2 WINED3D/gl and DAMAVAND/vk both work Game starts fullscreen but Esc key causes it to enter windowed mode. Otherwise seems to work well. *** Tower 57 OpenGL reported by MANGOHUD with install and gameplay results similar to Worms Revolution Separate cmd window appears responsible for game process that accepts Ctrl-C to kill game. *** PixelJunk Monsters WINED3D/gl only works (DAMAVAND/vk crashes with backtrace) Most problematic game with fairly severe rendering bugs. Alt+tab game window from foreground to background and back causes various graphical glitches such as menus disappearing and cursor appearing as black square. In-game display settings changed from default fullscreen to windowed mode causes it to never properly be shown in foreground any longer and always remains running in background. *** Vertical Drop Heroes WINED3D/gl and DAMAVAND/vk both work Switching in-game display setting from default fullscreen to windowed has slight malfunction fixed by alt+tab or exiting then re-entering the game which then starts in windowed mode. Otherwise game works well. -- 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.

May 18, 2026

[Bug 59648] ff7.exe gog version crashes after battle fanfare and before rewards menu

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59648 --- Comment #2 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Since the mingw-w64-gcc package was upgraded on Arch to 16.1.0, I can no longer reproduce the crash in FF VII. With the previous version of mingw-w64-gcc (15.2.0) I had to use CROSSCFLAGS="-O0" instead of -O2 to prevent the game from crashing. -- 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.

May 18, 2026

[Bug 59761] The ubuntu packages in wine-11.9 are built incorrectly

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59761 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #2 from Stian Low <wineryyyyy(a)gmail.com> --- Related? https://bugs.winehq.org/show_bug.cgi?id=59760 -- 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.

May 18, 2026

[Bug 59760] Missing i386-part on latest 11.9 release (noble)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59760 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #4 from Stian Low <wineryyyyy(a)gmail.com> --- Related? https://bugs.winehq.org/show_bug.cgi?id=59761 -- 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.

May 18, 2026

[Bug 58043] Multiple applications won't run on Wine 10.3 because they think that there is a debugger running when there isn't (DVDFab, DCS World updater)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58043 --- Comment #16 from Alex Henrie <alexhenrie24(a)gmail.com> --- (In reply to Chaos from comment #14) > (In reply to Alex Henrie from comment #13) > > No longer an issue in Wine 11.5. DVDFab just works now, even without > > changing the Windows version in winecfg :-D > > unfortunately, DCS's Updater is the opposite case - it is now broken on both > stable and staging as of 11.5, where previously it was only broken on stable > 10.3+. Please open a new bug report about DCS, and be sure to include a detailed description of how to reproduce the problem and what the exact error is. -- 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.

May 18, 2026

[Bug 59760] Missing i386-part on latest 11.9 release (noble)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59760 jenngra505(a)roadrunner.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jenngra505(a)roadrunner.com --- Comment #3 from jenngra505(a)roadrunner.com --- I'm using a non-staging development build, and it breaks on my end too. I had to manually roll back to 11.8 and make a symlink to Wine in the bin folder to get it working again. -- 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.

May 18, 2026

[Bug 52301] Firefox installer shows black rectangles

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=52301 --- Comment #9 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- 9.0.0~trixie-1 black 10.0.0~trixie-1 black 10.1~trixie-1 black wine-10.1-228-g5c7fcc13885 black wine-10.1-229-gb7ca09bd649 working (but upside-down) wine-10.2 working (but upside-down) 11.0.0~trixie-1 working (but upside-down) 11.9~trixie-1 working (but upside-down) The black rectangles got fixed with this commit: b7ca09bd6498155dd3cbcf3f6f81afd5103428f9 is the first working commit commit b7ca09bd6498155dd3cbcf3f6f81afd5103428f9 Author: Dmitry Timoshkov <dmitry(a)baikal.ru> Date: Thu Apr 21 14:40:58 2016 +0800 oleaut32: Make OleLoadPicture load DIBs using WIC decoder. Application in the bug 39474 depends on this (GetObject/bmBits should not be NULL, otherwise it crashes). Also, since CreateDIBSection doesn't support RLE compressed bitmaps it's necessary to decompress it in memory in advance. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=39474 Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> But unfortunately the image is now rendered upside-down, should this get it's own bug report? -- 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.

May 18, 2026

[Bug 46635] git for windows works or crashes depending on how its invoked

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=46635 Bernhard Übelacker <bernhardu(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |bdb2fe0cad3b34bb6c5b70926cc | |848f0b9e9e60f Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- The commit fixing this crash is: bdb2fe0cad3b34bb6c5b70926cc848f0b9e9e60f is the first working commit commit bdb2fe0cad3b34bb6c5b70926cc848f0b9e9e60f Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Sep 22 16:56:58 2020 +0200 server: Return the device name for named pipe files. Marking resolved fixed. -- 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.

May 17, 2026

[Bug 59631] wine-staging-11.6: flickering images in Battle.net Launcher

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59631 --- Comment #29 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Alistair Leslie-Hughes from comment #28) > I'm still not seeing the flicker issue, with/out acceleration enabled. Do any of these logs appear with patch applied? 0208:fixme:dxgi:dxgi_factory_CreateSwapChainForComposition iface 02A39810, device 0094FD98, desc 0022EBE0, output 00000000, swapchain 4B64515C stub! 0208:fixme:dxgi:wined3d_swapchain_desc_from_dxgi Ignoring alpha mode 0x1. 0208:fixme:d3d:wined3d_swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. 0208:fixme:d3d:wined3d_swapchain_init Unimplemented swap effect 0x3. -- 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.

May 17, 2026

[Bug 59763] New: wp_pointer_warp_v1 protocol doesn't work with FL Studio

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59763 Bug ID: 59763 Summary: wp_pointer_warp_v1 protocol doesn't work with FL Studio Product: Wine Version: 11.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)list.winehq.org Reporter: agarplayerarlon(a)gmail.com Distribution: --- Created attachment 80963 --> http://bugs.winehq.org/attachment.cgi?id=80963 video of the issue Recently support for the wp_pointer_warp_v1 protocol has been merged into winewayland and I've decided to test it, and it isn't working in FL Studio with Winewayland. In the video of this issue that I've attached you can see that when I'm using the knobs in the mixer and in the BPM value, the mouse cursor actually moves instead of staying still like it does on Windows and most of the times it escapes the window and goes into the panel, and this behavior can actually break the functionality of some knobs like the BPM one where I literally cannot use it. I'm using the latest version of wine 11.9 and KDE Plasma 6.6.5 Wayland on Fedora KDE 44, NVIDIA driver 595.71.05 -- 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.

May 17, 2026

[Bug 58578] Hygeia Pharmacy: complains that Microsoft ReportViewer is not installed (unimplemented MsiProvideAssemblyW() ?)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58578 --- Comment #6 from Ratchanan Srirattanamet <peathot(a)hotmail.com> --- So I tested again with Wine 11.9. And maybe `MsiProvideAssemblyW()` might not be the actual problem here. Because it turns out that if I install Report Viewer before installing dot48 via Winetricks, then the program works without even calling `MsiProvideAssemblyW()`. On the other hand, if I install dotnet48 before Report Viewer, then my implementation of `MsiProvideAssemblyW()` from MR !9038 [^1] is now unable to find the component, where it works before if I install Report Viewer alone/against Mono .NET. So this leads me to believe that the real problem is with MSI's interaction with the real .NET, somehow breaking installing/publishing Report Viewer's .NET assembly. Will look into this further... [^1]: https://gitlab.winehq.org/wine/wine/-/merge_requests/9038 -- 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.

May 17, 2026

[Bug 59631] wine-staging-11.6: flickering images in Battle.net Launcher

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59631 --- Comment #28 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- (In reply to Stian Low from comment #23) > > Maybe @leslie_alistair can provide insights regarding > dcomp-DCompositionCreateDevice2 staging patches since they added them. > The whole purpose of this patchset was to allow it to be tested and see what issues appear. I'm still not seeing the flicker issue, with/out acceleration enabled. -- 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.

May 17, 2026

[Bug 25974] AutoCAD 2009 LT: acadlt.msi doesn't start installer

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=25974 --- Comment #17 from Janne <janne.kekkonen(a)gmail.com> --- Created attachment 80962 --> http://bugs.winehq.org/attachment.cgi?id=80962 acadlt2009_installer_error_on_32bit_prefix Hello, i created new 32bit prefix and tried to run 32bit installer in there. 32bit installer starts and runs beyond user information guestions. Somepoint the installer stops and error message is shown, see attached screenshot. In 32bit prefix i tried to install with msiexec using following command. msiexec /i x86/acadlt.msi /l*v "C:\package.log" With above command same error message shown as previously. "Installation ended prematurely because of an error" Package.log had following information at the end. Action start 10:14:37: AdRestartDialog. AdRestartDialog DEBUG: Error 2726: Action not found: AdRestartDialog Internal Error 2726. AdRestartDialog Action ended 10:14:37: AdRestartDialog. Return value 0. Action ended 10:14:37: Fatal_Error. Return value 2 I started msixec with WINEDEBUG=+msi. Log contains similar warnings about the AdRestartDialog. 0148:trace:msi:ACTION_PerformAction Performing action (L"AdRestartDialog") ... 0148:warn:msi:get_dialog_record query failed for dialog L"AdRestartDialog" ... 0148:warn:msi:ACTION_PerformAction unhandled msi action L"AdRestartDialog" -- 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.

May 17, 2026

[Bug 59631] wine-staging-11.6: flickering images in Battle.net Launcher

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59631 --- Comment #27 from Stian Low <wineryyyyy(a)gmail.com> --- In summary, in case it was not clear from previous comments: Prior to recent DCompositionCreateDevice patches added to wine-staging, it seems Battle.net would fallback to alternative rendering method that uses swap effect 0x1 and only 1 back buffer. Therefore DCompositionCreateDevice support seems to have activated a different rendering method that is used instead of alternative fallback when available and uses swap effect 0x3 with more than one backbuffer which is not well supported. Therefore alternative rendering method without DCompositionCreateDevice seems to be the basis of how wine users expect Battle.net to behave and may be useful as a reference for dev fixes to DCompositionCreateDevice so that users eventually are barely able to tell the difference between the two rendering methods. Merge request patch intended to fix discrepancies for swap effect 0x3 and more than 1 backbuffer does not work when combined with wine-staging DCompositionCreateDevice patch so more work is needed for compatibility. -- 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.

May 17, 2026

[Bug 59762] New: application crashes when launching lotro store window ingame

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59762 Bug ID: 59762 Summary: application crashes when launching lotro store window ingame Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: winedbg Assignee: wine-bugs(a)list.winehq.org Reporter: djpat30(a)gmail.com Distribution: --- Created attachment 80961 --> http://bugs.winehq.org/attachment.cgi?id=80961 backtrace Launch the lord of the ring online game, login. At the main screen, launch the lotro store (upper right corner) notice the crash and error -- 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.

May 17, 2026

[Bug 59631] wine-staging-11.6: flickering images in Battle.net Launcher

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59631 --- Comment #26 from Stian Low <wineryyyyy(a)gmail.com> --- Confirmed that returning return E_NOTIMPL; for DCompositionCreateDevice2() fixes flickering for wine-staging-11.9. Done for all methods as ./dlls/dcomp/device.c DCompositionCreateDevice() DCompositionCreateDevice2() DCompositionCreateDevice3() Example: HRESULT WINAPI DCompositionCreateDevice2(IUnknown *rendering_device, REFIID iid, void **device) { FIXME("%p, %s, %p\n", rendering_device, debugstr_guid(iid), device); return E_NOTIMPL; if (!IsEqualIID(iid, &IID_IDCompositionDevice) && !IsEqualIID(iid, &IID_IDCompositionDesktopDevice)) return E_NOINTERFACE; return create_device(2, iid, device); } DCompositionCreateDevice patch will be included as part of ongoing tests for MR-10567 which may lead to some fixes to whatever causes flickering when DCompositionCreateDevice2() is supported. -- 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.

May 17, 2026

[Bug 59760] Missing i386-part on latest 11.9 release (noble)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59760 --- Comment #2 from mata <sutupud(a)yahoo.com> --- I have to correct myself, that doesn't apply to noble packages. I can reproduce it in a pristine noble container, so it really seems to be a dependency problem of the package. -- 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.

May 17, 2026

[Bug 59631] wine-staging-11.6: flickering images in Battle.net Launcher

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59631 --- Comment #25 from Stian Low <wineryyyyy(a)gmail.com> --- This log for wine 11.9 (without staging) and GE-Proton10-32 seems likely the cause of swapchain/backbuffers differences with staging which I overlooked previously: 0244:fixme:dcomp:DCompositionCreateDevice2 01794F88, {5f4633fe-1e08-4cb8-8c75-ce24333f5602}, 007FED24. Probably fixed by reverting DCompositionCreateDevice() for staging to match wine-11.8 which always returns E_NOTIMPL: ./wine-staging/patches/dcomp-DCompositionCreateDevice2/0005-dcomp-Add-IDCompositionDevice2-stub.patch Code for wine 11.9 without staging: HRESULT WINAPI DCompositionCreateDevice(IDXGIDevice *dxgi_device, REFIID iid, void **device) { FIXME("%p, %s, %p.\n", dxgi_device, debugstr_guid(iid), device); return E_NOTIMPL; } I will test this single change to wine-staging which probably effectively bypasses most/all of dcomp-DCompositionCreateDevice2 patches which seem to need additional work which is now on my radar in relation to swap effect 0x3 and backbuffer count > 1 merge request. -- 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.

May 17, 2026

[Bug 59761] The ubuntu packages in wine-11.9 are built incorrectly

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59761 --- Comment #1 from Rosanne DiMesio <dimesio(a)earthlink.net> --- What version of Ubuntu is this on? If it's 22.04 or 24.04, the i586 packages have not been built yet because their build environment is broken on the OBS. The i586 packages will be built when the OBS fixes that problem. -- 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.

May 17, 2026

[Bug 59760] Missing i386-part on latest 11.9 release (noble)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59760 mata <sutupud(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud(a)yahoo.com --- Comment #1 from mata <sutupud(a)yahoo.com> --- With the new WOW64 packages should no longer be a separate i386 package, it's not longer required. You might still have installed an old version, which you should purge manually first, then reinstall. See: https://gitlab.winehq.org/wine/wine/-/wikis/Debian-Ubuntu#ubuntu-2510-and-l… "you have held back broken packages" could be related, check what those are: apt-mark showhold Could it be that you held staging at an older version? Try to fix that. If that doesn't help, what versions are currently installed? -- 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.

May 17, 2026

[Bug 59631] wine-staging-11.6: flickering images in Battle.net Launcher

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59631 --- Comment #24 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Stian Low from comment #23) > Maybe @leslie_alistair can provide insights regarding > dcomp-DCompositionCreateDevice2 staging patches since they added them. Or @zzhang rather as original author. Commit seems dated over 20 years ago. From 7fce6c4e5ccc6db058892b0929dd38417bd37e27 Mon Sep 17 00:00:00 2001 From: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Fri, 6 Mar 2026 18:13:32 +0800 Subject: [PATCH 01/65] HACK: dxgi: Add a dxgi_factory_CreateSwapChainForComposition() stub. -- 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.

May 17, 2026

[Bug 59631] wine-staging-11.6: flickering images in Battle.net Launcher

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59631 --- Comment #23 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Maciej Stanczew from comment #22) > The issue was introduced in Staging 11.6 with the > dcomp-DCompositionCreateDevice2 patchset (please see comment 13). Building > Staging 11.9 with '-W dcomp-DCompositionCreateDevice2' makes the issue go > away. Applying your patch on top of this configuration doesn't seem to > change anything (Battle.net still works without flickering). So the issue > seems to be isolated to dcomp-DCompositionCreateDevice2. Only other bug with keyword "dxgi_factory_CreateSwapChainForComposition" besides this one: https://bugs.winehq.org/show_bug.cgi?id=57512#c4 "This won't be an easy fix." Patch that adds dxgi_factory_CreateSwapChainForComposition: https://gitlab.winehq.org/wine/wine-staging/-/blob/master/patches/dcomp-DCo… b70caa17726c3532b210a5ddf53af8024bc35b34 Author: Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> AuthorDate: Sun Mar 22 22:37:38 2026 +1100 Commit: Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> CommitDate: Mon Mar 23 07:47:32 2026 +1100 Parent: 5bfda368 Release v11.5 Contained: master Follows: v10.18 (93) Added dcomp-DCompositionCreateDevice2 patchset 1 file changed, 33 insertions(+) ...-a-dxgi_factory_CreateSwapChainForComposi.patch | 33 ++++++++++++++++++++++ Wine 11.9 without staging never logs dxgi_factory_CreateSwapChainForComposition and unclear what causes it to be called GE-Proton10-32 does not flicker but unclear if dxgi_factory_CreateSwapChainForComposition is handled by dxvk instead of wine although no logs indicate it is used. Trying to understand what triggers calls to dxgi_factory_CreateSwapChainForComposition which seems to cause the unsupported swapchain/backbuffer scenarios. Maybe @leslie_alistair can provide insights regarding dcomp-DCompositionCreateDevice2 staging patches since they added them. In the meantime I'll continue testing. -- 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.

May 17, 2026