July 2020 - Wine-Bugs - list.winehq.org

[Bug 45412] New: Mailing list for AppDB admins/maintainers
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=45412 Bug ID: 45412 Summary: Mailing list for AppDB admins/maintainers Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Distribution: --- The AppDB currently has a link whereby admins can email all maintainers, which is useful for announcements, but not discussion. Discussion of AppDB issues sometimes takes place on wine-devel, but few maintainers subscribe to that mailing list, and the issues are generally not of interest to developers. This is a feature request to add a mailing list for AppDB admins and maintainers, as discussed at WineConf2017. Posting to the list should be limited to those groups, but the posts should be archived on winehq.org and visible to anyone. Subscribing to the list should be automatic based on admin/maintainer status, so if mailman is used to maintain the list, there would need to be a daily cron job to update it. -- 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.

4 9

[Bug 31609] New: TestLauncher says a required DLL is missing, but the test runs fine without TestLauncher
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=31609 Bug #: 31609 Summary: TestLauncher says a required DLL is missing, but the test runs fine without TestLauncher Product: Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified http://source.winehq.org/git/tools.git/blob/HEAD:/testbot/src/TestLauncher/… has a function AllImportedDllsPresent() that tries to avoid running tests that implicitly link against DLLs that aren't present. Unfortunately, in the case of dlls with manifests, it reports it can't find dlls that are in fact present. What it needs is a good dose of the medicine that cured the same problem in winetest: http://www.winehq.org/pipermail/wine-cvs/2010-July/068410.html A quick test shows that this works. I'll send a patch soon. -- 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 14

[Bug 33769] New: Strong Bad's Cool Game for Attractive People Demo crashes without native d3dcompiler_43
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=33769 Bug #: 33769 Summary: Strong Bad's Cool Game for Attractive People Demo crashes without native d3dcompiler_43 Product: Wine Version: 1.6-rc1 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com CC: wine-bugs(a)winehq.org Classification: Unclassified The demo dd2f18068f16a1353a3490d95723b746cec8050f SBCG4AP_Homestar_Ruiner_setup.exe from http://www.strategyinformer.com/pc/strongbadscoolgameforattractivepeople/de… tested with wine-1.6-rc1, crashes unless you do winetricks d3dcompiler_43 I'll attach a +seh,trace+d3dcompiler log. -- 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 18

[Bug 33377] New: Dependencies on third-party import dlls are undetected
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=33377 Bug #: 33377 Summary: Dependencies on third-party import dlls are undetected Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified Created attachment 44167 --> http://bugs.winehq.org/attachment.cgi?id=44167 Patch to reproduce this bug The attached patch reproduces an issue first encountered 'in the wild' with this set of patches: * [1/3] include: Add COM interface definitions needed for PrintDlgEx implementation. http://www.winehq.org/pipermail/wine-patches/2013-April/123420.html * [3/3] comdlg32: Add an interactive PrintDlgEx test. http://www.winehq.org/pipermail/wine-patches/2013-April/123422.html * Re: [3/3] comdlg32: Add an interactive PrintDlgEx test. http://www.winehq.org/pipermail/wine-devel/2013-April/099397.html Here is the core of the issue: * The patch contains a first chunk that modifies include/commdlg.h. * This causes a new symbol to be exported by libuuid.a. * The comdlg32:printdlg test needs that symbol to be relinked. The problem is that the WineTestBot does not do a full recompile (for performance reasons), and thus libuuid.a is not rebuilt. So the comdlg32 relink fails because of the missing symbol. Unfortunately there's really no clear indication in the patch that libuuid.a needs to be rebuilt. We could very well run into the same issue with dxguid or a number of other dlls. Some options: * Systematically do a full rebuild. This would be pretty wasteful. * Do a full rebuild whenever the patch touches 'include/'. * Hardcode a list of uuid-like dlls and rebuild them all whenever a patch touches 'include/'. * Detect which uuid-like dlls the test links with (by parsing the Makefile?), and rebuild those whenever the patch touches 'include/'. It's also possible that any chunk outside of the test directory could get us into trouble if we link with the corresponding dll. -- 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 3

[Bug 48831] New: Crysis needs "gs_4_0" compilation target
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48831 Bug ID: 48831 Summary: Crysis needs "gs_4_0" compilation target Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Intro crashes with: fixme:d3dcompiler:compile_shader Compilation target "gs_4_0" not yet supported wine-5.4-412-g8baf4a2a55 -- 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 43288] New: Eve online opengl crash on mac OS X in library libGPUSupportMercury.dylib at function gpusSubmitDataBuffers ()
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=43288 Bug ID: 43288 Summary: Eve online opengl crash on mac OS X in library libGPUSupportMercury.dylib at function gpusSubmitDataBuffers() Product: Wine-staging Version: 2.11 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: davec.bugs(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Created attachment 58632 --> https://bugs.winehq.org/attachment.cgi?id=58632 eve_online_openg_crash_lldb_backtrace Eve online crashes on mac OS X in library libGPUSupportMercury.dylib at function gpusSubmitDataBuffers(). The crashes occurs randomly. -- 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 5

[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 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 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 48426] New: Wine-Gecko can't be installed.
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48426 Bug ID: 48426 Summary: Wine-Gecko can't be installed. Product: Wine-staging Version: 5.0-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)evolution-hosting.eu CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- wine-staging 64/32 is asking to install Gecko, but the installation attempt hangs at "loading down" with no progress. -- 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