October 2025 - Wine-bugs - list.winehq.org

[Bug 50815] New: Change UNCONFIRMED/NEW statuses to OPENED
by WineHQ Bugzilla 04 Feb '26

04 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=50815 Bug ID: 50815 Summary: Change UNCONFIRMED/NEW statuses to OPENED Product: WineHQ Bugzilla Version: 3.2.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- This has been a long standing cause of user confusion, so it might be a good idea to change it. It will inadvertently cause less spam on bugs, because users will no longer post comments to ask why a bug is still listed UNCONFIRMED instead of NEW, even though we don't currently make a distinction. -- 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.

2 8

[Bug 46562] New: Notepad++ 7.6.3 crashes when searching twice and first time found results
by wine-bugs＠winehq.org 04 Feb '26

04 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=46562 Bug ID: 46562 Summary: Notepad++ 7.6.3 crashes when searching twice and first time found results Product: Wine Version: 4.0 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bugs.winehq.org(a)fennec.ath.cx Used 32bit installer and 64bit installer with version 7.6.3, both can crash the same way. https://notepad-plus-plus.org/repository/7.x/7.6.3/npp.7.6.3.Installer.exe * Start Notepad++ * File -> Open * Will propose "C:\Program Files (x86)\Notepad++" folder by default * Chose change.log (or any other file) * Click Open, window will close and file is displayed * Search -> Find... * Input anything that find a result, for example "Notepad" and click button "Find All in All Opened Documents" * With change.log file, 3 results will be displayed in the "Find result" footer box (don't if it's the right name) * Search box will close automatically if there are matches * Search -> Find... (again) Application crashes It seems that if you first search does not find any result and you close the search box manually, then next searches won't crash even if you have matches. It looks like if the the first time you search and search ox close automatically then it will crash. -- 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.

3 4

[Bug 57635] New: Battle.net Launcher invisible/black with the Wayland driver
by WineHQ Bugzilla 04 Feb '26

04 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=57635 Bug ID: 57635 Summary: Battle.net Launcher invisible/black with the Wayland driver Product: Wine Version: 10.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: wine(a)xarov.net Distribution: ArchLinux Created attachment 77764 --> https://bugs.winehq.org/attachment.cgi?id=77764 Black window with Wayland driver Works fine with the X11 driver. Is completely black with the Wayland driver. -- 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.

2 24

[Bug 57815] New: Splinter Cell (2002): crashes when changing game resolution when used with DXVK
by WineHQ Bugzilla 04 Feb '26

04 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=57815 Bug ID: 57815 Summary: Splinter Cell (2002): crashes when changing game resolution when used with DXVK Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78025 --> https://bugs.winehq.org/attachment.cgi?id=78025 output log When I change the game resolution via the settings menu, the game crashes. You can also crash when you start the game (right after the introductory video). Just change the game resolution via the SplinterCellUser.ini configuration file: Resolution=1920x1080 This behavior only happens when used with DXVK. It doesn't happen with WineD3D OpenGL (it's impossible to test with WineD3D Vulkan, as it completely breaks the look of the game). And of course, it doesn't happen with winex11.drv either. - The game was installed via CD-ROM and is up to date with the latest update (v1.3). - I use labwc/wlroots as WM. - Although I'm on Arch Linux, I compile wine manually with these options: ./configure --prefix=/usr --enable-archs=i386,x86_64 --enable-win64. So I'm using the new WoW64 mode, but this behavior also happens in normal wine. -- 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.

2 11

[Bug 45373] New: map does not display in Battle Realms
by wine-bugs＠winehq.org 04 Feb '26

04 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=45373 Bug ID: 45373 Summary: map does not display in Battle Realms Product: Wine Version: 3.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fernando(a)cmartins.nl Distribution: --- The game map, at the bottom-right corner of the screen, does not display in the game Battle Realms. I see some messages in the terminal, not sure if related: 0009:fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled 0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32f294,0x00000000), stub! 0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32bad4,0x00000000), stub! 0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32bad4,0x00000000), stub! 0009:fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. 0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32f5e4,0x00000000), stub! 0009:fixme:ddraw:ddraw7_FlipToGDISurface iface 0x15ce80 stub! 0009:fixme:ddraw:ddraw_surface7_Flip Ignoring flags 0x1. -- 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.

3 17

[Bug 57806] New: visual and response lags in Guitar Pro v8.1.3 (build 121)
by WineHQ Bugzilla 04 Feb '26

04 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=57806 Bug ID: 57806 Summary: visual and response lags in Guitar Pro v8.1.3 (build 121) Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: acidbong(a)tilde.club Distribution: --- Created attachment 78013 --> https://bugs.winehq.org/attachment.cgi?id=78013 Guitar Pro in Wine-9.20 I've been using Wine-staging for running Guitar Pro on Linux (Gentoo, then NixOS), and it's been smooth until 9.20 -> 9.22 update (https://github.com/NixOS/nixpkgs/pull/359908, nixpkgs maintainers skipped v9.21). Then visual lags (constant, as if the program runs at 5 FPS) started to happen. Welp, they aren't solely visual, responsiveness also suffers. Audio, however, doesn't lag and is still smooth. The lag is also present on Wine10. Regression also confirmed on Wine-development v9.22 and with a demo version of the program and on different PCs (first on an Intel-based laptop (Core i3-7100), then on an AMD-based one (AMD Ryzen 5 5500U)), both with integrated GPUs. Camera recording (not screen capture, because `simplescreenrecorder` (haven't tried other tools) for some reason reduced these lags): https://0x0.st/8KNw.mp4 Logs are attached below. -- 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.

2 13

[Bug 50834] New: That wine uses the kde application style
by WineHQ Bugzilla 03 Feb '26

03 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=50834 Bug ID: 50834 Summary: That wine uses the kde application style Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: toadfield(a)tutanota.com Distribution: --- I hate it how wine programs look like,I want that they look exactly like my kde theme. -- 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.

2 11

[Bug 58433] New: entering sub-menus makes entire menu vanish behind main window in FL Studio (virtual desktop mode)
by WineHQ Bugzilla 03 Feb '26

03 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=58433 Bug ID: 58433 Summary: entering sub-menus makes entire menu vanish behind main window in FL Studio (virtual desktop mode) Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: cyrus.valkonen(a)gmail.com Distribution: --- When any menu is opened, such as "File ...", and then a nested sub-menu with more menu options such as "New from template ..." is hovered (not clicked) with the mouse to open it, the entire menu with sub-menu is suddenly rendered behind the main window (z-index issue?). Consequently the user can no longer open files and can no longer access a lot of important menus in a lot of the DAWs functions, such as music sheet editor, pattern editor, etc. In Wine 8.1 this bug does not occur, and must have been introduced somewhen after (my guess is version 9). Please note that this issue does NOT relate to X11, because it happens with "Emulate a virtual desktop" checked. I tried many things to work around it, including monkey-patching Wine 10.11 source, but everything is unsuccessful. Please note due to issues with VSTs, FL Studio needs very specific combos of NOT using DXVK, and not overriding d3dcompiler_47 or dxgi with winetricks. But even if used it makes no difference. There are NO OPTIONS in FL Studio that prevent this bug (such as unchecking ultrasmooth mode or disabling window animations). Only regressing to 8.1 fixes the bug. In the logs you will see two "TQuickPopupMenuWindow" being opened. The first is the menu, the second is the sub-menu. Many versions of FL Studio and Wine are affected by this. At least since FL 20 and Wine 9. Sadly because of changes in Juce (used by many VSTs), a lot of new and critical VST plugins now do require a very recent Wine version. Thus falling back to Wine 8.1 is no longer viable. -- 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.

2 11

[Bug 19469] New: ResEdit crashes checking for updates
by wine-bugs＠winehq.org 03 Feb '26

03 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=19469 Summary: ResEdit crashes checking for updates Product: Wine Version: 1.1.26 Platform: PC URL: http://www.resedit.net/ResEdit-UNICODE.7z OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: urlmon AssignedTo: wine-bugs(a)winehq.org ReportedBy: bunglehead(a)gmail.com Created an attachment (id=22630) --> (http://bugs.winehq.org/attachment.cgi?id=22630) Crash log ResEdit 1.4.7 (unicode build) crashes checking for updates. Attached log produced with 'Help -> Check for update' menu command. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

3 20

[Bug 58783] New: Black Desert Online black launcher with wayland driver
by WineHQ Bugzilla 03 Feb '26

03 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=58783 Bug ID: 58783 Summary: Black Desert Online black launcher with wayland driver Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timon2201(a)gmail.com Distribution: --- Created attachment 79428 --> http://bugs.winehq.org/attachment.cgi?id=79428 log from wine 10.16 When starting black desert over steam or the standalone client, the launcher is black but still interactable. -- 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.

2 14