April 2025 - Wine-Bugs - list.winehq.org

[Bug 58044] New: Realm Grinder freezes/crashes after a very long run
by WineHQ Bugzilla May 15, 2025

May 15, 2025

https://bugs.winehq.org/show_bug.cgi?id=58044 Bug ID: 58044 Summary: Realm Grinder freezes/crashes after a very long run Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 78299 --> https://bugs.winehq.org/attachment.cgi?id=78299 output of two failed runs This I strongly suspect is a regression, yet I can't really pin down the time when this started happening. The problem happens with little to no human interaction, yet the timeframes make it unreasonable to actively reproduce. I suspect it started around 10.0 release, but with a -/+ 2 months margin (so close to useless). Anyway, what's the problem ? If Realm Grinder is run for long enough (but 'long enough' here is measured in *days*), it tends to eventually either freeze with a completely black window or crash with an X server error. The attachment has output of two such runs, second chunk is when it just froze, the first when it crashed. 'fixme:d3d:swapchain_blit_gdi Using GDI present.' at the end of both seems to be the moment the problem triggers. It seems to be some kind of a resource leak, but it doesn't affect any other apps running besides it, not even those run by wine. No user action is really required to trigger this - I've seen it freeze after a desktop switch, I've seen it crash when the window was just displayed, but not really interacted with. (Realm Grinder here is still at v4.2.27.0, though I'll likely update it shortly for Easter event) -- 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 2

[Bug 42898] New: Listbox keyboard input
by wine-bugs＠winehq.org May 15, 2025

May 15, 2025

https://bugs.winehq.org/show_bug.cgi?id=42898 Bug ID: 42898 Summary: Listbox keyboard input Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janwinehq(a)gmail.com Distribution: --- A listbox widget in Wine does not react the same way to keyboard input as in Windows. In Windows, you can type the first characters of a word and the cursor will jump to the first item matching *all* the characters you typed. This allows you to drill down quickly to the item you want. In Wine, when you start typing it only considers the *last* character you typed when looking for a match. On listboxes where you have lots of items starting with the same character, this can make it problematic to drill down to the correct item. This may be better explained with a simple example. Suppose you have a listbox with the following items, sorted alphabetically: * AMBER * BLUE * BROWN * GREEN * ORANGE * RED * YELLOW Windows behavior: * if you type "B", it will drill down to "BLUE" * if you type "BR", it will drill down to "BROWN" * if you type "BRO", it will drill down to "BROWN" Wine behavior: * if you type "B", it will drill down to "BLUE" * if you type "BR", it will drill down to "RED" * if you type "BRO", it will drill down to "ORANGE" -- 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 58180] New: CaptureAge 1.17.1: fails to GetSharedHandle
by WineHQ Bugzilla May 15, 2025

May 15, 2025

http://bugs.winehq.org/show_bug.cgi?id=58180 Bug ID: 58180 Summary: CaptureAge 1.17.1: fails to GetSharedHandle Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eabesea(a)rambler.ru Distribution: Ubuntu Created attachment 78475 --> http://bugs.winehq.org/attachment.cgi?id=78475 captureage log When I run CaptureAge, it fails to start rendering. It appears that the fail is because dxgi_resource_GetSharedHandle is not implemented. I'm not attaching full wine terminal output since it's very large and appears to be mostly irrelevant. -- 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 58164] New: WINTAB32.dll: When the pen is pressed against the board, pkStatus is given TPS_QUEUE_ERR after a second or two and Queue overflows.
by WineHQ Bugzilla May 15, 2025

May 15, 2025

http://bugs.winehq.org/show_bug.cgi?id=58164 Bug ID: 58164 Summary: WINTAB32.dll: When the pen is pressed against the board, pkStatus is given TPS_QUEUE_ERR after a second or two and Queue overflows. Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wintab32 Assignee: wine-bugs(a)winehq.org Reporter: axis6404(a)proton.me Distribution: --- When the pen is pressed against the board, pkStatus is given TPS_QUEUE_ERR after a second or two and Queue overflows. After the queue overflows, no signal is sent. (After raising the pen again, until it is pressed against the board again) Cannot draw anything or the line thickness is messed up. https://github.com/wine-mirror/wine/blob/f7503d0a996ae1243dd6c87b39a9143624… Macromedia Flash MX X11 Section "InputClass" Identifier "Tablet" Driver "wacom" MatchDevicePath "/dev/input/event*" MatchUSBID "28bd:0905" Option "Suppress" "0" Option "Threshold" "1" Option "RawSample" "1" EndSection -- 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 58162] New: GetPrivateProfileIntA/W and WritePrivateProfileStringA/W does not detour properly.
by WineHQ Bugzilla May 15, 2025

May 15, 2025

http://bugs.winehq.org/show_bug.cgi?id=58162 Bug ID: 58162 Summary: GetPrivateProfileIntA/W and WritePrivateProfileStringA/W does not detour properly. Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Created attachment 78443 --> http://bugs.winehq.org/attachment.cgi?id=78443 sone_patch's debug log under Windows 10. When trying to detour a Recettear - An Item Shop's Tale's custom.exe using https://gitlab.com/redpolline/sone_patch, all attempts to update the game's config ini file fail under Wine, but work under Windows. The game's custom.exe uses the GetPrivateProfileIntA() and WritePrivateProfileStringA() functions to access the game's ini file instead of calling CreateFileA(), ReadFile(), and WriteFile() directly. I assume that the cause is Wine possibly having GetFullPathNameW() as a statically linked symbol within the context of GetPrivateProfileIntA() and WritePrivateProfileStringA(). (As all three of them are exported by kernel32.dll, and therefore the compiler would not need to search for the symbol at build time.) But I could be wrong here. What matters is that when sone_patch detours GetFullPathNameA/W(), GetPrivateProfileIntA() and WritePrivateProfileStringA() should be affected by that detour without being detoured themselves. A good way to see this is by using sone_patch's debug build, as it logs when a detoured function is hit, along with the given arguments. Under Windows 10, multiple calls to GetFullPathNameA/W() are seen in the log. (But no CreateFileA/W() for the ini file.) Under Wine, no calls are logged at all for the ini file. The only call to GetFullPathNameW() seen under Wine is for C:\windows\resources\themes\light\light.msstyles. Which isn't present under the Windows log, so that one is Wine specific.) As a result, the game's button config and display settings cannot be altered by the game's custom.exe. As it gets the original (developer intended) file which is read-only (and owned by another user) on my system. Which sone_patch is supposed to workaround through the detouring of GetFullPathNameA/W() to point custom.exe to an accessible file elsewhere. -- 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

[Bug 57672] New: Knights of the Old Republic II - Rendering issues and crashes when using new WoW64 mode
by WineHQ Bugzilla May 15, 2025

May 15, 2025

https://bugs.winehq.org/show_bug.cgi?id=57672 Bug ID: 57672 Summary: Knights of the Old Republic II - Rendering issues and crashes when using new WoW64 mode Product: Wine Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: info(a)fdossena.com Distribution: --- Created attachment 77849 --> https://bugs.winehq.org/attachment.cgi?id=77849 Screenshot of how the game looks with the new WoW64 mode I'm testing the "classic" version of KOTOR 2 (not the 2015 remaster from steam) and I noticed a strange behavior. When building Wine using the new WoW64 mode, the game has visual artifacts in the character creation screen, and freezes when trying to start a new game. When building Wine with the old WoW64, the game works correctly. The first game, based on the same engine, works correctly with both versions of WoW64. Tested on: * Arch Linux x86_64, Kernel 6.12 * AMD Radeon RX6900XT with Mesa 24.3.3 * KDE Plasma on Wayland (wine is running with the x11 backend) I'm attaching screenshots of Wine 10.0-rc5. Logs don't show anything out of the ordinary or different between the two builds. -- 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 37088] New: SmartBarXP hangs on exit
by wine-bugs＠winehq.org May 14, 2025

May 14, 2025

https://bugs.winehq.org/show_bug.cgi?id=37088 Bug ID: 37088 Summary: SmartBarXP hangs on exit Product: Wine Version: 1.7.24 Hardware: x86 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 49298 --> https://bugs.winehq.org/attachment.cgi?id=49298 terminal output Noticed while checking bug 8018. Closing the application (either via Option, Exit or clicking the X) results in a hang. There's a seh exception thrown, as well. -- 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 7

[Bug 27117] New: Quake III Arena demo installer spawns Wine File when setting up Start menu items
by wine-bugs＠winehq.org May 2, 2025

May 2, 2025

http://bugs.winehq.org/show_bug.cgi?id=27117 Summary: Quake III Arena demo installer spawns Wine File when setting up Start menu items Product: Wine Version: 1.3.19 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tjwt(a)hush.ai The demo is downloadable from ftp://ftp.idsoftware.com/idstuff/quake3/win32/Q3ADemo.exe . During a default installation in Wine, it creates ten files in C:\users\Public\Start Menu\ and ten Wine File windows appear. No Windows Explorer windows open when installing under Windows XP. I see the problem with Wine 1.3.18 and 1.3.19 (I did not try earlier versions). -- 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 23978] New: keyboard seems to be dead after changing to another field with TAB-key
by wine-bugs＠winehq.org April 29, 2025

April 29, 2025

http://bugs.winehq.org/show_bug.cgi?id=23978 Summary: keyboard seems to be dead after changing to another field with TAB-key Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lorenz.giefing(a)utanet.at Created an attachment (id=30111) --> (http://bugs.winehq.org/attachment.cgi?id=30111) WINDEBUG=+all FileMaker Pro 5 If I change to another form-field using the TAB-key, the keyboard is dead, no reaction at all. Mouse acts normal, I can use the menus and copy/paste text anyway. Clicking out of the window and into again (getting focus again) and the keyboard is alive again. There seems to be a pattern depending on the field, some trigger the problem each time I leave them with TAB, some never do. After reading a lot of bug reports, I tried "virtual desktop" on/off, "allow window manager" on/off, no changes at all. I tried [HKCU\software\Wine\X11 Driver] UseTakeFocus="yes" without changes. Ubuntu 10.04 Keyboard and mouse via PS2 No SCIM installed. -- 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 33

[Bug 50828] New: CompressonatorGUI 4.1 installer crashes (Advanced Installer)
by WineHQ Bugzilla April 29, 2025

April 29, 2025

https://bugs.winehq.org/show_bug.cgi?id=50828 Bug ID: 50828 Summary: CompressonatorGUI 4.1 installer crashes (Advanced Installer) Product: Wine Version: 6.4 Hardware: x86-64 URL: https://github.com/GPUOpen-Tools/Compressonator/releas es/tag/V4.1.5083 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: the.ideals(a)gmail.com Distribution: --- After selecting or deselecting prerequisites during setup, the setup crashes. [SEH_AV_READ_BADPTR] ACCESS_VIOLATION (0xc0000005) at address [0x00424f72] Advanced Installer Enhanced UI 13.5 build 74683 *** Stack Trace (x86) *** [0x00424f72] EntryPoint() [0x00424ae6] EntryPoint() [0x00400000] MODULE_BASE_ADDRESS sha1sum CompressonatorGUI_x64_4.1.5083.exe cb0c6f9bcaf7d2c93287ddeb90e72efa771b19fe CompressonatorGUI_x64_4.1.5083.exe du -sh CompressonatorGUI_x64_4.1.5083.exe 33M CompressonatorGUI_x64_4.1.5083.exe -- 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