January 2023 - Wine-Bugs - list.winehq.org

[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

[Bug 52625] New: Vertex texture fetch advertised on R300-R500 class AMD hardware
by WineHQ Bugzilla March 2, 2026

March 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=52625 Bug ID: 52625 Summary: Vertex texture fetch advertised on R300-R500 class AMD hardware Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: pavel.ondracka(a)gmail.com CC: stefan(a)codeweavers.com Distribution: --- I'm not 100% sure if this is an app bug, or if wine messes something up, but Unigine sanctuary reports: Found optional Vertex texture fetch and later fails badly, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/6053 This is with mesa r300 driver (latest git). None of the R300-R500 cards have vertex texture support and as far as I can see mesa correctly reports GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS = 0 BTW Anno1404 under nine also produces TXL opcodes in vertex shaders, but there is might be also gallium-nine problem. The Sanctuary is with pure 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 6

[Bug 40157] New: logger32 Crash changing columns order
by wine-bugs＠winehq.org March 2, 2026

March 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=40157 Bug ID: 40157 Summary: logger32 Crash changing columns order Product: Wine Version: 1.9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: luca.civinini(a)gmail.com Distribution: --- Created attachment 53659 --> https://bugs.winehq.org/attachment.cgi?id=53659 Logger 32 backtrace Logger32 is an ham radio operator logging software (www.logger32.net) Installed wine-1.9.1 (Staging) under Fedora 23. created a 32 bit WINEPREFIX as a Windows XP environment with default settings Logger32 installs and starts ok. But if you right click on the logbook page, then select SETUP -> GRID LAYOUT and try to change some checkboxes (didn't matter which one), when clicking APPLY or CANCEL a crash will occur. Similar crashes also happens in other similar windows. Crash seems to occur every time a "modal" window is closed. I've tried setting several DLLs to native but no luck. -- 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 2

[Bug 29775] New: Cannot install OrCAD 16.5
by wine-bugs＠winehq.org March 2, 2026

March 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=29775 Bug #: 29775 Summary: Cannot install OrCAD 16.5 Product: Wine Version: 1.4-rc1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: ehoover(a)mines.edu Classification: Unclassified The installer for the OrCAD 16.5 Lite/Demo version (OrCAD_16.5_Demo_CapturePSpiceOnly.exe) does not ungray the "Next" button on the page for choosing the installation type (everyone vs. local user). This issue renders the 16.5 version of OrCAD unusable. This installer can be retrieved a number of places, one location is: http://www.ecse.rpi.edu/courses/S12/ENGR-4300/OrCAD/OrCAD_16.5_Demo_Capture… -- 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 9

[Bug 33350] New: Maxthon 4 fails to start
by wine-bugs＠winehq.org March 2, 2026

March 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=33350 Bug #: 33350 Summary: Maxthon 4 fails to start Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gmazzone0(a)aol.com Classification: Unclassified When I open Maxthon 4, it shows a blonk page with:"Missing: sidebar/index.html Missing: layout:html" and can't be used -- 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 17

[Bug 39844] New: iqfeed.exe does crash after running couple of hours
by wine-bugs＠winehq.org March 2, 2026

March 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=39844 Bug ID: 39844 Summary: iqfeed.exe does crash after running couple of hours Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mozdemir(a)gmail.com Distribution: --- Created attachment 53193 --> https://bugs.winehq.org/attachment.cgi?id=53193 winedbg output Hi, i have windows applications iqfeed.exe. I run it using wine.it does run pretty well but after couple of hours it does crash. All System info is below. I attach the winedbg/back trace file, too. Thanks a lot, musti System information: Wine build: wine-1.6.2 Platform: i386 Host system: Linux Host version: 3.19.0-30-generic -- 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 4

[Bug 50824] New: ISdone.dll error 5, something releated to insufficient virtual memory
by WineHQ Bugzilla March 2, 2026

March 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=50824 Bug ID: 50824 Summary: ISdone.dll error 5, something releated to insufficient virtual memory Product: Wine Version: 6.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gab.pulcio(a)gmail.com Distribution: --- Created attachment 69642 --> https://bugs.winehq.org/attachment.cgi?id=69642 WINEDEBUG loaddll Warning: I know I'm about to ask you to fix something releated to game repacks, which they're illegal (provided I don't have the legal copy) but in my logic, that's a windows releated-thing and it should be fixed, maybe not now, but at least should be considered. Now, fitgirl repacks crashes at random progress, while rg-mechanics repacks are straight to the error, the same as always. I read that in the past this was fixed so that's a regression but since no-one has reported this and apparently no one has that problem, I'm filing this bug as normal. For the record: this bug happens since I installed linux, at the time Wine was at version 6.0. In my case, this repack is of a game that I legally own (Far Cry 3: Blood Dragon) but I've got a capped data plan and I have to install a repack then I'll be able to verify the game with Uplay. -- 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 19368] New: lpfnWndProc can't catch Up/Down/Left/Right and CTRL+ other Button
by wine-bugs＠winehq.org March 1, 2026

March 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=19368 Summary: lpfnWndProc can't catch Up/Down/Left/Right and CTRL+ other Button Product: Wine Version: 1.1.26 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sakaihdt(a)d2.dion.ne.jp Hello I want to use "sakura editor". (a Japanese Open Souce text editor for MS Windows) (http://sakura-editor.sourceforge.net/) But this application is not work well in wine(1.0.1 or 1.1.26 Ubuntu GNU/Linux 9.0.4) - Not work Up/Down/Left/Right button in text area - Not work CTRL+C or CTRL+A and other in text area - Not work Backspace in text area - Not work Function Key in text area normal text button( a-z, 0-9 ) is work well, and Up/Down... is work well in menu . "sakura editor" catch Up/Down/Ctrl event from lpfnWndProc() callback. but wine's lpfnWndProc seem not work when push Up/Down... key. ( I insert log in sakura editor source and check.) I have 2 question. please tell me. (1) Can lpfnWndProc() catch Up/Down/Left/Right CTRL+A,X,C and Function key in Wine ? (2) "lpfnWndProc() can catch Up/Down/Left/Right ..." is WindowsAPI specification? Thank you. -- 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 13

[Bug 34134] New: "open file" dialog does not shrink after switching to "use adobe dialog" and back to system dialog
by wine-bugs＠winehq.org March 1, 2026

March 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=34134 Bug #: 34134 Summary: "open file" dialog does not shrink after switching to "use adobe dialog" and back to system dialog Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: unxed(a)mail.ru Classification: Unclassified If you press "use adobe dialog" button in "open file" dialog, it grows. If you press "use os dialog" after it, window does not shrink back. -- 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 3

[Bug 33241] New: incorrect display of a combobox in a Clipper application
by wine-bugs＠winehq.org March 1, 2026

March 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=33241 Bug #: 33241 Summary: incorrect display of a combobox in a Clipper application Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ironeman(a)tiscali.it Classification: Unclassified As mentioned in http://forum.winehq.org/viewtopic.php?f=8&t=18198, I am using 16-bit Clipper/xBase programs. When I have a listbox, the field is not correctly initialized, despite the list is ok. Debugging my application, I have found that it is due to a strange memory management. I start by saying that Clipper/xBase uses dynamic scoping, so the value of a variable is the last assigned to it into the stack; a variable can be local or global (prefixed by m->). When using the dialog that has the problem, I use the activation command (Fivewin library): m->mTipoDoc:=.... // assign the global variable m->mTipoDoc activate DIALOG oDlg centered on init (SettaCombo()) function SettaCombo() // initialization code of the dialog ... // use the global variable m->mTipoDoc but, at this point, when using WINE, the variable has lost its content and is empty I solved the problem using a local variable that temporarily holds the value of the global variable: m->mTipoDoc:=.... // assign the global variable m->mTipoDoc local tmpcod:=m->mTipoDoc // to solve the wine bug activate DIALOG oDlg centered on init (SettaCombo(tmpcod)) function SettaCombo(val) m->mTipoDoc:=val // to solve the wine bug ... // use the global variable m->mTipoDoc Evidently the local variable is managed in a different way by WINE and the error has disappered. To test this behaviour, I wrote the attached sample program. Into the zip there is a readme.pdf that explains how it works. Best regards. -- 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 5