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

[Bug 56921] New: MusicBee: Random moments of lag when scrolling, seemingly related to rendering of rating stars.
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=56921 Bug ID: 56921 Summary: MusicBee: Random moments of lag when scrolling, seemingly related to rendering of rating stars. Product: Wine-staging Version: 9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: v_winebugs(a)outlook.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 76742 --> https://bugs.winehq.org/attachment.cgi?id=76742 Log from terminal Tested on Wine 9.5-staging, on Fedora 40 KDE Plasma Spin MusicBee will have these random moments of lag when scrolling on views and playlists that have rating stars enabled. It seems to be related to how the stars are being rendered, since when they are hidden the lag goes away, and this lag is not present when running MusicBee under Windows. To make it worse, this lag persists after the app is restarted. Attached is a log from the terminal done while using MusicBee with the lag. -- 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 10

[Bug 54660] New: Call of Juarez shows 'Assertion failed: deref->offset_regset == HLSL_REGSET_NUMERIC'
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54660 Bug ID: 54660 Summary: Call of Juarez shows 'Assertion failed: deref->offset_regset == HLSL_REGSET_NUMERIC' Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Assertion failed: deref->offset_regset == HLSL_REGSET_NUMERIC, file ../vkd3d/libs/vkd3d-shader/hlsl_codegen.c, line 3143 1.6-199-gda243570 -- 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 48912] New: Allow blacklisting unreliable and always new failures
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48912 Bug ID: 48912 Summary: Allow blacklisting unreliable and always new failures Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- A number of tests produce false positives because: * Either the failure message contains a value that changes with each run (e.g. an HWND). In some cases these values are really necessary for diagnosis and moving them to a separate line would make the code quite a bit more complex. * Or the test fails intermittently and is hard to fix. Sometimes the cause of the failures may also come from external factors such as bugs in QEmu (for instance long execution delays causing timeouts). * Sometimes the intermittent failure is the product of a new Windows version or configuration, which requires investigating before a fix is found. In all cases the tests should be fixed eventually, but a solution is needed for the interim so these tests to not make the TestBot so unreliable that its results are ignored. So the goal is to provide a way to blacklist some test failures so they do not cause a patch to be rejected. Some safeguards are needed to ensure that: * Failures are not blacklisted lightly. The preference should always be to fix the test. * The blacklist does not get so large that it becomes hard to maintain. * Once a test is fixed the corresponding blacklist entries are removed in a timely fashion. * There is still an incentive to fix the tests. So here is a proposal for implementing this blacklist: * Each blacklist entry should be associated with a Wine bug describing the issue. That bug should provide some minimal diagnosis: whether it's a new Windows behavior, a race condition or some issue that was reported to QEmu. That would ensure we know why the blacklist entry was added. One could also check the status of the bug when reviewing the blacklist entries. A closed bug would be a strong hint that the blacklist entry is no longer needed. * Rather than blacklisting whole test units, blacklist entries should target specific test failures via a regular expression. Besides being finer grained this would be useful for cases like user32:win which has different issues depending on the locale and where each should be linked to a different bug (bugs 48815, 48819 and 48820). * The TestBot should record when each blacklist entry was last used. This relies on having the above regular expression since without it the TestBot would not know anything beyond 'the test unit was run and had failures'. Also the regular expression would only be used against *new* failures. So this would really record the last time the blacklist entry was actually useful. An entry that was unused for a long time would be a prime candidate for reviewing the corresponding bug and for removal. (Note: The blacklist would also be used on WineTest reports so it would get a chance of matching its target at least 5 days / week). * The blacklist entries would only be needed for 'base' test configurations since they are the only ones wine-devel patches run on. * There should be a page listing the blacklist entries so developers have a good starting point to work on them. * Ideally the blacklist page would also point to the tasks where the blacklist was last used. Since most of the blacklisted failures are either intermittent or specific to a given test configuration this would make it easier for developers to find reports where the failure did happen. Note that Wine VMs often test multiple configurations per task (e.g. wow32 and wow64, different locales), each producing its own test report. So pointing at just the task would leave the developer guessing which report should be looked at. But that may be sufficient guidance. * (test:unit, testbot-vm) tuples make it impossible to target a specific Wine test configuration such as a specific locale since they all run on the same VM. Similarly it would make blacklisting bitness-blind on Windows VMs. If necessary the tuple could be extended either with the specific mission the blacklist applies to, or with the basename of the corresponding report (the latter being easier to use in comparisons). Whether that's practical and worth the effort remains to be determined. One complication for instance is that this would lead to more blacklist entries: many 64 bit VMs would need two entries, one for 32 bit tests and one for 64 bit tests. * Pseudo database schema and sample use: FailureBlacklists ----------------- PK Bug 48815 PK TestModule user32 PK TestUnit win Name 0x738 message FailureRegExp Test failed: hwnd [0-9A-F]{8,16} message 0738 LastUse 2020-03-27 FailureBlacklistVMs ------------------- PK Bug 48815 PK TestModule user32 PK TestUnit win PK VMName Entries for w1064v1709, w1064v1809, etc. (48815, user32, win, w1064v1709) (48815, user32, win, w1064v1809) (48815, user32, win, w1064v1809_2scr) ... FailureBlacklistUses (optionally) --------------------------------- PK Bug PK TestModule PK TestUnit PK JobId PK StepNo PK TaskNo (48815, user32, win, 68507, 1, 7) (48815, user32, win, 68508, 1, 7) ... -- 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 57251] New: Keepass 2: program crashes when clicking on the User name field to add or change an entry
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=57251 Bug ID: 57251 Summary: Keepass 2: program crashes when clicking on the User name field to add or change an entry Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bouwe(a)westerdijk.info Distribution: --- Created attachment 77169 --> https://bugs.winehq.org/attachment.cgi?id=77169 Saved crash report As described in the Summary. -- 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 38583] New: Legions Overdrive: In-game textures black
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=38583 Bug ID: 38583 Summary: Legions Overdrive: In-game textures black Product: Wine Version: 1.7.42 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: gaming4jc2(a)yahoo.com Distribution: --- Created attachment 51481 --> https://bugs.winehq.org/attachment.cgi?id=51481 D3D fixmes Since the entire world is black excepting the sky and some text, it is still not possible to play this in native wine without DLL overrides. I am attaching a bug report showing various D3D fixmes needed. -- 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 14

[Bug 57098] New: Battle.net does not start after upgrade to 9.16
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=57098 Bug ID: 57098 Summary: Battle.net does not start after upgrade to 9.16 Product: Wine Version: 9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: sfjuocekr(a)gmail.com Distribution: --- Created attachment 76977 --> https://bugs.winehq.org/attachment.cgi?id=76977 log Battle.net does not work with the latest wine-staging = 9.16 I had just updated wine from apt, the launcher starts but during login it opens a command prompt with error message that closes and opens repeatedly. I suppose this has something to do with the latest cmd.exe changes? -- 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 23

[Bug 54778] New: Multiple apps need support for SM1 non-float expression (Strong Bad's Cool Game for Attractive People Episode 1: Homestar Ruiner, Darksiders II Deathinitive Edition (GOG), NewoAsteroids played with Dolphin emulator)
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54778 Bug ID: 54778 Summary: Multiple apps need support for SM1 non-float expression (Strong Bad's Cool Game for Attractive People Episode 1: Homestar Ruiner, Darksiders II Deathinitive Edition (GOG), NewoAsteroids played with Dolphin emulator) Product: vkd3d Version: 1.7 Hardware: x86-64 URL: https://www.moddb.com/games/strong-bad/downloads/stron g-bad-s-cool-game-for-attractive-people-demo OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- 0114:err:d3dcompiler:D3DCompile2 <anonymous>:9:11: E5017: Aborting due to not yet implemented feature: SM1 non-float expression. -- 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 54472] New: Cryostasis: Sleep of Reason demo crashes due to HLSL syntax error 'unexpected KW_TECHNIQUE10'
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54472 Bug ID: 54472 Summary: Cryostasis: Sleep of Reason demo crashes due to HLSL syntax error 'unexpected KW_TECHNIQUE10' Product: vkd3d Version: 1.6 Hardware: x86-64 URL: https://www.guru3d.com/files-details/cryostasis-sleep- of-reason-game-demo.html OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 00d4:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x804. 00d4:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 00d4:err:d3dcompiler:D3DCompile2 Shader log: 00d4:err:d3dcompiler:D3DCompile2 signature.fx:8:1: E5000: syntax error, unexpected KW_TECHNIQUE10 00d4:err:d3dcompiler:D3DCompile2 1.6-110-g240b2f96 -- 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 41123] New: 8-bit Armies requires "fx_5_0" compilation target
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=41123 Bug ID: 41123 Summary: 8-bit Armies requires "fx_5_0" compilation target Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- When I was testing this bug: https://bugs.winehq.org/show_bug.cgi?id=40725 I noticed that 8-bit Armies would show this line in the terminal before crashing: fixme:d3dcompiler:compile_shader Compilation target "fx_5_0" not yet supported Native d3dcompiler_43 via "winetricks d3dcompiler_43" works around the issue. -- 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 6

[Bug 56786] New: Proprietary native ODBC driver crashing
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=56786 Bug ID: 56786 Summary: Proprietary native ODBC driver crashing Product: Wine-staging Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: steve.fawcett(a)bitnosis.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 76592 --> https://bugs.winehq.org/attachment.cgi?id=76592 Backtrace of failing call (Using wine-9.10 (Staging) as I believe staging id required for native odbc) .Net app to retrieve data via odbc using a proprietary native 64 bit odbc driver fails with System.AccessViolationException 'Attempted to read or write protected memory' when interop is calling 'SQLDriverConnectW' Tried c++ to remove .Net from the equation and depending on what connection string is used it yields a different error. If connection details are passed in the connectionstring ie: Driver=xxxxx ODBC driver;Server=x.x.x.x,yyy;DBNAME=xxxxx;UID=xxxxx;PWD=xxxxx; The following error occurs: Error in SQLDriverConnect(hDbc, GetDesktopWindow(), pwszConnStr, SQL_NTS, NULL, 0, NULL, SQL_DRIVER_COMPLETE) 0024:fixme:odbc:SQLFreeHandle (HandleType 2, Handle 00000000006F3DA0) 0024:fixme:odbc:SQLFreeHandle (HandleType 1, Handle 00000000006F3D70) A backtrace is not given and even when launching via 'wine winedbg ...', setting $BreakOnFirstChance=0 and 'cont'inuing I do not get one. If I pass a DSN in the connection string of a data source preconfigured in the registry (exported from working windows machine and imported): DSN=xxxxx;UID=xxxxx;PWD=xxxxx A backtrace is produced (attached, albeit with failing dll renamed to xodbc64). I can supply the driver privately on 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.

2 3