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

[Bug 50278] New: Diggles: The Myth of Fenris (GOG version) crashes on launch
by WineHQ Bugzilla June 27, 2025

June 27, 2025

https://bugs.winehq.org/show_bug.cgi?id=50278 Bug ID: 50278 Summary: Diggles: The Myth of Fenris (GOG version) crashes on launch Product: Wine-staging Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lcaffe(a)inbox.lv CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68826 --> https://bugs.winehq.org/attachment.cgi?id=68826 When runnning main executable 'Diggles.exe' Game Diggles: The Myth of Fenris https://www.gog.com/game/diggles_the_myth_of_fenris Crashes on startup (log attached), the screen becomes black for a second or two. -- 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 8

[Bug 50577] New: Saya no Uta: hangs on RtlpWaitForCriticalSection
by WineHQ Bugzilla June 27, 2025

June 27, 2025

https://bugs.winehq.org/show_bug.cgi?id=50577 Bug ID: 50577 Summary: Saya no Uta: hangs on RtlpWaitForCriticalSection Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: pernegger(a)gmail.com Distribution: --- Created attachment 69251 --> https://bugs.winehq.org/attachment.cgi?id=69251 terminal output at default settings Note: This is about the Japanese "Windows 10 compatible" release, not an English localised one. There is no demo version, I'm afraid. The game runs fine--until it hangs at: 012c:err:ntdll:RtlpWaitForCriticalSection section 103971A4 "?" wait timed out in thread 012c, blocked by 0024, retrying (60 sec) The hang may happen, after as little as 1 min, sometimes it's 10 min, and I might have made it 20 min once. When it happens, it does not recover, the message just repeats every once in a while. I'm using the Ubuntu packages from the official winehq repo. Originally I tried with wine-staging 6.0, then I went backwards version by version through (wine-staging) 5.18, and finally now I'm on (wine-devel) 6.0 for this bug report. No discernable difference either way. The run in the attached log happened in a clean prefix (though I admit I may have forgotten to wipe the prefix between some downgrades). -- 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 42796] New: X11DRV_ActivateKeyboardLayout spam during GTA5 run
by wine-bugs＠winehq.org June 27, 2025

June 27, 2025

https://bugs.winehq.org/show_bug.cgi?id=42796 Bug ID: 42796 Summary: X11DRV_ActivateKeyboardLayout spam during GTA5 run Product: Wine Version: 2.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: winetest(a)luukku.com Distribution: --- I just tested wine-staging 2.5 against GTA5. And I get my console spammed annoying amount of These 3 lines group of 3. fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4090409, 40000000: semi-stub! fixme:keyboard:X11DRV_ActivateKeyboardLayout flags 40000000 not supported fixme:dxgi:dxgi_swapchain_Present Unimplemented flags 0x1 The keyboard spam comes from here https://source.winehq.org/git/wine.git/blob/61a1a266faa9fa7c959136b0ab0b5d7… Maybe priting the message few times and putting rest of the spam into TRACE? Since bug 42017 got fixed the output is much cleaner now. This is just enchanment request to get better looking logs by default. -- 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 47985] New: SysListView32 header are not rendered
by WineHQ Bugzilla June 27, 2025

June 27, 2025

https://bugs.winehq.org/show_bug.cgi?id=47985 Bug ID: 47985 Summary: SysListView32 header are not rendered Product: Wine Version: 4.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: bitter.taste(a)gmx.com Distribution: --- This problem can be noticed if one tries to use LTSpice [1], places a Capacitor in the schematic, right clicks on it and then on "Select Capacitor". The window that opens has a blank space where the header is supposed to be, resizing the windows makes the header appear and clicking on the headers themselves makes them appear for a brief instant. [1] https://www.analog.com/en/design-center/design-tools-and-calculators/ltspic… -- 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 38889] New: Microsoft Orca unable to create transform file
by wine-bugs＠winehq.org June 27, 2025

June 27, 2025

https://bugs.winehq.org/show_bug.cgi?id=38889 Bug ID: 38889 Summary: Microsoft Orca unable to create transform file Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: crosstieger(a)gmail.com Distribution: --- Created attachment 51827 --> https://bugs.winehq.org/attachment.cgi?id=51827 terminal output of the error Microsoft Orca is unable to modify cells within an .msi file. Modifying a cell returns the following error message: Could not change this cell to '<Value>'. The data was rejected by the database. It may be out of the valid range or formatted incorrectly. In the terminal you can see the error message: fixme:msidb:TABLE_modify 0x7a5098 4 0x7a5e40 - mode not implemented The value 0x7a5098 and 0x7a5e40 changes depending on the cell you edit. If you click on 'Transform - Generate Transform' and want to save your .MST file, it returns the error: Orca was unable to generate the transform. (MSI Error 120) On the terminal: fixme:msi:MsiDatabaseGenerateTransformW 3 2 L"Z:\\home\\techniktriberg\\Downloads\Untitled.mst" 0 0 The path depends on where you want to save the file. Full terminal output as an attachment. ---- Installation process ---- run: winetricks dotnet40 run: winetricks mfc42 run: msiexec -i Orca.Msi -- 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 51064] New: Crash from Starcraft 2 game in Direct Strike mode
by WineHQ Bugzilla June 26, 2025

June 26, 2025

https://bugs.winehq.org/show_bug.cgi?id=51064 Bug ID: 51064 Summary: Crash from Starcraft 2 game in Direct Strike mode Product: Wine-staging Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: terapy-session(a)bk.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 69922 --> https://bugs.winehq.org/attachment.cgi?id=69922 screen The bug is manifested for a long time. 100% repeatability. Through Proton no problem. The problem is only in this mode. -- 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 48283] New: Pegasus Mail 4.73 crashes after install
by WineHQ Bugzilla June 25, 2025

June 25, 2025

https://bugs.winehq.org/show_bug.cgi?id=48283 Bug ID: 48283 Summary: Pegasus Mail 4.73 crashes after install Product: Wine Version: 4.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: daveypy(a)outlook.com Distribution: --- Created attachment 65965 --> https://bugs.winehq.org/attachment.cgi?id=65965 Saved backtrace from crash After installing Pegasus Mail in Wine, Pegasus Mail crashes upon launch. I would be willing to test this in Wine STAGING, but I don't know how to install STAGING alongside STABLE in Ubuntu. -- 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 44236] New: Poisson Superfish: Slow to write binary file.
by wine-bugs＠winehq.org June 23, 2025

June 23, 2025

https://bugs.winehq.org/show_bug.cgi?id=44236 Bug ID: 44236 Summary: Poisson Superfish: Slow to write binary file. Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: raphaelcervantes(a)protonmail.com Distribution: --- Discussion is in this forum. https://forum.winehq.org/viewtopic.php?f=2&t=29936 I am using Wine to run Poisson Superfish. This program essentially does some calculations and then writes the results into a binary file. This action is performed in less than a second in a Windows environment. Unfortunately, it takes about 10 seconds to write this binary file under Wine. Here is how to reproduce the error: 1. Install Poisson Superfish on linux using Wine. You have to scroll all the way down and click register. http://laacg.lanl.gov/laacg/services/download_sf.phtml 2. Once installed, open a unix terminal in this directory .../.wine/drive_c/LANL/Examples/RadioFrequency/Waveguides/ 3. Run wineconsole cmd. 4. In the new window, run RUNWG.BAT. 3. Several windows will pop up. The ones that stall for a bit are in the process of writing to a file named something.T35. The T35 refers to tape 35 (I guess that's how a sector of harddrive memory would be referred as back in the 80s). This is the binary file with the solution in it. It will finish eventually, but it is pretty slow. -- 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 8

[Bug 52646] New: Trying to run wit (Wimms Iso Tools) , it works, its just when I start the iso extraction it gives me this error.
by WineHQ Bugzilla June 23, 2025

June 23, 2025

https://bugs.winehq.org/show_bug.cgi?id=52646 Bug ID: 52646 Summary: Trying to run wit (Wimms Iso Tools) , it works, its just when I start the iso extraction it gives me this error. Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: madeinclt26(a)gmail.com Distribution: --- Created attachment 71966 --> https://bugs.winehq.org/attachment.cgi?id=71966 After it starts extracting the iso it says " The program wit.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. After it starts extracting the iso it says " The program wit.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. -- 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 54975] New: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization
by WineHQ Bugzilla June 23, 2025

June 23, 2025

https://bugs.winehq.org/show_bug.cgi?id=54975 Bug ID: 54975 Summary: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- win32u:win32u exits prematurely, leaves child process behind: win32u:win32u start dlls/win32u/tests/win32u.c [...] win32u.c:1037: Test marked todo: res = 4 win32u.c:1040: Test marked todo: buf[1] = 0 win32u:win32u:09f0 done (0) in 0s 1295B win32u.c:1045: Test failed: res = 0 win32u.c:1046: Test failed: buf = d win32u.c:1049: Test failed: res = 0 win32u.c:1059: Test failed: res = 0 09e0:win32u: 14 tests executed (2 marked as todo, 0 as flaky, 4 failures), 0 skipped. See https://test.winehq.org/data/patterns.html#win32u:win32u There are two things to notice in the above log: * The main win32u:win32u process is 09e0 but it did not issue a 'tests executed' summary. This means it exited prematurely. * 09e0 is a child process that continues running and printing messages which interferes with the next test, specifically windows.globalization:globalization. Also on the TestBot one can find the corresponding Wine log which contains these lines that seem strongly correlated to this issue: 0480:err:seh:KiUserCallbackDispatcher ignoring exception 0480:err:seh:KiUserCallbackDispatcher ignoring exception wine client error:480: partial write 57344 Running: win32u:win32u (694 of 774) Running tests - 6 failures This issue only happens on Linux and happens systematically but only on three configurations: fg-deb64-t32 but not for the wow32 and wow64 builds on the same machine fgtb-debian11-wow64 but not for the wow32 build on the same machine debian11b-wow64 but but not for the wow32 build on the same machine (and none of the 32-bit builds on debian11 is impacted) And I have been unable to reproduce this failure on my machine (fg-deb64-t32). So it's unclear what causes this failure but it clearly started on 2023-05-15 so it's probably some commit on that day. -- 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 8