November 2025 - Wine-Bugs - list.winehq.org

[Bug 58505] New: Odd windows management behaviour in later dev versions
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=58505 Bug ID: 58505 Summary: Odd windows management behaviour in later dev versions Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kg.hammarlund(a)gmail.com Distribution: --- I run a geneaology database program written for windows under wine. It runs fine on v10.0 (stable) and on dev versions up to 10.4. From v10.5 and upwards, including v1012, I'm encountering an odd issue. When opening a search window, this window opens in the background instead of on top of the main window. I then have to move or resize the main window in order to highilght the search window and fill in the search data. But this only happens the first time I open the search window. Next time it opens in the foreground. If I untick the box "Allow the window manager to control the windows" in winecfg > graphics, the search window opens expected. But this solution has its drawbacks. -- 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 28

[Bug 24851] New: Explorer++ treeview shows plus signs even when a folder contains no subfolders
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=24851 Summary: Explorer++ treeview shows plus signs even when a folder contains no subfolders Product: Wine Version: 1.3.5 Platform: x86-64 URL: http://www.explorerplusplus.com/download OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=31446) --> (http://bugs.winehq.org/attachment.cgi?id=31446) terminal output On Windows, the little plus signs for expanding folders in the treeview don't appear next to folders that contain no subfolders (and thus, nothing to expand). In Wine, such folders still have the plus sign even though it doesn't do anything. Native comctl32 didn't help. -- 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.

2 14

[Bug 16957] New: CreateProcess handles are inherited even when bInheritHandles=FALSE
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=16957 Summary: CreateProcess handles are inherited even when bInheritHandles=FALSE Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)salilab.org Created an attachment (id=18729) --> (http://bugs.winehq.org/attachment.cgi?id=18729) test.c The attached file uses CreateProcess to create a subprocess (gzip in this case) with redirected standard output. In order for this to work properly, the output handle created in this code must be inherited by the subprocess - thus the bInheritHandles argument to CreateProcess must be TRUE. And indeed if this program is compiled to test-true.exe, a simple text file 'test.in' and the gzip binary are placed in the same directory, and then test-true.exe is run, it successfully produces the output test.gz. If the TRUE argument is switched to FALSE and the file is compiled again to test-false.exe, when the program is run in the same way on a 'real' Windows sytem (32 bit Vista Business in this case) the following is output: gzip: stdout: Bad file descriptor This is also fine and expected, since the output file handle was not passed to gzip. *However* if the same test-false.exe program is run with Wine (the Fedora 10 wine-core-1.1.12-1.fc10.i386 package in this case) it runs in just the same way as test-true.exe, generating the test.gz output. This suggests to me that the bInheritHandles argument is ignored by Wine. As stated, this is a minor bug but it would be nice if Wine behaved the same way as Windows here. (In our case we discovered this problem after we tested our program successfully under Wine, but then had it fail on a real Windows system.) I am not familiar with the code, but hopefully it should be straightforward enough to provide the subprocess with invalid handles if bInheritHandles=FALSE? -- 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 17

[Bug 42024] New: FL Studio 12.4 installer crashed
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=42024 Bug ID: 42024 Summary: FL Studio 12.4 installer crashed Product: Wine Version: 2.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikhail.v.gavrilov(a)gmail.com Distribution: --- Created attachment 56484 --> https://bugs.winehq.org/attachment.cgi?id=56484 backtrace $ wine Muzon/Image-Line.FL.Studio.Producer.Edition.v12.4.Incl.Keygen-R2R/flstudio_12.4.exe fixme:thread:GetThreadUILanguage : stub, returning default language. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d198, (nil) 0x33d1c0 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d198 (nil) 0x33d1c0) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d198, 0x1a7a680 0x33d1c0 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d198 0x1a7a680 0x33d1c0) returning a dummy value (current locale) fixme:thread:GetThreadUILanguage : stub, returning default language. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d198, (nil) 0x33d1c0 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d198 (nil) 0x33d1c0) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d198, 0x1a7a680 0x33d1c0 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d198 0x1a7a680 0x33d1c0) returning a dummy value (current locale) fixme:thread:GetThreadUILanguage : stub, returning default language. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d198, (nil) 0x33d1c0 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d198 (nil) 0x33d1c0) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d198, 0x1b8a680 0x33d1c0 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d198 0x1b8a680 0x33d1c0) returning a dummy value (current locale) wine: Unhandled exception 0x0eedfade in thread 7d at address 0x7b43fa6e (thread 007d), starting debugger... -- 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 52330] New: iZotope software authorization process fails
by WineHQ Bugzilla March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=52330 Bug ID: 52330 Summary: iZotope software authorization process fails Product: Wine-staging Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frech(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71492 --> https://bugs.winehq.org/attachment.cgi?id=71492 journalctl log during authorization process Authorizing iZotope software will result in an error. According to the iZotope Support, the attempt is visible, but the local application did not recognize that. Also see attachment. -- 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 20

[Bug 49393] New: Gag game crash
by WineHQ Bugzilla March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=49393 Bug ID: 49393 Summary: Gag game crash Product: Wine Version: 5.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: axet(a)me.com Distribution: --- Hello! I'm trying to run 'Gag' game. And it's crashing winmm reading at zero memory address. I've tested few wine versions 5.0.0 .. 5.10 and all have same issue. https://en.wikipedia.org/wiki/GAG_The_Impotent_Mystery If you want trying to run the game, you gonna need start X server with 16-bit display like this: Xephyr :1 -ac -screen 800x600x16 & Crash output: 5.10 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7db6). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7db6 ESP:016cf7c0 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:00ca3e08 ECX:016cf760 EDX:000001d0 ESI:00000000 EDI:014afb1c Stack dump: 0x016cf7c0: 009b38b8 639ec090 00000001 00000000 0x016cf7d0: 00ca3e24 00000000 00000000 639d85b5 0x016cf7e0: 00ca3ed4 00000008 000000e8 7ea09ea0 0x016cf7f0: 00000001 016cf810 016cf8cc 016cf820 0x016cf800: 0000001c 7ffc4000 0000003f 00ca0cf0 0x016cf810: 00ca0cf0 016cf830 639efe20 00ca3e08 Backtrace: =>0 0x639d7db6 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8688 EntryPoint+0xffffffff() in winmm (0x00ca3ed4) 2 0x639da5b9 EntryPoint+0xffffffff() in winmm (0x016cf918) 3 0x7ea1bd0c in user32 (+0x9bd0b) (0x016cf918) 4 0x7ea1c35d in user32 (+0x9c35c) (0x016cf968) 5 0x7ea1e5a3 in user32 (+0x9e5a2) (0x016cf9b8) 6 0x7e9db0f2 in user32 (+0x5b0f1) (0x016cfa28) 7 0x7e9dd6c7 in user32 (+0x5d6c6) (0x016cfe48) 8 0x7e9e32df in user32 (+0x632de) (0x016cfea8) 9 0x639d9949 EntryPoint+0xffffffff() in winmm (0x016cff5c) 0x639d7db6 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) 5.0.0 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7b36). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7b36 ESP:0127f700 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:0089e300 ECX:0127f6a0 EDX:0089e678 ESI:00000000 EDI:0105fb0c Stack dump: 0x0127f700: 0089c3c8 639eb090 00000001 00000000 0x0127f710: 0089e31c 00000000 00000000 639d8335 0x0127f720: 0089e3cc 00000008 000000e8 0127f750 0x0127f730: 0000000c 00030038 0127f768 7e925c50 0x0127f740: 7ea78cc0 7ffc4000 0000003f 0089c9f0 0x0127f750: 0089c9f0 0127f770 639eee20 0089e300 Backtrace: =>0 0x639d7b36 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8408 EntryPoint+0xffffffff() in winmm (0x0089e3cc) 2 0x639da339 EntryPoint+0xffffffff() in winmm (0x0127f858) 3 0x7e93863c in user32 (+0xa863b) (0x0127f858) 4 0x7e938cad in user32 (+0xa8cac) (0x0127f8a8) 5 0x7e93b113 in user32 (+0xab112) (0x0127f8f8) 6 0x7e8f635e in user32 (+0x6635d) (0x0127f968) 7 0x7e8f8a7f in user32 (+0x68a7e) (0x0127fe38) 8 0x7e8fedca in user32 (+0x6edc9) (0x0127fe98) 9 0x639d96c9 EntryPoint+0xffffffff() in winmm (0x0127ff4c) 0x639d7b36 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) -- 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 5

[Bug 42027] New: Xilinx Vivado 2014.4 installer fails: systeminfo is a stub
by wine-bugs＠winehq.org March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=42027 Bug ID: 42027 Summary: Xilinx Vivado 2014.4 installer fails: systeminfo is a stub Product: Wine Version: 2.0-rc1 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: jack.lovell(a)ukaea.uk Created attachment 56490 --> https://bugs.winehq.org/attachment.cgi?id=56490 Log output until the installer crashes. When trying to run the Xilinx Vivado 2014.4 web installer, the program crashes shortly after startup. A look at the log output suggests the installer is calling systeminfo and piping the output to findstr to get the OS version. However, systeminfo is a stub, and so outputs nothing to stdout. I plan to file the findstr stub as a separate 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.

3 11

[Bug 57415] New: ROMCenter crash after creating database > IO Exception cannot locate resource images/defaultsystemicon.png
by WineHQ Bugzilla March 6, 2026

March 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=57415 Bug ID: 57415 Summary: ROMCenter crash after creating database > IO Exception cannot locate resource images/defaultsystemicon.png Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: augusto7744(a)aol.com Distribution: --- Hello. Thanks for reading my topic. Ubuntu 24.04.1 and WINE 9.18 ( version 9.21 crash some softwares related with the bug https://bugs.winehq.org/show_bug.cgi?id=57306 so not tested with that version ). ROMCenter 4.1.1 32 bits. An rom manager software using database hash. When is done the creation of database happen an crash showing the error message below and close the software. IO Exception cannot locate resource images/defaultsystemicon.png Seeing in some sites is as if is related with net framework. Some WINE previous versions the software run perfectly without errors. Perhaps is related with wine-mono ? Have an nice week. -- 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 16

[Bug 47279] New: TP-Link PowerLineUtility installs but does nothing
by wine-bugs＠winehq.org March 4, 2026

March 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=47279 Bug ID: 47279 Summary: TP-Link PowerLineUtility installs but does nothing Product: Wine Version: 4.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dave(a)davehigton.me.uk Distribution: --- The TP-Link PowerLineUtility.exe installes OK under wine 4.9 (my thanks to the team for fixing the bug I reported recently which prevented installation). Running the installed app offers me "Trust and launch", whereupon I get the "round hourglass" for about 15 seconds, then... nothing. No error window, no nothing. It should be accessing the status and configuration of the power line modems that I have. The Linux box it's on is communicating over them to post this message. The app in question can be downloaded from https://static.tp-link.com/2018/201809/20180904/PowerLineUtility_Win_180816… -- 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 3

[Bug 52570] New: d3d:debug_d3dformat Unrecognized 0x34324644 & 0x36314644 WINED3DFORMAT
by WineHQ Bugzilla March 4, 2026

March 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=52570 Bug ID: 52570 Summary: d3d:debug_d3dformat Unrecognized 0x34324644 & 0x36314644 WINED3DFORMAT Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- Hi all! It looks like there are present two unimplemented ATI texture features in WineD3D. I can confirm this for the Unigine Sanctuary benchmark. When WineD3D is used, I get on startup an "Unrecognized 0x34324644 (as fourcc: DF24)" and "Unrecognized 0x36314644 (as fourcc: DF16)" error message. Shortly after this the benchmark stops / halts. There is at the CLI the following information avaiable: ---- Render ---- Renderer: ATI R500 256Mb Direct3D9 desc: ATI Radeon X1600 Series Direct3D9 driver: atiumdag.dll Found required D3DPTEXTURECAPS_CUBEMAP Found required D3DPTEXTURECAPS_VOLUMEMAP Found required D3DPTADDRESSCAPS_WRAP Found required D3DPTADDRESSCAPS_CLAMP Found required D3DCAPS2_CANAUTOGENMIPMAP Found optional Vertex shader 3.0 Found optional Pixel shader 3.0 Found optional Vertex texture fetch Found optional HDR blending Found optional HDR filtering Found optional NULL texture Found optional RGB10A2 texture Found optional DXT texture compression Found optional ATI texture compression 1 Found optional ATI texture compression 2 0110:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! 0110:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table. 0110:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT! 0110:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table. 0110:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! 0110:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table. Found optional NVIDIA hardware shadow Found ATI alpha to coverage Found optional NVIDIA alpha to coverage Maximum texture width: 4096 Maximum texture height: 4096 Maximum render targets: 4 Interestingly this doesn't occur when Gallium Nine is used: ---- Render ---- Renderer: ATI R500 256Mb Direct3D9 desc: ATI Radeon X1600 Series Direct3D9 driver: atiumdag.dll Found required D3DPTEXTURECAPS_CUBEMAP Found required D3DPTEXTURECAPS_VOLUMEMAP Found required D3DPTADDRESSCAPS_WRAP Found required D3DPTADDRESSCAPS_CLAMP Found required D3DCAPS2_CANAUTOGENMIPMAP Found optional Vertex shader 3.0 Found optional Pixel shader 3.0 Found optional Vertex texture fetch Found optional HDR blending Found optional HDR filtering Found optional NULL texture Found optional RGB10A2 texture Found optional DXT texture compression Found optional ATI texture compression 1 Found optional ATI texture compression 2 Found optional ATI texture fetch 4 Found optional ATI hardware shadow Found optional NVIDIA hardware shadow Found ATI alpha to coverage Found optional NVIDIA alpha to coverage Maximum texture width: 4096 Maximum texture height: 4096 Maximum render targets: 4 So it looks that the "ATI texture fetch 4" and "ATI hardware shadow" features are not implemented in WineD3D. ;-) And by the way, the function "Vertex texture fetch" isn't supported by all ATI R500 based hardware so it shouldn't be listed as avaiable. Regarding this there exist a bug report on Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6053 -- 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 6