wine-bugs

wine-bugs@winehq.org

1 participants
159090 discussions

[Bug 58592] New: Font substitution partially broken - regression
by WineHQ Bugzilla 05 Sep '25

05 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58592 Bug ID: 58592 Summary: Font substitution partially broken - regression 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: zdenek.koprivik(a)post.cz Distribution: --- While trying to replace "Tahoma" with "Noto Sans Regular" (the default Plasma desktop font), I've encountered an issue, where the font replacement does not work in some cases. Since I'm migrating from a very old system with Wine 1.6.2, I know that the font replacement used to work for the exact same binary and the same UI elements. I've set the following registry keys: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Tahoma"="Noto Sans Regular" "Segoe UI"="Noto Sans Regular" "MS Shell Dlg"="Noto Sans Regular" "MS Shell Dlg 2"="Noto Sans Regular" The issue can be reproduced by opening the file dialog in the built-in registry editor. Running the built-in registry editor I've got the main font changed to "Noto Sans Regular" as expected, but in the file open dialog for import, there is still "Tahoma". When I'm browsing for directories, the font changes to "Noto Sans Regular", but when an item is selected, the font changes back to "Tahoma". Here is a short video showing the issue: https://imgur.com/a/l0BhsB8 This is only one example of the non-working substitution. The "Tahoma" is also rendered on the buttons and almost everywhere around in the dialog. I'm using the substitution mostly for MikroTik network equipment management apps (WinBox and The Dude) to improve the readability. It is working fine when running the exact same binaries on the old PC with Wine 1.6.2, but I can't get it to work with the newest Wine. The system is KDE neon User, Plasma 6.4.4, Wine 10.12 from the WineHQ PPA. -- 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 7

[Bug 58670] New: [Damavand] The renderer crashes with Clickteam games
by WineHQ Bugzilla 05 Sep '25

05 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58670 Bug ID: 58670 Summary: [Damavand] The renderer crashes with Clickteam games Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- When trying to play clickteam games with damavand, they crash before anything is rendered. These lines appear the most in the console: 0148:fixme:d3d_shader:shader_spirv_scan_shader Shader log: 0148:fixme:d3d_shader:shader_spirv_scan_shader <anonymous>:25:0: W7006: Input register 9 was used without being declared. 0148:fixme:d3d_shader:shader_spirv_scan_shader <anonymous>:26:0: W7006: Input register 10 was used without being declared. The full log is attached (This one is from FNaF World specifically) -- 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 56614] New: Videos are not player in The Signifier (GOG)
by WineHQ Bugzilla 05 Sep '25

05 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=56614 Bug ID: 56614 Summary: Videos are not player in The Signifier (GOG) Product: Wine Version: 9.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- Created attachment 76371 --> https://bugs.winehq.org/attachment.cgi?id=76371 console log Videos are not played. Observable during menu and on the computer at the beginning. Console output attached. wine-9.7-100-g7641124d07a -- 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 24

[Bug 58610] New: Sim Racing Studio fails to start: “Error Loading Prython DLL ”C:\Progam Files\RimsRacingStudio 2.0\python312.dll"
by WineHQ Bugzilla 05 Sep '25

05 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58610 Bug ID: 58610 Summary: Sim Racing Studio fails to start: “Error Loading Prython DLL ”C:\Progam Files\RimsRacingStudio 2.0\python312.dll" Product: Wine Version: 10.13 Hardware: x86-64 URL: https://www.simracingstudio.com/download OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Reported on the forum: https://forum.winehq.org/viewtopic.php?t=41487; Note: dotnet48 installed beforehand Debug shows it fails just after it can't get entry for PssQuerySnapshot, see below. After adding a stub entry, story repeats for PssCaptureSnapshot and PsFreeSnapshot. After adding those the application starts. I'll send patches later. 0100:Call KERNEL32.GetProcAddress(6fffffeb0000,6ffffe3653f0 "PssQuerySnapshot") ret=6ffffe373909 0100:Ret KERNEL32.GetProcAddress() retval=00000000 ret=6ffffe373909 0100:Ret PE DLL (proc=00006FFFFE372DB0,module=00006FFFFDCC0000 L"python312.dll",reason=PROCESS_ATTACH,res=0000000000000000) retval=0 0100:Call PE DLL (proc=00006FFFFE372DB0,module=00006FFFFDCC0000 L"python312.dll",reason=PROCESS_DETACH,res=0000000000000000) 0100:Ret PE DLL (proc=00006FFFFE372DB0,module=00006FFFFDCC0000 L"python312.dll",reason=PROCESS_DETACH,res=0000000000000000) retval=0 0100:Call PE DLL (proc=00006FFFFF982AD0,module=00006FFFFF980000 L"WS2_32.dll",reason=PROCESS_DETACH,res=0000000000000000) 0100:Ret PE DLL (proc=00006FFFFF982AD0,module=00006FFFFF980000 L"WS2_32.dll",reason=PROCESS_DETACH,res=0000000000000000) retval=1 0100:Call PE DLL (proc=00006FFFFDC516A0,module=00006FFFFDC50000 L"VERSION.dll",reason=PROCESS_DETACH,res=0000000000000000) 0100:Ret PE DLL (proc=00006FFFFDC516A0,module=00006FFFFDC50000 L"VERSION.dll",reason=PROCESS_DETACH,res=0000000000000000) retval=1 0100:Call PE DLL (proc=00006FFFFDC713B0,module=00006FFFFDC70000 L"VCRUNTIME140.dll",reason=PROCESS_DETACH,res=0000000000000000) 0100:Ret PE DLL (proc=00006FFFFDC713B0,module=00006FFFFDC70000 L"VCRUNTIME140.dll",reason=PROCESS_DETACH,res=0000000000000000) retval=1 0100:Call PE DLL (proc=00006FFFFDC96600,module=00006FFFFDC90000 L"bcrypt.dll",reason=PROCESS_DETACH,res=0000000000000000) 0100:Ret PE DLL (proc=00006FFFFDC96600,module=00006FFFFDC90000 L"bcrypt.dll",reason=PROCESS_DETACH,res=0000000000000000) retval=1 0100:Ret ntdll.LdrLoadDll() retval=c0000142 ret=6fffffc703d2 0100:Call ntdll.RtlReleasePath(002b7750) ret=6fffffc703e3 0100:Ret ntdll.RtlReleasePath() retval=00000001 ret=6fffffc703e3 0100:Ret KERNEL32.LoadLibraryExW() retval=00000000 ret=140007209 0100:Call KERNEL32.GetLastError() ret=14000265a 0100:Ret KERNEL32.GetLastError() retval=0000045a ret=14000265a 0100:Call KERNEL32.FormatMessageW(00001000,00000000,0000045a,00000400,00205520,7c4001f00001000,00000000) ret=14000753c 0100:Call ntdll.RtlFindMessage(6fffffbf0000,0000000b,00000400,0000045a,00205348) ret=6fffffc6c796 0100:Ret ntdll.RtlFindMessage() retval=00000000 ret=6fffffc6c796 0100:Call ntdll.RtlFormatMessage(6fffffe43d1c,00000000,00000000,00000000,401039a00000000,00000000,00205520,3c103fe00002000,002053fc) ret=6fffffc10f1a 0100:Ret ntdll.RtlFormatMessage() retval=00000000 ret=6fffffc10f1a 0100:Ret KERNEL32.FormatMessageW() retval=0000001c ret=14000753c 0100:Call KERNEL32.WideCharToMultiByte(0000fde9,00000000,00205520 L"DLL initialization failed.\r\n",ffffffff,14004b000,7c4001f00001000,00000000,00000000) ret=140007592 0100:Call ntdll.RtlUnicodeToUTF8N(14004b000,00001000,002053fc,00205520,0000003a) ret=6fffffc604c5 0100:Ret ntdll.RtlUnicodeToUTF8N() retval=00000000 ret=6fffffc604c5 0100:Ret KERNEL32.WideCharToMultiByte() retval=0000001d ret=140007592 0100:Call KERNEL32.MultiByteToWideChar(0000fde9,00000000,00207570 "Error loading Python DLL 'C:\\Program Files\\SimRacingStudio 2.0\\python312.dll'.\nLoadLibrary: DLL initialization failed.\r\n",ffffffff,00208570,00000400) ret=140007b26 0100:Call ntdll.strlen(00207570 "Error loading Python DLL 'C:\\Program Files\\SimRacingStudio 2.0\\python312.dll'.\nLoadLibrary: DLL initialization failed.\r\n") ret=6fffffc2aa19 0100:Ret ntdll.strlen() retval=00000078 ret=6fffffc2aa19 -- 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 58604] New: Unable to handle Ctrl+C signal correctly，02c0:fixme:console:default_ctrl_handler Terminating process e0 on event 0
by WineHQ Bugzilla 05 Sep '25

05 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58604 Bug ID: 58604 Summary: Unable to handle Ctrl+C signal correctly，02c0:fixme:console:default_ctrl_handler Terminating process e0 on event 0 Product: Wine Version: 10.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 1514704742(a)qq.com Distribution: --- Unable to handle Ctrl+C signal correctly -- 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 10

[Bug 38985] New: CopyTrans Manager Invalid Floating Point operation on install
by wine-bugs＠winehq.org 04 Sep '25

04 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=38985 Bug ID: 38985 Summary: CopyTrans Manager Invalid Floating Point operation on install Product: Wine Version: 1.7.47 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: axfelix(a)gmail.com Distribution: --- axfelix@shoebox:~/Downloads$ wine Install* fixme:ntoskrnl:KeInitializeSpinLock stub: 0x662740 fixme:ntoskrnl:KeInitializeSpinLock stub: 0x66273c fixme:ntoskrnl:KeInitializeSpinLock stub: 0x662744 fixme:ntoskrnl:KeInitializeSpinLock stub: 0x662748 fixme:ntoskrnl:KeInitializeSpinLock stub: 0x66274c fixme:ntoskrnl:KeInitializeEvent stub: 0x66272c 1 0 fixme:ntoskrnl:IoInitializeTimer stub: 0x660020, 0x54c3d0, 0x660020 fixme:ntoskrnl:IoStartTimer stub: 0x660020 fixme:ntoskrnl:KeWaitForSingleObject stub: 0x66272c, 0, 0, 0, (nil) fixme:ntoskrnl:PsTerminateSystemThread stub: 0 fixme:ntoskrnl:ExInitializeResourceLite stub: 0x112882 fixme:ntoskrnl:KeInitializeSpinLock stub: 0x1128da fixme:ntoskrnl:KeInitializeSpinLock stub: 0x1128e6 fixme:ntoskrnl:KeInitializeEvent stub: 0x1128ee 1 1 fixme:ntoskrnl:KeInitializeSpinLock stub: 0x1128fe fixme:ntoskrnl:KeInitializeSpinLock stub: 0x1128ce fixme:ntoskrnl:ExInitializeZone stub: 0x1128be, 192, 0x112c58, 24584 fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:process:SetProcessDEPPolicy (1): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:process:SetProcessShutdownParameters (00000380, 00000000): partial stub. fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot fixme:wtsapi:WTSRegisterSessionNotification Stub 0x1007a 0x00000000 fixme:msg:ChangeWindowMessageFilterEx 0x10086 400 1 (nil) fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub! fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:win:WINNLSEnableIME hwnd 0x10134 enable -1: stub! fixme:win:WINNLSEnableIME hwnd 0x10144 enable -1: stub! fixme:win:WINNLSEnableIME hwnd 0x10134 enable -1: stub! fixme:win:WINNLSEnableIME hwnd 0x40150 enable -1: stub! fixme:win:WINNLSEnableIME hwnd 0x40150 enable -1: stub! fixme:win:WINNLSEnableIME hwnd 0x40150 enable -1: stub! Killed During "check connection" phase of install process, throws an "invalid floating point operation" popup; appears to continue to work in the background, but attempting to dismiss this popup causes it to repeatedly reappear and reprint the last line in the above output. -- 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 3

[Bug 58668] New: SolidWorks - Certain buttons fail to trigger actions
by WineHQ Bugzilla 04 Sep '25

04 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58668 Bug ID: 58668 Summary: SolidWorks - Certain buttons fail to trigger actions Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- Created attachment 79253 --> http://bugs.winehq.org/attachment.cgi?id=79253 SolidWorks 2023 buttons not working on Wine-10.14 Clicking certain buttons in SolidWorks no longer trigger an action, but stop at selecting the button instead. This bug must have been introduced some time after wine-9.22, as wine-9.22 works fine. Please see attached screen grab for SolidWorks 2023sp05: The buttons in question are - <Close>, aka green tick mark - "Rectangle Type" selection When building wine-10.14 from source, replacing the wine-10.14 folder "dlls/comctl32" with the older one from wine-9.22 fixes the problem and the SolidWorks buttons work again. -- 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 58665] New: cmd incorrectly wraps text containing ANSI escape sequences
by WineHQ Bugzilla 04 Sep '25

04 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58665 Bug ID: 58665 Summary: cmd incorrectly wraps text containing ANSI escape sequences Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: forestix(a)gaga.casa Distribution: --- Created attachment 79250 --> http://bugs.winehq.org/attachment.cgi?id=79250 reproducer: should print 3 lines; wine prints 4 lines Wine's cmd.exe prematurely inserts line breaks when a program's output contains non-printable ANSI escape sequences, such as those used to change colors. It looks as though Wine is counting not only the printable characters in the program's output, but also the non-printable ones, and using the total to decide where to insert a line break. Text that fits entirely on one line in a real Windows console is sometimes broken midway through the line, or followed by a blank line that should not be there, when run in an xterm using Wine. I am attaching a batch file that reproduces the problem. It should print 3 lines. The second line is identical to the others with the addition of some non-printable escape sequences. These characters should either occupy no width in the terminal (making the line length match the others) or be rendered as visible placeholder characters (as older Windows versions do). To see Wine handling it incorrectly, run it in an 80-column xterm or a similar terminal. Ideally, the output should look like this, with the head of line 2 in red: 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 In wine, the output looks like this: 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_12 3456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 Bug 49780 is related, but IMHO does not excuse this behavior. Regardless of whether virtual terminal sequences are supported, Wine should either print a character or not count it toward the length of a line when deciding where to wrap 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 1

[Bug 58500] New: 64-bit "Plain Vanilla Compiling" fails
by WineHQ Bugzilla 04 Sep '25

04 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58500 Bug ID: 58500 Summary: 64-bit "Plain Vanilla Compiling" fails Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- Building Wine-10.12 "64-bit only" shows a number of issues and fails in the end during "make install" when trying to copy a non-existing file. Test-Environment: - Host providing RAMdisk as SharedDrive for build - VirtualBox 7.1.10 r169112 VM with - 8 cores - Debian 12 bookworm 64-bit & KDE - user "vbox" - no previous Wine installation (neither cxoffice or others) - SharedDrive mounted as /home/vbox/RAMdisk -- 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 14

[Bug 57691] New: wine-mono: ASan gets triggered in mono_path_canonicalize with strcpy-param-overlap.
by WineHQ Bugzilla 04 Sep '25

04 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57691 Bug ID: 57691 Summary: wine-mono: ASan gets triggered in mono_path_canonicalize with strcpy-param-overlap. Product: Wine Version: 10.0-rc6 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 77881 --> https://bugs.winehq.org/attachment.cgi?id=77881 asan_2025-01-18_17-11-19_.1748 Hello, I tried getting wine being built with ASan (PE side) enabled. [1] And tried running on this build the wine conformance tests. One place where ASan gets triggered is in mono\mono\utils\mono-path.c [2]: 90 if (dest != lastpos) strcpy (dest, lastpos); ERROR: AddressSanitizer: strcpy-param-overlap A few lines above (line 74) there is the possibility of the strings overlapping mentioned and a memmove used. Attached file contains the full output of one ASan event. Would it be valuable to replace the `strcpy (dest, lastpos);` by a `memmove (dest, lastpos, strlen(lastpos) + 1)`? [1] https://gitlab.winehq.org/bernhardu/wine/-/blob/asan-pe_2024-12-29/README.md [2] https://gitlab.winehq.org/mono/mono/-/blame/main/mono/utils/mono-path.c#L90 -- 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

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