January 2026 - Wine-bugs - list.winehq.org

[Bug 59340] New: Win32 streams support (filename:streamname:$DATA)
by WineHQ Bugzilla 02 Feb '26

02 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=59340 Bug ID: 59340 Summary: Win32 streams support (filename:streamname:$DATA) Product: Wine Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)list.winehq.org Reporter: dan.f.shelton(a)gmail.com We need Win32 streams support (filename:streamname:$DATA) in Wine to support those applications which use them (i.e. INDB, MS SQL, SIEMENS PLC simulators, BOSCH/REXROTH PLC, ... software). -- 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 59138] New: Timelapse export failing in Clip Studio Paint
by bugs＠winehq.org 02 Feb '26

02 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=59138 Bug ID: 59138 Summary: Timelapse export failing in Clip Studio Paint Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: risto.lehtela(a)gmail.com Distribution: --- I was able to get CSP v4 working to an acceptable degree using the tutorial here but i stumbled into a bug. When recording a timelapse in CSP the export fails. As far as i know the app records the process to the .csp file just fine as i was able to export the timelapse on Windows but when hitting File-->Timelapse-->Export timelapse and configuring the export i get a "Failed to export timelapse" message. This happens on all version of CSP not just v4. I feel this might be a dependency problem like FFMPEG as Krita uses that to export timelapses but i'm not sure if CSP does. Thanks in advance for any help! -- 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 5

[Bug 59338] New: Menus fail to display after closing child dialog in DAZ Studio 4.24.0.4 (Qt popup recreated but not mapped/shown)
by WineHQ Bugzilla 01 Feb '26

01 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=59338 Bug ID: 59338 Summary: Menus fail to display after closing child dialog in DAZ Studio 4.24.0.4 (Qt popup recreated but not mapped/shown) Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: korb(a)qisc.com Distribution: --- Created attachment 80276 --> http://bugs.winehq.org/attachment.cgi?id=80276 Log as detailed in description I was running WINE 11.0-rc4 prior to this week, and it was working fine. The issue started when I updated to 11.0 (I skipped rc5). Steps to reproduce in clean prefix (wineboot --init, no overrides, no env vars): 1. Install base DAZ Studio 4.24.0.4 (no content needed). 2. Launch DAZ. 3. Window → Workspace → Select Layout... → Cancel 4. Try to open Window menu again → menu does not appear (click has no effect). Log (+err,+warn,+qt,+focus,+menu,+popup) shows: - First menu open: system popup created (e.g., 0x10262/0x10264), all standard items inserted (&Restore, &Move, etc.), NtUserThunkedMenuInfo applied, default set, get_menu_state checks. - Dialog close: NtUserDestroyMenu destroys popup handles. - Second (and third) menu attempt: identical creation cycle (new handle, items inserted again, etc.). - But no MapNotify/Expose/visibility events for the second popup — menu never appears on screen. Setup: - Wine: wine-11.1 (apt install --install-recommends winehq-devel) - OS: Linux Mint 21.3 Cinnamon X11 w/ all latest updates applied - GPU: NVIDIA 590.48.01 driver - App: DAZ Studio 4.24.0.4 base install Tested: - Compositing off - Virtual desktop on/off - Qt env vars (QT_X11_NO_MITSHM=1, QT_AUTO_SCREEN_SCALE_FACTOR=0) - Windows version change (10 -> 7) - Focus mode switch (from sloppy to click and back) - No DLL overrides or custom env vars in clean prefix I then ran my test again with WINEDEBUG='+err,+warn,+qt,+focus,+menu,+popup' to produce the attached log. I interjected comments into the log to indicate where I took the actions described above. My comments are on lines that start with "***". -- 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 58043] New: DVDFab won't run on Wine 10.3 because it thinks that there is a debugger running when there isn't
by WineHQ Bugzilla 01 Feb '26

01 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=58043 Bug ID: 58043 Summary: DVDFab won't run on Wine 10.3 because it thinks that there is a debugger running when there isn't Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 78297 --> https://bugs.winehq.org/attachment.cgi?id=78297 Screenshot To reproduce, run `wine dvdfab13_online_13037.exe`. When installation is complete, an error dialog appears that says "A debugger has been found running in your system. Please, unload it from memory and restart your program." This error did not happen before Wine 10.3. `git bisect` says: dc718fd33b23a6104a0fa2e971a358662bf766af is the first bad commit commit dc718fd33b23a6104a0fa2e971a358662bf766af (HEAD) Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Tue Feb 25 13:45:33 2025 +0100 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Tue Feb 25 23:01:11 2025 +0100 ntdll: Add some missing Zw exports. dlls/ntdll/ntdll.spec | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) $ sha256sum dvdfab13_online_13037.exe 9260ecbad0ddeeca876ff7adb35d26cffc7fb40399c814ae6fd369d2d7708791 -- 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 59347] New: winetest.exe should have tests for Win32 streams (filename:streamname:$DATA)
by WineHQ Bugzilla 31 Jan '26

31 Jan '26

http://bugs.winehq.org/show_bug.cgi?id=59347 Bug ID: 59347 Summary: winetest.exe should have tests for Win32 streams (filename:streamname:$DATA) Product: Wine Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: testcases Assignee: wine-bugs(a)list.winehq.org Reporter: dan.f.shelton(a)gmail.com winetest.exe should have tests for Win32 streams (filename:streamname:$DATA). Tests should include: - create a non-sparse Win32 stream (filename:streamname:$DATA) - create a sparse Win32 stream (filename:streamname:$DATA) by calling FSCTL_SET_SPARSE - delete a Win32 stream - rename a Win32 stream to another name in the same file, e.g. "filename:streamname:$DATA" to "filename:streamname_newname:$DATA". NTFS allows this by setting the destination filename in FileRenameInformation to ":streamname_newname:$DATA" -- 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 59286] New: Wine crashes while running PhotoImpact (iedit.exe)
by WineHQ Bugzilla 31 Jan '26

31 Jan '26

http://bugs.winehq.org/show_bug.cgi?id=59286 Bug ID: 59286 Summary: Wine crashes while running PhotoImpact (iedit.exe) Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: cjmh.gt(a)gmail.com Distribution: --- Created attachment 80216 --> http://bugs.winehq.org/attachment.cgi?id=80216 Crash Dump from Wine PhotoImpact is a very old windows program from the 1990s. It installs on Windows and Wine with the exe header flag indicating it can use more the 2GB of memory. In Windows this can cause the program to declare it is out of memory on occasion. Under Wine this "out of memory' happens frequently. When that happens it is fatal in that any attempt to save the work or exit the program fails wit hthe "out of memory" error. I mention this because I modified the iedit.exe as follows: I flipped the File Header bit on iedit.exe to limit it 2GB. That seemed to solve the out of memory issue on both Windows and Wine. However, it occasionally crashes under Wine. I have attach the crash dump. -- 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 59249] New: I keep getting this issue whenever I try to run clip studio paint v3 and I'm not too sure what to do about it.
by WineHQ Bugzilla 31 Jan '26

31 Jan '26

http://bugs.winehq.org/show_bug.cgi?id=59249 Bug ID: 59249 Summary: I keep getting this issue whenever I try to run clip studio paint v3 and I'm not too sure what to do about it. Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: skcunanan10(a)gmail.com Distribution: --- Created attachment 80165 --> http://bugs.winehq.org/attachment.cgi?id=80165 the backtrace from the program error. Whenever I try to run clip studio paint v3, it starts off relatively normal. It asks me to select whether I want to run EX or PRO. I select EX since that's what I want to run. Then I get a program error that says "The program CLIPStudioPaint.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience." I'm not quite sure what to do about this or how to get it running. -- 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 53619] New: World of Warcraft Shadowlands randomly crashes
by WineHQ Bugzilla 31 Jan '26

31 Jan '26

https://bugs.winehq.org/show_bug.cgi?id=53619 Bug ID: 53619 Summary: World of Warcraft Shadowlands randomly crashes Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cianuro2036(a)protonmail.com Distribution: --- This is something that has happened on multiple hardware, platforms and OS distros. This is also something that has been happening for a while, I just decided to report it because It can affect some parts of the game, such as rated PVP. The particular error logs as follows: 05f4:err:seh:dispatch_exception unknown exception (code=c0000420) raised wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. How to reproduce: This feels 'random' but makes me _think_ it could be a memory leak issue. If you're in highly populated areas _or_ highly demanding zones, it can trigger itself. Two recent scenarios I can recall - First, doing multiple arena matches and waiting for the queue in Oribos. The crash happened specifically during arena. - Second, doing the Ashran Brawl Battleground. This battleground is very, very long and has a lot of people around. In both scenarios there is a slowdown in FPS in both areas. -- 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 54925] New: World of Warcraft WotLK Classic crashes on receiving inputs very frequently
by WineHQ Bugzilla 31 Jan '26

31 Jan '26

https://bugs.winehq.org/show_bug.cgi?id=54925 Bug ID: 54925 Summary: World of Warcraft WotLK Classic crashes on receiving inputs very frequently Product: Wine Version: 8.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chagatai(a)bitigchi.xyz Distribution: --- Created attachment 74446 --> https://bugs.winehq.org/attachment.cgi?id=74446 wine debug log After logging in and selecting a character the game seems to run as normal without issues. If I don't do anything and just leave the game as is without inputs it runs for quite a while without issue. But without fail, if I start making inputs the game crashes within a minute or two. Most of the debug log is just this one line: 010c:err:sync:RtlLeaveCriticalSection section 0000000000FD26C0 (null) is not acquired And when the application stops responding it's: 01d4:err:sync:RtlpWaitForCriticalSection section 0000000000FD26F0 (null) wait timed out in thread 01d4, blocked by 0000, retrying (60 sec) At which point the application stops responding and I'm forced to terminate 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.

2 4

[Bug 59343] New: Debian 13 (Trixie): winehq-stable depends on non‑installable wine-stable-i386 despite WOW64 support
by WineHQ Bugzilla 31 Jan '26

31 Jan '26

http://bugs.winehq.org/show_bug.cgi?id=59343 Bug ID: 59343 Summary: Debian 13 (Trixie): winehq-stable depends on non‑installable wine-stable-i386 despite WOW64 support Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-packages Assignee: wine-bugs(a)list.winehq.org Reporter: w4wgw0okswwksckskgs8k4k0og8k4gos(a)ai.notifier.in CC: dimesio(a)earthlink.net Distribution: --- On Debian 13 (Trixie) amd64, installing winehq-stable from the WineHQ repository fails due to an unsatisfied dependency on wine-stable-i386, which is not installable on this system. The Debian/Ubuntu installation wiki states that with the new WoW64 support you no longer need to enable i386 architecture for Wine 11, but the current wine-stable:amd64 package still has a hard dependency on wine-stable-i386. > Steps to reproduce 1. Install a fresh Debian 13 (Trixie) amd64 system. 2. Add the official WineHQ repository for Trixie and import its key as documented. sudo apt update sudo apt install winehq-stable > Actual result apt fails with: wine-stable : Depends: wine-stable-i386 (= 11.0.0.0~trixie-1) but it is not installable E: Unable to correct problems, you have held broken packages. A detailed solver output (from apt/your frontend) shows: winehq-stable:amd64=11.0.0.0~trixie-1 Depends wine-stable (= 11.0.0.0~trixie-1) wine-stable:amd64=11.0.0.0~trixie-1 Depends wine-stable-i386 (= 11.0.0.0~trixie-1) but no installable candidate exists. > Expected result Either: - wine-stable:amd64 should be installable on a pure amd64 system without requiring wine-stable-i386 (new WoW64 packaging), or - The documentation should clearly state that i386 and multiarch are still required for the current Debian 13 packages, and the repository should provide a working wine-stable-i386 candidate. > Environment - Distribution: Debian 13 “Trixie” amd64 - Wine package: winehq-stable 11.0.0.0~trixie-1 - dpkg --print-architecture: amd64 - dpkg --print-foreign-architectures: Nothing - apt policy wine-stable-i386; wine-stable-i386: Installed: (none) Candidate: (none) Version table: > Comment I am using: # dpkg --list|grep wine ii libwine:amd64 10.0~repack-6 amd64 Windows API implementation - library ii wine 10.0~repack-6 all Windows API implementation - standard suite ii wine64 10.0~repack-6 amd64 Windows API implementation - 64-bit binary loader ii winetricks 20250102-1 all simple tool to work around common problems in Wine from debian APT, and I wanted to use Wine 11 from WineHQ because I heard it support WOW64 (32bit over 64bit), but since it cannot be installed without multiarch, I guess I have to wait for Debian maintainer instead :( -- 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