- Wine-bugs - list.winehq.org

[Bug 59122] New: ashampoo burning studio 27
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59122 Bug ID: 59122 Summary: ashampoo burning studio 27 Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: lars_martin4(a)hotmail.com Distribution: --- Created attachment 79946 --> http://bugs.winehq.org/attachment.cgi?id=79946 image poor grapic will not boot -- 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 59013] New: Final Fantasy XI Online: Noticeable overall performance regression.
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59013 Bug ID: 59013 Summary: Final Fantasy XI Online: Noticeable overall performance regression. Product: Wine Version: 10.6 Hardware: x86-64 URL: http://www.playonline.com/ff11eu/download/media/benchm ark03.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: 93bfdc6f21a1b1be092b7a7b8e5b1dad0aff8a46 Distribution: Gentoo Not sure if this is regression per se, but it looks like after 93bfdc6f21a [1], at least some applications suffer from lower performance. For example in certain situations in Final Fantasy XI Online, FPS may drop by ~12 or more from the maximum of ~29. At 11390796260 [2], or possibly already starting/related at/to ac8591ee3d2 [3], the commit before that, FPS in the same testing method can be seen dropping by ~5 at most, so that might add some to it. Before that point, the FPS count would more or less stay around the maximum ~29 (I don't think I've ever seen the Wine debug 'fps' hit 30, which is the maximum, but I'm not sure if it really hits it on Windows either), with a CPU use on the executable at around 170-180% (two threads). After [1], CPU usage will be at the maximum of two threads for the process, and my CPU fans start working a bit harder on the Ryzen 9 7950X too. Graphics stack consists of the open amdgpu driver and a Radeon RX 5700 XT. Unsurprisingly perhaps, these drops can be observed using the related, Final Fantasy XI Online Benchmark as well. At 9.0.1 or 9.0 and up for some ways, the benchmark will give me a score over 12000, but after these two points in commits, it will give around 10000. The first, slight drop happens at around 9.3, but it is much less noticeable, and I didn't bisect that fully yet. As a sidey-note, I also saw ~8000 points when not using GCC optimisations (normally -O2), and ~6000 if additionally running it with wow64-new, but that's a tale for another time. Thank you! 1. https://gitlab.winehq.org/wine/wine/-/commit/93bfdc6f21a1b1be092b7a7b8e5b1d… 2. https://gitlab.winehq.org/wine/wine/-/commit/11390796260f8fb54b19024f109384… 3. https://gitlab.winehq.org/wine/wine/-/commit/ac8591ee3d25c0545c6a67d260e0c7… -- 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 58167] New: Pegasus Mail immediately restores window
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58167 Bug ID: 58167 Summary: Pegasus Mail immediately restores window 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: winehq(a)jonass.user.lysator.liu.se Distribution: --- After upgrading from 10.5 to 10.6 I can't minimize Pegasus Mail. When I click minimize the window only flashes, seems like it minimizes but immediately restores to open window with the same size as before. No error messages in console. git bisect suggests it may be related to commit 6b04bdf25796c9c76815588bf7bdc36ff44b9e13 OS: XUbuntu 24.04.2 LTS NVIDIA Driver Version: 535.183.01 Using X11 (not Wayland) -- 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 30

[Bug 59121] New: iexplore 11 hangs on x86_64
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59121 Bug ID: 59121 Summary: iexplore 11 hangs on x86_64 Product: Wine Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)list.winehq.org Reporter: crinteanu.cristian(a)gmail.com Distribution: --- Created attachment 79944 --> http://bugs.winehq.org/attachment.cgi?id=79944 backtrace of wine10 x86_64 iexplore, shipped by wine package, will miserably hang with "Unhandled exception: inexact float result in 64-bit" if wine is build WITHOUT mingw on its back. Tested on two distros (i'm from PCLinuxOS) with same bad results. The hang occurs only on x86_64 build of iexplore (wine64). The 32 bit one works fine. The bug also confirmed on stable 10.0 through 11.0-rc1... Any ideea what is happening ? Thx ! -- 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 59120] New: xactengine3_7:xact3 is crashing since 2025-11-19 with debian 12 and older.
by WineHQ Bugzilla 11 Dec '25

11 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59120 Bug ID: 59120 Summary: xactengine3_7:xact3 is crashing since 2025-11-19 with debian 12 and older. Product: Wine Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 79943 --> http://bugs.winehq.org/attachment.cgi?id=79943 backtrace and possible patch I could reproduce it inside a debian 12 bookworm VM by stopping pulseaudio: systemctl --user stop pulseaudio.service pulseaudio.socket The crash happens because winealsa.drv tries a `snd_pcm_open` with of device "plughw:0,0", which fails with -16 / -EBUSY. There is a `FAudio_assert` in `FAudio_PlatformGetDeviceDetails`, but it gets compiled out because faudio gets compiled with NDEBUG. The test `test_renderer_details` got added in commit 61963006e0, does this justify to mark this as regression? Attached file contains the backtrace of the snd_pcm_open and the crash. And an early return if alsa_get_mix_format fails. Test pattern page: https://test.winehq.org/data/patterns.html#xactengine3_7:xact3 Testbot run showing the crash: https://testbot.winehq.org/JobDetails.pl?Key=161257 Testbot run with the patch from attached file: https://testbot.winehq.org/JobDetails.pl?Key=161258 -- 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 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