- Wine-bugs - list.winehq.org

[Bug 58919] New: osu!stable freezes when running on winewayland
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58919 Bug ID: 58919 Summary: osu!stable freezes when running on winewayland Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: marshnelloosu(a)gmail.com Distribution: --- Playing a map in osu!stable (https://osu.ppy.sh/home/download) on latest winewayland causes the game to freeze (visually, audio still runs in the background). Bisected the breaking commit to be this: https://gitlab.winehq.org/wine/wine/-/commit/871a52cb8b2d9688dbc100284843aa… Reverting it does indeed make the game playable again. Tested on latest KDE Plasma 6.5 To reproduce: - `winetricks -q dotnet48 dotnet20 gdiplus_winxp` - Launch the game with `DISPLAY=` and wait a few seconds (20-30s) in the main menu - Set the game FPS to unlimited in settings - Play a beatmap, freeze should occur as soon as it's launched. If it does not occur on the game's first run, a second run should trigger the issue. -- 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 4

[Bug 57933] New: SAVIHost can take a long time to close, with it and wineserver eating the CPU
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57933 Bug ID: 57933 Summary: SAVIHost can take a long time to close, with it and wineserver eating the CPU Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- Starting from 1fa0d491a87f5c7d9f600ea95ee2bfc37ca6f940 in Wine 7.5, SAVIhost can take a long time to close, with it and wineserver then using the CPU a lot, causing me to have to terminate it manually. It seems the amount of time it can take depends on system, on my main machine I've had it take a minute sometimes, whereas my laptop (which is much slower) can somehow do so in up to about 10 seconds. This still happens on Wine 10.3, which just released. Downloads: https://www.hermannseib.com/programs/savihostx64.zip https://cdn.roland.com/assets/media/zip/scva_win_trial.zip Steps to reproduce: 1. Execute "winetricks mfc90" to get a required DLL 2. Extract scva_win_trial.zip and install the Roland Sound Canvas VA VST 3. Extract savihostx64.zip, and move savihost.exe to "C:\Program Files\Roland\Sound Canvas VA" 4. Rename savihost.exe to "Sound Canvas VA.exe" 5. Run the renamed executable 6. Go to Devices>MIDI, and set Input Port 1 to "Midi Through Port-0" 7. Close the program (I mentioned this in passing a few years ago in 52828 but never made it its own report, sorry) -- 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 2

[Bug 59118] New: 32-bit WINE does not work correctly with 32-bit device IDs and 64-bit inodes
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59118 Bug ID: 59118 Summary: 32-bit WINE does not work correctly with 32-bit device IDs and 64-bit inodes Product: Wine Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)list.winehq.org Reporter: e.j.bennett(a)swansea.ac.uk Distribution: --- Created attachment 79937 --> http://bugs.winehq.org/attachment.cgi?id=79937 Log showing command run, error, and location of correct directory When Wine starts, Wineserver uses the device and inode IDs of the `~/.wine` directory to name a temporary directory (`/tmp/.wine-${UID}/server-${DEVICE_ID_IN_HEX}-${INODE_ID_IN_HEX}`). A lock file and socket are created in this directory that the Wine client then (I presume) uses to communicate with Wineserver. When running on our HPC cluster with a Lustre filesystem, Wineserver creates this directory with a different name to the one that the client uses to look for it. Specifically, it is created with a 32-bit device ID and 64-bit inode ID, but read with a 16-bit device ID and 32-bit inode ID. The truncated device ID is simply the last 16 bits of the full 32-bit ID, but it is not clear to me how the truncated inode ID is related---the last 12 bits appear the same, but the remainder does not line up. The machine is running CentOS 7; as far as I know no official packages are available, and I'm not able to build 32-bit Wine due to a lack of a 32-bit toolchain, so I am running in an Apptainer container. To my knowledge this shouldn't affect the behaviour observed; running `stat ~/.wine` inside the container returns the same inode number as running it outside the container. -- 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 1

[Bug 59117] New: foobar 2000+Columns UI: Artwork cannot be displayed due to Direct2D features not being implemented in Wine
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59117 Bug ID: 59117 Summary: foobar 2000+Columns UI: Artwork cannot be displayed due to Direct2D features not being implemented in Wine Product: Wine Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: paregistrase(a)yahoo.es Distribution: --- With the current development version of columns_ui, artwork cannot be displayed in Wine. This is mainly due to the following Direct2D features not being implemented: · Colour management effect (a pass-through identity effect would at least get images rendering) https://learn.microsoft.com/en-gb/windows/win32/direct2d/color-management · ID2D1DeviceContext::GetImageLocalBounds for effects https://learn.microsoft.com/en-gb/windows/win32/api/d2d1_1/nf-d2d1_1-id2d1d… · ID2D1DeviceContext::DrawImage for effects https://learn.microsoft.com/en-gb/windows/win32/api/d2d1_1/nf-d2d1_1-id2d1d… Link to columns_ui post https://github.com/reupen/columns_ui/issues/1294#issue-3281142478 Acording to https://hydrogenaudio.org/index.php/topic,128859.msg1073914.html#msg1073914 "On ID2D1DeviceContext::GetImageLocalBounds() and ID2D1DeviceContext::DrawImage(), they are implemented in Wine for bitmaps but not effects. It's the effect part that's missing." foobar2000 https://www.foobar2000.org/windows columns_ui https://github.com/reupen/columns_ui If you’re logged into GitHub, you can download the latest development version by visiting the list of recent GitHub Actions builds, clicking on the most recent entry with a green tick, and then scrolling down to the links named ‘Component package (release, win32)’ and ‘Component package (release, x64)’ at the bottom. -- 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 58443] New: x11 'minimized' windows not re-fullscreening (fallout 3 / new vegas)
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58443 Bug ID: 58443 Summary: x11 'minimized' windows not re-fullscreening (fallout 3 / new vegas) Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- c67bfdbeba1860c891e53c64379f5e86d8e8b664 / https://gitlab.winehq.org/wine/wine/-/commit/c67bfdbeba1860c891e53c64379f5e… reading the title of the mr makes sense, however this completely breaks fullscreen for fallout 3 and new vegas, and im sure other older games as mentioned https://bugs.winehq.org/show_bug.cgi?id=58442 - there have been a lot of fullscreen/focus/window bugs so it's hard to tell what all is what i spent a bunch of time to just bisect so i'll have to look for what is going on tomorrow -- 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 42

[Bug 58505] New: Odd windows management behaviour in later dev versions
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58505 Bug ID: 58505 Summary: Odd windows management behaviour in later dev versions Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kg.hammarlund(a)gmail.com Distribution: --- I run a geneaology database program written for windows under wine. It runs fine on v10.0 (stable) and on dev versions up to 10.4. From v10.5 and upwards, including v1012, I'm encountering an odd issue. When opening a search window, this window opens in the background instead of on top of the main window. I then have to move or resize the main window in order to highilght the search window and fill in the search data. But this only happens the first time I open the search window. Next time it opens in the foreground. If I untick the box "Allow the window manager to control the windows" in winecfg > graphics, the search window opens expected. But this solution has its drawbacks. -- 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 59038] New: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception.
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59038 Bug ID: 59038 Summary: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception. Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: info(a)fernandolucas.info Distribution: --- Created attachment 79802 --> http://bugs.winehq.org/attachment.cgi?id=79802 wine console output I am using the new packages for Debian Wine 10.18 - 10.19 with the new wow64 mode. Installing .net 10 after initializing the prefix works well. Additional installations of a previous .net core version or running C:\Program Files\dotnet\dotnet.exe workload install wasm-tools fails with 0150:fixme:crypt:CertAddCertificateLinkToStore (00007FFFFED4B850, 00007FFFFE8A3DF8, 00000004, 0000000000000000): semi-stub Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception 0130:fixme:unwind:call_user_apc_dispatcher flags 0x3 are not supported. -- 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 4

[Bug 55915] New: Shader Compiler Issues
by WineHQ Bugzilla 10 Dec '25

10 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=55915 Bug ID: 55915 Summary: Shader Compiler Issues Product: Wine Version: 8.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Created attachment 75465 --> https://bugs.winehq.org/attachment.cgi?id=75465 Shader Compiler Errors Found When attempting to play StarCraft II using a custom map (StarCraft Mass Recall latest version to be precise), I noticed the attached in the log when starting. Nothing on either side of this trace seemed out of the ordinary. As a side note (don't know if it's related but I'll note it anyway), Map 5 of Loomings ("Extermination") does seem to have the same graphics crash previously reported when I build a Machine Shop off the Factory or try to attack the first base. -- 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 14

[Bug 44920] New: Starcraft II Arcade Crash during load
by wine-bugs＠winehq.org 10 Dec '25

10 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=44920 Bug ID: 44920 Summary: Starcraft II Arcade Crash during load Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: antonio.e.russo(a)gmail.com Distribution: --- Created attachment 61011 --> https://bugs.winehq.org/attachment.cgi?id=61011 WINEDEBUG=warn+all log of crash (gzipped) Starcraft II is a moving target. After the most recent patch, I was unable to use wine-staging 2.21, which had been working excellently for me. Wine 3.5 has trouble: loading the "Hero Attack 3X" (popular) arcade game, the game crashes. I've attached a "WINEDEBUG=warn+all" log, and can help debug. I checked "use 32-bit version", and I am using a clean prefix. -- 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.

3 25

[Bug 57770] New: Hearts of Iron IV requires 'WorldMatrix' identifier
by WineHQ Bugzilla 10 Dec '25

10 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57770 Bug ID: 57770 Summary: Hearts of Iron IV requires 'WorldMatrix' identifier Product: vkd3d Version: 1.14 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Using DX9 (legacy) 0384:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0384:err:d3dcompiler:D3DCompile2 Shader log: 0384:err:d3dcompiler:D3DCompile2 memory:433:47: E5005: Identifier "WorldMatrix" is not declared. 1.14-345-gf1412e42 -- 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