June 2026 - Wine-Bugs - list.winehq.org

[Bug 39303] New: Cannot copy schematics between different windows / ltspice
by wine-bugs＠winehq.org July 4, 2026

July 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=39303 Bug ID: 39303 Summary: Cannot copy schematics between different windows / ltspice Product: Wine Version: 1.7.51 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dieter.jurzitza(a)t-online.de Distribution: --- Trying to copy parts or an entire schematic between two schematics in two windows from within ltspice does not work. I can easily select components to copy, I can copy them within one single schematic, but I cannot copy them between two different schematics in a single ltspice instance (what works without issues using plain windows, but who is using plain windows :-)) Thank you for looking into this, take care Dieter Jurzitza -- 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 40620] New: Unhandled exception: page fault on read access to 0x00000001 in 32-bit code (0x00422056).
by wine-bugs＠winehq.org July 4, 2026

July 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=40620 Bug ID: 40620 Summary: Unhandled exception: page fault on read access to 0x00000001 in 32-bit code (0x00422056). Product: Wine-gecko Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: florit(a)gmx.at Distribution: --- Created attachment 54479 --> https://bugs.winehq.org/attachment.cgi?id=54479 the test project Console W32 cout some msg Simple ... i work on some App that rewrites some exe but enough from this. the Backtrace from the Applikation gives me some information About the crash in wine-1.9.7 Linux / OpenSuSe 13.2 . it's a win32 app that give me no idea why it dosen't should work. here the Backtrace: =>0 0x00422056 in output_a (+0x22056) (0x006df908) 1 0x004018e7 in output_a (+0x18e6) (0x006dfd88) 2 0x004013e2 in output_a (+0x13e1) (0x006dfe60) 3 0x7b465ecc call_process_entry+0xb() in kernel32 (0x006dfe78) 4 0x7b466fd3 in kernel32 (+0x46fd2) (0x006dfeb8) 5 0x7bc86020 call_thread_func_wrapper+0xb() in ntdll (0x006dfed8) 6 0x7bc8922d call_thread_func+0x7c() in ntdll (0x006dffa8) 7 0x7bc85ffe RtlRaiseException+0x21() in ntdll (0x006dffc8) 8 0x7bc5785e call_dll_entry_point+0x3fd() in ntdll (0x006dffe8) 9 0xf75453ad wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 10 0xf754546b wine_switch_to_stack+0x2a() in libwine.so.1 (0xffe5b4d8) 11 0x7bc5dc89 LdrInitializeThunk+0x238() in ntdll (0xffe5b518) 12 0x7b46d883 __wine_kernel_init+0xa12() in kernel32 (0xffe5c638) 13 0x7bc5eb83 __wine_process_init+0x192() in ntdll (0xffe5c6c8) 14 0xf7543220 wine_init+0x29f() in libwine.so.1 (0xffe5c728) 15 0x7c000c1c main+0x8b() in <wine-loader> (0xffe5cb78) 16 0xf735a993 __libc_start_main+0xf2() in libc.so.6 (0x00000000) I got no idea whats wrong! My modifyer or wine. now marked as bug for the moment ;) G()()D DAY and a lot of Work ... -- 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 56726] New: Ability to disable wine builtin title bar and borders
by WineHQ Bugzilla July 4, 2026

July 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=56726 Bug ID: 56726 Summary: Ability to disable wine builtin title bar and borders Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: Deresiant(a)protonmail.ch Distribution: --- Currently when running applications through wine on the wayland driver, those windows have a titlebar and border (I think these called window decorations?) which are provided by wine and can be configured in winecfg. There isn't a method to disable these window decorations completely. -- 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 59726] New: Syscall emulation on Linux using Syscall User Dispatch broken with glibc 2.34
by WineHQ Bugzilla July 3, 2026

July 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59726 Bug ID: 59726 Summary: Syscall emulation on Linux using Syscall User Dispatch broken with glibc 2.34 Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: valy(a)etersoft.ru Regression SHA1: cbb9906d75346c9ca9be8ac0b3ddb06d9d48824d Distribution: --- Created attachment 80872 --> http://bugs.winehq.org/attachment.cgi?id=80872 VisualStudioSetup.exe After initializing the Visual Studio installer (https://visualstudio.microsoft.com) under Wine 11.8, execution stops. I managed to identify that the cause is this commit: cbb9906d75346c9ca9be8ac0b3ddb06d9d48824d is the first bad commit commit cbb9906d75346c9ca9be8ac0b3ddb06d9d48824d (HEAD) Author: Elizabeth Figura zfigura(a)codeweavers.com Date: Fri Mar 13 16:25:41 2026 -0500 ntdll: Implement syscall emulation on Linux using Syscall User Dispatch. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=48291 dlls/ntdll/tests/exception.c | 1 - dlls/ntdll/unix/signal_x86_64.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------- 2 files changed, 60 insertions(+), 12 deletions(-) As I understand it, the reason for this behavior is the merging of libpthread, libdl, libutil, libanl into libc in version 2.34 (https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html) I am running with libc version 2.32. -- 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 19

[Bug 59296] New: Installed Adobe InDesign CS5.5 with no issue, but program crashes right after starting, attaching file with details.
by WineHQ Bugzilla July 2, 2026

July 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=59296 Bug ID: 59296 Summary: Installed Adobe InDesign CS5.5 with no issue, but program crashes right after starting, attaching file with details. Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: rucafiorio(a)proton.me Distribution: --- Created attachment 80234 --> http://bugs.winehq.org/attachment.cgi?id=80234 Error details Adobe Photoshop 5,1 works fine, fyi. -- 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 59745] New: Wine crashes when a custom window is created to show information
by WineHQ Bugzilla July 2, 2026

July 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=59745 Bug ID: 59745 Summary: Wine crashes when a custom window is created to show information Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: matthias0178+wine(a)gmail.com Distribution: --- Created attachment 80922 --> http://bugs.winehq.org/attachment.cgi?id=80922 Source code of the test program I created a program using C and the Windows API. This program was designed to create and display a specific window containing help text rendered via GDI. As soon as the user pressed any key on the keyboard or clicked with the mouse, the special window was supposed to be destroyed and the application terminated. Since this program functioned flawlessly on Windows but crashed under Wine immediately after displaying and destroying the special window, I developed a small test program that demonstrates the bug. This test program logs to the command line what occurs when the same task is executed in a simplified manner. I have attached the source code for this tiny test program. You may copy, modify and distribute it without restrictions to the extent permitted by law. On the Debian 13 console, the console output is not the same as in the console of Windows 11. -- 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 53812] New: Text does not show in Some APPs with native wine7.19
by WineHQ Bugzilla July 2, 2026

July 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=53812 Bug ID: 53812 Summary: Text does not show in Some APPs with native wine7.19 Product: Wine Version: 7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- Created attachment 73324 --> https://bugs.winehq.org/attachment.cgi?id=73324 how to reproduce problem I filed a bug(# Bug 53739) with the font display issue before, because I was doing some font replacements (seems to involve dwrite).This problem appears to be the same as the previous one, but it's not the same problem. This problem occurs in different sections of QQ, DingTalk, and corporate WeChat. For example, some fonts on the landing page of QQ are not displayed； some fonts are not displaye when sending a message on the meeting interface of corporate WeChat. Among them, the problem of QQ is the easiest to reproduce(even if you don't have an account, you can reproduce it), so I will use QQ to explain the problem below. 「Problem Description In general」—— use native unmodified wine In general, the font of QQ can be displayed normally on my virtual machine, but it cannot be displayed normally on my physical machine，with the same Language Environment and System installation scene > $ echo LANG = zh_CN.UTF-8 > System installation scene：debian-live-11.4.0-amd64-kde.iso > System installation scene download URL:https://drive.google.com/file/d/14FJVpGkLNTJrDlU9SQW38eSIFlr_qjUB/view?… 「The machine I use」 M1: "physical machine" debian-11.4.0-KDE M2: "virtual machine" debian-11.4.0-KDE 「 Problem Description 」 I just downloaded the source code of wine 7.19 and make it. I click to add an account, the font display of QQ fails on M1, but successed on M2. By use WINEDEBUG=+relay,I find when text show on M2, APPs called API:ScriptTextOut,and then text show successed. But on M1, APPs called API:ExtTextOutW, and then text show fails. I just started to suspect that QQ has different versions installed on different machines, so I packaged all the files of QQ installed on the virtual machine into a zip file, and then took this file to the physical machine to run, but the text still cannot be show on the physical machine. I don't know why QQ calls different APIs on the physical machine and the virtual machine to output text, so I'm asking for your help. What channel should I use to check my environment？nls?locale? 「Reproduce Problem」 The picture(how_to_..._proble,.png) shows the operation process QQ downloardURL:https://im.qq.com/download QQ Version:9.6.7 -- 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 55138] New: msys2: bash.exe is not able to fork/start another process.
by WineHQ Bugzilla July 2, 2026

July 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=55138 Bug ID: 55138 Summary: msys2: bash.exe is not able to fork/start another process. Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 74697 --> https://bugs.winehq.org/attachment.cgi?id=74697 allocation stacks in parent and child bash.exe This is a followup to bug 47808. If I understand it right, bug 47808 was primarily about native libraries getting called at a win32 stack which was not yet committed. Those native libraries then jumped over the guard page, therefore the stack got not grown, instead a crash reported. This aspect was fixed by using the syscall interface and therefore bug 47808 was closed. But there is another issue that causes a msys2-forked process crashing, because after the stack was grown it still misses the PAGE_READWRITE flags. For this Zeb Figura included in the first attachement to bug 47808 "always expand the stack if within the stack reserve" a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE" to the page that gets the VPROT_GUARD removed in grow_thread_stack. This modification still enables a forked process to run. The issue can be reproduced with an unmodified wine by just - running msys2 bash.exe interactively - then trying to start e.g. notepad from it. Attached file shows the stack when the stack gets allocated - in a working msys2-parent process and - in a failing msys2-forked child process. Therefore it looks like the forked stack get really setup differently, but it is still not clear if or when this memory gets the READ/WRITE added in native windows. -- 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 39006] New: ISAXAttributes.getLocalName should only return an empty string for namespace attributes that are not xmlns
by wine-bugs＠winehq.org July 2, 2026

July 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=39006 Bug ID: 39006 Summary: ISAXAttributes.getLocalName should only return an empty string for namespace attributes that are not xmlns Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: ott(a)mirix.org Distribution: --- According to the specification the local name if a namespace propery is only an empty string if it is exactly "xmlns": "For "xmlns", this value is empty." (https://msdn.microsoft.com/en-us/library/ms757865%28v=vs.85%29.aspx) This makes sense because it would be impossible to get the namespace prefix otherwise. -- 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 39004] New: ISAXAttributes.getQName should return an empty string for xmlns attributes
by wine-bugs＠winehq.org July 2, 2026

July 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=39004 Bug ID: 39004 Summary: ISAXAttributes.getQName should return an empty string for xmlns attributes Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: msxml3 Assignee: wine-bugs(a)winehq.org Reporter: ott(a)mirix.org Distribution: --- According to the specification ISAXAttribute.getQName should return an empty string if "http://xml.org/sax/features/namespace-prefixes" is enabled and an attribute is an xmlns attribute: "For the "xmlns" namespace, the qname value is empty." (https://msdn.microsoft.com/en-us/library/ms760423%28v=vs.85%29.aspx) (If "http://xml.org/sax/features/namespace-prefixes" is disabled such attributes are correctly ignored.) -- 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