wine-bugs June 2025

wine-bugs@winehq.org

1 participants
611 discussions

[Bug 58363] New: Thief and Thief II crash in an unpredictable way when loading certain missions
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58363 Bug ID: 58363 Summary: Thief and Thief II crash in an unpredictable way when loading certain missions Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juliusr(a)proton.me Distribution: --- Created attachment 78761 --> http://bugs.winehq.org/attachment.cgi?id=78761 Backtrace for latest crash Ever since Wine 10.0 I've been experiencing various crashes when playing Thief Gold and Thief II, with the crashes themselves happening either upon a cutscene being played, or right after having finished it. The crashes seem to also be unpredictable; some cutscenes will play just fine with the mission loading afterwards, some will crash. As an example, I often experience a crash when loading the first mission in Thief Gold. Sometimes the cutscene plays but the game crashes after finishing it (or skipping it with ESC), sometimes the game crashes even before playing the cutscene. Some other times everything works out fine with the first mission, but I experience a crash when loading the second. Sometimes it helps to move the cutscene folder elsewhere. Movies no longer play but missions seem to load. Unfortunately, crashes end up happening anyway when loading other missions. Even more interestingly, sometimes I am able to play a mission that was crashing before by moving away the cutscene folder, load the mission, then move back the cutscene folder. The crash no longer happens afterwards. Still, this is no sure solution either - it works sometimes but it doesn't some other times. Crashes sometimes seem to be related to the game scripts. contained in script modules with the extension OSM. As an example, here are the last lines in the thief.log file after having experienced a crash: : Loaded script module "miss03.osm" [FileModDate=2018-Jul-03] : Loaded script module "script-t1.osm" [FileVer=2.1.0.0 ; ProductVer=2.1.0.0 ; FileModDate=2018-Jul-03] I'm also including the backtrace for a crash that occurred upon loading the second mission in Thief Gold, the crash having happened after having skipped the introductory cutscene. What I've described happens on a clean 32-bit Wine 10.10 prefix. Both games have been installed using the latest GOG installers. Though System Shock 2 runs on the same engine, I haven't experienced any crash there (thus far). -- 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 21

[Bug 58384] New: Sid Meier's Civilization III becomes unresponsive
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58384 Bug ID: 58384 Summary: Sid Meier's Civilization III becomes unresponsive Product: Wine Version: 10.10 Hardware: x86-64 URL: https://store.steampowered.com/app/3910/Sid_Meiers_Civ ilization_III_Complete/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 9a8047d729196120cc03e7b888951e0a211a6c8e Distribution: --- The game stops when the intro video is about to play. If I disable the intro video the game loads the main menu, menus are working but the game becomes unresponsive in a similar way when any of the available game modes are selected (New game, Quick game, Conquests! etc.) Nothing suspicious in the terminal output. This started happening after commit 9a8047d729196120cc03e7b888951e0a211a6c8e win32u: Use a pbuffer to implement GL on memory DCs. No such problem with the previous commit. To disable the intro video so you can get to the menus, insert PlayIntro=0 in the conquests.ini configuration file. wine-10.10-34-gaf5f7ce3ac9 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 575.57.08 -- 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 50577] New: Saya no Uta: hangs on RtlpWaitForCriticalSection
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

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 56517] New: osu!: Does not launch since 9.3
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=56517 Bug ID: 56517 Summary: osu!: Does not launch since 9.3 Product: Wine Version: 9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: kyuunex(a)protonmail.ch Distribution: --- Created attachment 76272 --> https://bugs.winehq.org/attachment.cgi?id=76272 log osu! does not launch since wine version 9.3. easy script to reproduce ========================== #!/bin/sh export OSU_INSTALL_LOCATION="$HOME/.local/share/osu-stable" export WINEPREFIX="$HOME/.local/share/wineprefixes/osu-stable" export WINEARCH=win32 if [ ! -d "$OSU_INSTALL_LOCATION" ] then mkdir -p "$OSU_INSTALL_LOCATION" wget -O "$OSU_INSTALL_LOCATION/osu!.exe" "https://m1.ppy.sh/r/osu!install.exe" fi if [ ! -d "$WINEPREFIX" ] then mkdir -p "$WINEPREFIX" winetricks -q --force dotnet40 fi cd "$OSU_INSTALL_LOCATION" wine "osu!.exe" "$@" ===================================== There is a workaround by installing `gdiplus` via winetricks, however, it was not nessasary to install this prior to 9.3. The bug is reproducable on the latest git commit as well as of the time of this report. -- 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 11

[Bug 56086] New: [9.0_rc regression] C&C Generals Zero Hour has graphic errors in menu
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=56086 Bug ID: 56086 Summary: [9.0_rc regression] C&C Generals Zero Hour has graphic errors in menu Product: Wine Version: 9.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: herrtimson(a)yahoo.de Distribution: --- Created attachment 75751 --> https://bugs.winehq.org/attachment.cgi?id=75751 exit box dialogue broken This was just fine with wine-8.0.2, when upgrading the prefix to 9.0_rc3 the Exit Box Dialogue is broken. I have a screenshot attached. -- 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 9

[Bug 58417] New: Failure to compile: Undeclared KW_ object
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58417 Bug ID: 58417 Summary: Failure to compile: Undeclared KW_ object Product: vkd3d Version: 1.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: johngodman006(a)gmail.com Distribution: --- Created attachment 78834 --> http://bugs.winehq.org/attachment.cgi?id=78834 Compilation log I am trying to compile wine in shared WoW64 mode, and ran into the attached error during compilation of the 64 bit binary. I have to imagine, given the compilation error is an undeclared identifier, that I am missing some headers. However, I'm not sure what exactly I am missing. I have packages spirv-headers-devel, vulkan-headers, and libvkd3d-devel installed at their latest versions from Fedora. For reference, I'm on Fedora 42 kernel 6.15.3. I must be making a simple mistake, right? If someone could give me a hand, I'd greatly appreciate 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.

1 2

[Bug 42796] New: X11DRV_ActivateKeyboardLayout spam during GTA5 run
by wine-bugs＠winehq.org 27 Jun '25

27 Jun '25

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 58264] New: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93"
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58264 Bug ID: 58264 Summary: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevu lkan/loader_thunks.c, line 93" Product: Wine Version: 10.7 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78605 --> http://bugs.winehq.org/attachment.cgi?id=78605 macOS Terminal log, wine-devel 10.8 running cpuz_x64.exe On macOS, there is a regression in multiple Windows programs since Wine-devel 10.7 (including 10.8) releases by Gcenx, with the final lines of the terminal output reading: > -[MTLHeapDescriptorInternal validateWithDevice:]:327: failed assertion `Heap Descriptor Validation > Placement heap type is not supported. > ' > 01a0:err:msvcrt:_wassert (L"!status && \"vkAllocateMemory\"",L"/Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c",93) > Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93 These programs work fine in Wine-devel 10.6 and lower tested with Wine-devel 10.7 and 10.8 binary releases from Gcenx (https://github.com/Gcenx/macOS_Wine_builds/releases) on macOS 11.7.10 tested with CPU-Z 2.15 (portable) (cpuz_x64.exe) download: https://download.cpuid.com/cpu-z/cpu-z_2.15-en.zip sha256: c8461d995d77a8fe1e8c5823403e88b04b733165cc151083b26379f1fe4b9501 -- 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 58415] New: Wine msiexec behaviour deviates from MS msiexec for tables missing from .msi
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58415 Bug ID: 58415 Summary: Wine msiexec behaviour deviates from MS msiexec for tables missing from .msi Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- While investigating a problematic .msi file, I noticed the following: The .msi file in its InstallExecuteSequence calls functions that depend on tables in the msi. However these tables do not exit. Examples found: "LaunchConditions", but no "LaunchCondition Table" "IsolateComponents", but no "IsolatedComponent Table" "PublishComponents/UnpublishComponents", but no "PublishComponent Table" "RegisterMIMEInfo/UnregisterMIMEInfo", but no "MIME table" "RegisterTypeLibraries/UnregisterTypeLibraries", but no "TypeLib table" "RegisterComPlus/UnregisterComPlus", but no "Complus table" When MS msiexec processes the .msi, it reports "Return value 0" in these cases. However when Wine msiexec does the same, it reports "Return value 1" instead. When modifying the .msi with the Orca MSI editor adding the missing tables (left empty), then MS msiexec reports "Return value 1", and Wine msiexec does the same. So there is a mismatch between the two implementations; I would conclude that Wine msiexec is missing a check for missing tables. Whether there are problems resulting from this difference in behaviour I cannot say, but it is at least not making investigations of .msi-issues any easier. -- 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 58419] New: Kubios Scientific needs PathMakeUniqueName to write to the output buffer.
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58419 Bug ID: 58419 Summary: Kubios Scientific needs PathMakeUniqueName to write to the output buffer. Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- When getting over bug #58418, the installer calls PathMakeUniqueName and uses the output buffer to put there some temporary files. Unfortunately this buffer stays uninitilized, so it creates "random" directories in current path. fixme:shell:PathMakeUniqueNameW 00007FFFFE1FF760 260 (null) L"tmp_install_dir" L"C:\\users\\benutzer\\AppData\\Local\\Temp\\" stub -- 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

← Newer
1
...
4
5
6
7
8
9
10
...
62
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs June 2025