December 2024 - Wine-Bugs - list.winehq.org

[Bug 52566] New: d3d11:d3d11 fails in test_clip_distance() on cw-gtx560
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=52566 Bug ID: 52566 Summary: d3d11:d3d11 fails in test_clip_distance() on cw-gtx560 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 has had failures on cw-gtx560 forever [1] but it recently started exhibiting a few new failures in test_clip_distance() on cw-gtx560: d3d11.c:29488: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29054: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29061: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29077: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29089: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29054: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29061: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29077: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29089: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29519: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29054: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29061: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29077: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29089: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29542: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29557: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29569: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. d3d11.c:29582: Test failed: Got 0x00000000, expected 0xff00ff00 at (0, 0, 0), sub-resource 0. https://test.winehq.org/data/patterns.html#d3d11:d3d11 A bisect shows that these failures started with the same commit that causes failures on cw-rx460 (see bug 52563): commit a13fc3bb7e055562b8b9deae985c64c5c7861424 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Fri Feb 11 19:42:02 2022 -0600 wined3d: Use the chunk allocator for GL vertex buffers. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> [1] To be fair it got a lot better on 2022-02-09 but sadly these new failures appeared on a few days later. It's still better than it used to be. -- 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.

1 7

[Bug 57213] New: Starcraft 2 ram usage problem
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57213 Bug ID: 57213 Summary: Starcraft 2 ram usage problem Product: Wine-staging Version: 9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: calmstorm(a)posteo.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Basically, I play one game of Starcraft 2 via wine-staging. If its long enough, it will start to lag severely if i play a 2nd game, severe lag. By severe, I mean the players in the game are forced to drop me within minutes if I don't leave. I am not sure how I should save a log of this. all I know is that I start the game, I am using 1.5GB once I start it. After the first game or 40 minutes, I am using 5.6GB! Very annoying it is. Any advice as to how to fix this? PS, using a Debian fork known as Devuan. Its based on debian bookworm btw. -- 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.

1 4

[Bug 56807] New: Procedure "DllCanUnloadNow" not found in ole32
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=56807 Bug ID: 56807 Summary: Procedure "DllCanUnloadNow" not found in ole32 Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: mywine(a)schiermeier-it.de Distribution: --- While running and tracing "The Bat!" mailer under wine I got a hint about a missing procedure call to the procedure "DllCanUnloadNow". Please see attachment named: thebat-trace-1.log More info about this procedure see here: https://learn.microsoft.com/de-de/windows/win32/api/combaseapi/nf-combaseap… -- 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.

1 3

[Bug 56002] New: Adaptive sync results in transient halved refresh rate with winewayland
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=56002 Bug ID: 56002 Summary: Adaptive sync results in transient halved refresh rate with winewayland Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Component: winewayland.drv When running Cyberpunk 2077 using winewayland (vkd3d-proton/dxvk's dxgi set up in the prefix with Wine 9.0-rc1 + esync), there is a transient issue when monitor's refresh rate drops to half of the game framerate instead of matching it as adaptive sync should do. DE: KDE Plasma 5.27.9. I measure game framerate with MangoHud and monitor's refresh rate with on-screen OSD. With winex11 they match, with winewayland they match most of the time, but sometimes refresh rate is halved. So for example the game would have 128 fps and OSD will show 64 Hz. Since it only happens with winewayland, there must be something specific going on with it. KWin developers suggested it could have something to do with some additional subsurfaces preventing direct scanout for example. -- 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.

1 18

[Bug 49767] New: All resources deleted during update Logos Bible Software
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=49767 Bug ID: 49767 Summary: All resources deleted during update Logos Bible Software Product: Wine Version: 5.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: johnpgoodman(a)gmail.com Distribution: --- Created attachment 68072 --> https://bugs.winehq.org/attachment.cgi?id=68072 Console output from during update Updates result in data wipe. Logos stores all resources, eg. ebooks, videos etc in a subdir like drive_c/users/$username/Local Settings/Application Data/Logos/Data/$uniqueid/ResourceManager/ When an update to Logos Bible Software becomes available there is a notification in the app. The update will usually install ok however on wine the Resources are all wiped. The user is now stuck with a massive download eg. 40gb+. On Windows the resources are always still there after an update. It's as if the msi somehow overwrites the directory rather than merging with it? I've attached a console log updating from 8.15.0.0004 to 8.16.0.0002 - in this case the update also did not relaunch the newly updated app but simply kept running. At this point I checked and confirmed all resources were wiped. Once quit and reloaded it was clear the update had completed but it began to download everything again. -- 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.

1 25

[Bug 56985] New: how to improve the performance of Wine?
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=56985 Bug ID: 56985 Summary: how to improve the performance of Wine? Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: csumushu(a)126.com Distribution: --- Created attachment 76816 --> https://bugs.winehq.org/attachment.cgi?id=76816 demo.c I have found that my program runs much slower when using Wine compared to running it directly on Windows. On Windows, it responds quickly, but when running with Wine, there is a delay of three to four seconds. After analyzing the program code, I discovered a loop within which semaphore operations are performed. The time consumption for a single semaphore operation is 10-4 seconds when using Wine, whereas it only takes 10-6 seconds on Windows. I wrote a demo program to test it and indeed confirmed this. Semaphore operations are just one example; some other Windows APIs are also significantly slower when compared to Windows. Is there any way to optimize this? -- 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.

1 7

[Bug 45151] New: patches: 'git send-email' through Zoho SMTP causes patch queue to go berserk
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=45151 Bug ID: 45151 Summary: patches: 'git send-email' through Zoho SMTP causes patch queue to go berserk Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: kyle.auble(a)zoho.com Distribution: --- Created attachment 61339 --> https://bugs.winehq.org/attachment.cgi?id=61339 I'm starting to get embarrassed So I'll probably just start using my Gmail account for submissions to Wine anyways, but I've been having problems sending patches through Zoho. I've followed the instructions on https://wiki.winehq.org/Submitting_Patches and when running 'git send-email', there are no issues on my computer. I'm prompted for my SMTP password, git does its thing, and I've received an "OK / 250" return code every time. Small, one-off patches seem to make it through fine, but beyond that, then the wine-devel or the patch-list doesn't get them. Furthermore, Zoho delivers me a message saying that wine-devel can't be reached and that they'll keep retrying the delivery. And they do, which is where I think part of the problem might be coming from. --- In the first case, I tried sending a series of 7 patches. The first patch was a very short text change, the next five were larger batch substitutions on different strings, and the last one was a relatively short binary patch to delete five images. The first patch made it through pretty quickly, but the rest never showed up. To make things more confusing, I received Zoho notices that patches 5-7 couldn't reach the list and would be retried, but nothing about 2-4. Then a few hours later, the mailing list confirmed that patch 7 had made it through fine, but no sign of the middle 5. Since I had no notification from wine-devel or Zoho for patches 2-4, I tried resending patch 2 a couple times. Everything besides patches 1 & 7 seemed to just be falling into a black-hole though... until the next morning, every last patch I had sent (including the repeats of patch 2) was on both wine-devel and the patch-list, showing the original send dates, as if they had been there all along. --- In the second case, I had three large binary patches for deleting old images that have since been moved onto the wiki. I tried sending them one-at-a-time, 'git send-email' gave me an OK / 250, and they never made it to the list. This time Zoho sent me a notice saying that there was a fatal error with wine-devel's address, specifically "ResponseCode 421, Read timed out" The notice said they would keep retrying the delivery for 4 days, but then I didn't hear anything... until all of a sudden, today I see this on the patch queue (screenshot attached). I know I didn't resend either of these patches, much less 17 times. Weirdly enough, the wine-devel mailing list seems to understand what's going on a little better and only shows the message once. --- The one other pattern I have noticed is that it almost seems like the mailing list is clocking out for business hours. The first was on a Wed evening, but it wasn't until the next morning that everything suddenly appeared. The second time, I tried sending in my patches before Friday evening, but there was still no sign of them when I checked yesterday (Sun). Sure enough, they're all there today though. TL/DR: I know very little about how mail protocols work, and it could very well be on my mail service's end, but it almost seems like the mailing-list is actually receiving the emails. It then puts them in quarantine outside of normal work-hours, which doesn't seem like a problem in isolation. Somehow the sender is getting "delivery failed" codes though, and I only seem to get delivery receipts sporadically, despite turning on delivery receipts in my pipermail settings for wine-devel. -- 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 57091] New: Missing wine64 in MacOS build 9.15 distribution (released on github/Gcenx)
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57091 Bug ID: 57091 Summary: Missing wine64 in MacOS build 9.15 distribution (released on github/Gcenx) Product: Wine Version: 9.15 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cytan299(a)yahoo.com After downloading either wine-devel-9.15-osx64.tar.xz or wine-staging-9.15-osx64.tar.xz, I found that wine64 is not included in the distribution. Can wine64 be included thanks! -- 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.

1 3

[Bug 56051] New: Clickteam Fusion Application Bug
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=56051 Bug ID: 56051 Summary: Clickteam Fusion Application Bug Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: coopacademy2020(a)gmail.com Distribution: --- On Wine Staging 8.21, Clickteam Fusion-made applications with things that are activated by hovering your mouse over the bottom of the screen (for example, FNaF games) tend to get triggered without the user allowing the game to do so. This also happens on every version of Windows, including Windows 11, Windows 10, etc. -- 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.

1 5

[Bug 57620] New: High CPU load when setting "Screen resolution" to other value then 96
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57620 Bug ID: 57620 Summary: High CPU load when setting "Screen resolution" to other value then 96 Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- I am seeing a high CPU load (more than 40%) for the application and the Xorg server (also more than 40%) when setting the screen resolution with winecfg to (i.e) 192. Also the window manager shows a high load. With screen resolution 96 the high load does not happen. The application is Framemaker 8 and the Desktop Environment is somewhat special (Trinity desktop, a KDE 3.5 derivate) A bisect shows the following commit 0f1d999bb878ea54214057d3662c116271ec4812 is the first bad commit commit 0f1d999bb878ea54214057d3662c116271ec4812 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Tue Nov 19 13:28:39 2024 +0100 winex11: Update the Win32 window state outside of event handlers. I am grateful for any advice on what further information can help to solve this problem. -- 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.

1 7