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

[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 55799] New: ws2_32: setsockopt flag IP_RECVIF unimplemented
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=55799 Bug ID: 55799 Summary: ws2_32: setsockopt flag IP_RECVIF unimplemented Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: Littlefighter1996(a)googlemail.com Distribution: --- Created attachment 75287 --> https://bugs.winehq.org/attachment.cgi?id=75287 UDP Receive Program Some applications require IP_RECVIF to be set in order to identify the source (IP Address and Interface) from which a message has been received. This flag is not implemented, leading to either termination of the program or unexpected behavior. -- 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 13

[Bug 43443] New: mouse pointer/focusing issues with wine 2.11.1
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=43443 Bug ID: 43443 Summary: mouse pointer/focusing issues with wine 2.11.1 Product: Wine Version: 2.11 Hardware: x86 URL: https://bugzilla.redhat.com/show_bug.cgi?id=1468889 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)evolution-hosting.eu Distribution: Fedora Description of problem: Since wine got updated to 2.11-1 this morning, i had trouble with the mouse pointer in "Runes of Magic" . The pointer got invisible/stuck/both randomly when moving it on and off the monitor ( dual monitor here ) where ROM was running, wenn moving the char around with WASD controls. This was disturbing and made "dangerouse" gameplay next to impossible, i.o.w. i couldn't risk dangerouse actions in game, because it was uncertain if i could control the game while doing it. After downgrading, it works again flawless ( said that in context with ROM, means something :D ) Version-Release number of selected component (if applicable): 2.11.1-fc25 List of packages installed - Action taken to revert wine back to 2.10 : wine-2.11-1.fc25.i686 38/74 wine-2.11-1.fc25.i686 39/74 wine-fonts-2.11-1.fc25.noarch40/74 wine-desktop-2.11-1.fc25.noarch 41/74 wine-pulseaudio-2.11-1.fc25.i686 42/74 wine-alsa-2.11-1.fc25.i686 43/74 wine-capi-2.11-1.fc25.i686 44/74 wine-cms-2.11-1.fc25.i686 45/74 wine-ldap-2.11-1.fc25.i686 46/74 wine-openal-2.11-1.fc25.i686 47/74 wine-opencl-2.11-1.fc25.i686 48/74 wine-twain-2.11-1.fc25.i686 49/74 wine-core-2.11-1.fc25.i686 50/74 wine-common-2.11-1.fc25.noarch 51/74 wine-times-new-roman-fonts-2.11-1.fc25.noarch 52/74 wine-tahoma-fonts-system-2.11-1.fc25.noarch 53/74 wine-pulseaudio-2.11-1.fc25.i686 54/74 wine-tahoma-fonts-2.11-1.fc25.noarch 55/74 wine-alsa-2.11-1.fc25.i686 56/74 wine-capi-2.11-1.fc25.i686 57/74 wine-cms-2.11-1.fc25.i686 58/74 wine-ldap-2.11-1.fc25.i686 59/74 wine-openal-2.11-1.fc25.i686 60/74 wine-opencl-2.11-1.fc25.i686 61/74 wine-twain-2.11-1.fc25.i686 62/74 wine-systemd-2.11-1.fc25.noarch 63/74 wine-arial-fonts-2.11-1.fc25.noarch 64/74 wine-courier-fonts-2.11-1.fc25.noarch 65/74 wine-fixedsys-fonts-2.11-1.fc25.noarch 66/74 wine-marlett-fonts-2.11-1.fc25.noarch 67/74 wine-ms-sans-serif-fonts-2.11-1.fc25.noarch 68/74 wine-small-fonts-2.11-1.fc25.noarch 69/74 wine-symbol-fonts-2.11-1.fc25.noarch 70/74 wine-system-fonts-2.11-1.fc25.noarch 71/74 wine-wingdings-fonts-2.11-1.fc25.noarch 72/74 wine-core-2.11-1.fc25.i686 73/74 wine-filesystem-2.11-1.fc25.noarch 74/74 Bug has been reported to Fedoras Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1468889 -- 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 54270] New: Random crashing in Overwatch 2
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=54270 Bug ID: 54270 Summary: Random crashing in Overwatch 2 Product: Wine Version: 8.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: nanotwerp(a)gmail.com Distribution: --- While playing Overwatch 2, I experience random crashing. This especially happens when I play Ashe, and I do not recall it happening while playing other characters, but this could be a coincidence. The error I get is: free(): invalid pointer 06a8:err:seh:call_stack_handlers invalid frame 0000000027B4E3E0 (0000000027952000-0000000027A50000) 06a8:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. The same issue was also noted by someone who posted this Blizzard bug report: https://us.forums.blizzard.com/en/blizzard/t/random-crashes-in-game-wow-cla… I believe that this issue is what this merge request by Torge Matthies was made to fix: https://gitlab.winehq.org/wine/wine/-/merge_requests/1152 . Oddly enough, though, after applying Matthies' patch rebased to 8.0-rc2 (https://github.com/openglfreak/wine-tkg-userpatches/search?q=overwatch) I still experience this error. I think that some change in 8.0 (Full-ish PE conversion maybe?) caused this incompatibility with Overwatch 2. -- 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 12

[Bug 57363] New: Find window in Notepad++ does not become translucent after losing focus
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57363 Bug ID: 57363 Summary: Find window in Notepad++ does not become translucent after losing focus Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: francisco278herrera(a)gmail.com Distribution: --- Find window in Notepad++ does not become translucent after losing focus This might be a regression but when it did work the find window didn't have any window decorations T reproduce, using notepad++ version 8.7, press ctrl+f in notepad++ to open the find window, and then click on the text document behind the find window. In wine 9.20 the window doesn't become transparent when it loses focus and the option for it is checked on the find window. In wine 9.0 it does become transparent after losing focus if the option for it is checked in the find window. -- 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 57084] New: WINE without X11/XWayland (pure Wayland) can't find graphics driver
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57084 Bug ID: 57084 Summary: WINE without X11/XWayland (pure Wayland) can't find graphics driver Product: Wine Version: 9.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: redwindwanderer(a)gmail.com Distribution: --- Hello there, I've just built latest stable WINE (9.15) and also latest stable WINE sources from gitlab (https://gitlab.winehq.org/wine/wine/) and I get identical results when trying to load any program with it: 0148:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0148:err:winediag:nodrv_CreateWindow L"The graphics driver is missing. Check your build!" WINE was successfully configured and built using the wine-wayland driver: ./configure --enable-win64 --without-x --with-wayland --without-pulse --without-cups --without-gphoto --without-opencl --without-pcap --without-pcsclite --without-dbus --without-sane --without-oss --without-krb5 --without-netapi --without-capi --without-gettext --without-gnutls --enable-archs=x86_64,i386 As you can see in the configure log attached, the wayland driver is activated correctly. And the wayland WINE driver is installed: ~/src/wine$ find /usr/local -name *winewayland* /usr/local/lib/wine/i386-windows/winewayland.drv /usr/local/lib/wine/x86_64-unix/winewayland.so /usr/local/lib/wine/x86_64-windows/winewayland.drv I also tried forcing the driver loading using: WINEDEBUG=+wayland WINEDLLOVERRIDES="winewayland.drv=n" winecfg But that makes no difference. Maybe mainline WINE is not ready for Wayland-only? Any ideas, please? -- 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 6