November 2025 - Wine-Bugs - list.winehq.org

[Bug 59060] New: Movie Maker msi does not open
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59060 Bug ID: 59060 Summary: Movie Maker msi does not open Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)list.winehq.org Reporter: passymas(a)gmail.com Distribution: --- Created attachment 79830 --> http://bugs.winehq.org/attachment.cgi?id=79830 error movie maker msi Movie Maker msi does not open. -- 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 57588] New: Guardant USB key drivers: grdkey.sys crashes
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

https://bugs.winehq.org/show_bug.cgi?id=57588 Bug ID: 57588 Summary: Guardant USB key drivers: grdkey.sys crashes Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: amorozov(a)etersoft.ru Distribution: --- Created attachment 77697 --> https://bugs.winehq.org/attachment.cgi?id=77697 Log with WINEDEBUG=+ntoskrnl,+plugplay and winedbg output I installed Guardant USB key drivers 7.0.224 from here: https://www.guardant.com/support/users/download/2238/ with WoW64 Wine build. $ md5sum GrdDrivers.exe 731d388d2ee4c1a4f45d655e4b8c9163 GrdDrivers.exe After installation windows/system32/drivers/grdkey.sys appears. And it crashes at Wine start: wine: Unhandled page fault on read access to 0000000000000008 at address 00006FFFFC8A295B (thread 00f0), starting debugger... In AddDevice handler grdkey.sys calls IoOpenDeviceRegistryKey. This results in calling get_device_instance_id -> get_device_id and sending IRP_MJ_PNP/IRP_MN_QUERY_ID with BusQueryDeviceID to the driver which calls IofCallDriver(NULL, ....) and crashes. The crash can be avoided with commenting out this line: device = IoGetAttachedDevice( device ); in get_device_id function in dlls/ntoskrnl.exe/pnp.c But I assume that the correct fix should be in avoiding to send IRPs from IoOpenDeviceRegistryKey. MSDN says that IRP_MN_QUERY_ID is sent before loading driver and calling AddDevice: https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/adding-a-… -- 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 30853] New: Wine doesn’t always handle "right alt" properly
by wine-bugs＠winehq.org Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=30853 Bug #: 30853 Summary: Wine doesn’t always handle "right alt" properly Product: Wine Version: 1.5.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 40410 --> http://bugs.winehq.org/attachment.cgi?id=40410 workaround/quick and dirty fix I’m trying to get World of Warcraft working under Wine. However, I have huge trouble with key bindings (I use unusual key bindings : I use the right half of my keyboard, whereas most players use the left half). After investigation, I found 3 bugs (different behaviors between Wine and my Windows installation). The first one is the management of the right "Alt" key (labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with Spy++, I get the followings events : <03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:0 fRepeat:0 fUp:0 <03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:0 fUp:0 <03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:0 fRepeat:1 fUp:1 Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb lp 760001 [note: wp = VK_OEM_PA2] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp c0260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp c0760001 [note: wp = VK_OEM_PA2] With xev, I get : KeyPress event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425), state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425), state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I get this under Wine : trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp a5 lp 21380001 [wp = VK_RMENU] trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp 4c lp 20260001 [wp = 'L'] trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c lp 20260001 [wp = 'l'] trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c lp e0260001 [wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp c1380001 [wp = VK_RMENU] (yes, I have a KEYUP without KEYDOWN) Wich is still not the same as Windows. So I think there is two problems here : - ISO_Level3_Shift is not properly recognized by Wine - "AltGr" doesn't have the same behavior under Wine and Windows FYI, attached patch is a workaround to have the same behavior than Windows. With it, I get this under Wine : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2 lp 1d0001 [note: wp = VK_LCONTROL] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4 lp 20380001 [note: wp = VK_LMENU] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c lp 20260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp e0260001 trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2 lp e01d0001 trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp c0380001 Which is still not the same as Windows : - Windows uses (right) control + menu (with fExtended flag for menu) whereas Wine uses left control + left menu. Not investigated if this is related to TranslateMessage. - AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message, wheras Wine send nothing. Note that I had to disable the XFilterEvent test in event.c to have those messages, otherwise nothing is sent to the program (but that’s another story for another bug report) But it suffice for my use case (WoW key bindings with right alt) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 57925] New: winewayland.drv: Games are not filled to my monitor's resolution
by WineHQ Bugzilla Nov. 30, 2025

Nov. 30, 2025

https://bugs.winehq.org/show_bug.cgi?id=57925 Bug ID: 57925 Summary: winewayland.drv: Games are not filled to my monitor's resolution Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78178 --> https://bugs.winehq.org/attachment.cgi?id=78178 SWAT 4 output log (in this log I opened the settings and tried to set the maximum resolution that the game supports) Old games (specifically Ghost Recon, Splinter Cell 1, Splinter Cell 2 and SWAT 4) won't fill to my monitor's resolution, even if I switch to a higher resolution in the game settings. This MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/6804) was supposed to work with winewayland.drv and fix this issue, but it doesn't work or fix it. However, this MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/5057) does work and fixes that issue. There is a workaround (at least for SWAT 4): which is to take the game window out of fullscreen, then toggle the maximization state of the game window and put the game window back into fullscreen (In labwc/openbox terms: ToggleFullscreen > ToggleMaximize > ToggleFullscreen). I think it also works for Ghost Recon. Splinter Cell 1 even supports 16:9 resolutions, but only in game (in the menus, loadings and cut-scenes are still not filled in for my monitor's resolution) and Splinter Cell 2 is worse, there's no support for 16:9 resolutions or even a workaround. - I use labwc/wlroots as WM. - I'm using the new WoW64 mode. I did some tests with normal wine, but it's been a few weeks or months, so I'm not sure if the new WoW64 mode has any impact here, but I don't think so. (Sorry if the paraphrases seem disconnected from each other, if I'm not very clear or if I'm giving too little information. I've been doing a lot of testing over the last few hours and my mind isn't in a good place to come up with a good text here :/) -- 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 8

[Bug 59059] New: Cannot update/upgrade from wine-staging-1:10.17.1.1.x86_64 to wine-staging-1:10.18.1.1.x86_64
by WineHQ Bugzilla Nov. 29, 2025

Nov. 29, 2025

http://bugs.winehq.org/show_bug.cgi?id=59059 Bug ID: 59059 Summary: Cannot update/upgrade from wine-staging-1:10.17.1.1.x86_64 to wine-staging-1:10.18.1.1.x86_64 Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)list.winehq.org Reporter: JustTiredOfThis(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- grayman(a)hyperactive:~$ sudo dnf update -y Updating and loading repositories: Repositories loaded. Problem 1: cannot install the best update candidate for package wine-staging-1:10.17-1.1.x86_64 - nothing provides wine-missing-buildrequires-on-OSMesa needed by wine-staging-1:10.18-1.1.x86_64 from WineHQ Problem 2: package winehq-staging-1:10.18-1.1.x86_64 from WineHQ requires wine-staging = 1:10.18-1.1, but none of the providers can be installed - cannot install the best update candidate for package winehq-staging-1:10.17-1.1.x86_64 - nothing provides wine-missing-buildrequires-on-OSMesa needed by wine-staging-1:10.18-1.1.x86_64 from WineHQ Package Arch Version Repository Size Skipping packages with broken dependencies: wine-staging x86_64 1:10.18-1.1 WineHQ 1.4 GiB winehq-staging x86_64 1:10.18-1.1 WineHQ 62.0 KiB -- 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 58901] New: Fedora packages include dummy package in place of libOSMesa
by WineHQ Bugzilla Nov. 29, 2025

Nov. 29, 2025

http://bugs.winehq.org/show_bug.cgi?id=58901 Bug ID: 58901 Summary: Fedora packages include dummy package in place of libOSMesa Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: wolfy1339(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- The current Fedora packages for Wine 10.18 are broken due to the inclusion of a dummy package in the Requirements named wine-missing-buildrequires-on-OSMesa It would seem from that, that the libOSMesa is missing in the build environment -- 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 51546] New: ran a application and it gave an error
by WineHQ Bugzilla Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=51546 Bug ID: 51546 Summary: ran a application and it gave an error Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrtbryanonlinux(a)gmail.com Distribution: --- Created attachment 70389 --> https://bugs.winehq.org/attachment.cgi?id=70389 Im trying to run Xenos64.exe for gta v and then that happened plz help tried to run a application called xenos64.exe i use it for gta v so i wined it then that happened. plz try and fix ASAP -- 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 8

[Bug 45063] New: win64 / 64-bit .NET 4.0 - c0000005 from ntdll: RtlGetDaclSecurityDescriptor
by wine-bugs＠winehq.org Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=45063 Bug ID: 45063 Summary: win64 / 64-bit .NET 4.0 - c0000005 from ntdll:RtlGetDaclSecurityDescriptor Product: Wine Version: 3.6 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: pembertona(a)gmail.com After fighting for some to get .NET 4.0 running on 64 bit (great progress here after overcoming multiple msi/msiexec/installer issues), I've hit an access violation exception running a very basic 'hello world' 64-bit console app. This is on `portable-winehq-staging-3.6-osx64` - but almost certainly the devel and stable branches as well. 136984.882:0008:0041:Call advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW(19e1f7f8 L"D:P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)",00000001,19e1f780,19e1f7c8) ret=6447f2c4d3e 136984.884:0008:0041:trace:advapi:ConvertStringSecurityDescriptorToSecurityDescriptorW L"D:P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 1, 0x19e1f780, 0x19e1f7c8 136984.884:0008:0041:trace:heap:RtlAllocateHeap (0x10000,70000062,00000062): returning 0xf60b0 136984.885:0008:0041:trace:advapi:ParseStringAclToAcl L"P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)" 136984.885:0008:0041:trace:advapi:ParseStringSidToSid L"BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 0x0, 0x19e1f514 136984.885:0008:0041:trace:advapi:ParseStringSidToSid only size requested, returning TRUE with 16 136984.885:0008:0041:trace:advapi:ParseStringSidToSid L"S-1-5-21-0-0-0-1000)", 0x0, 0x19e1f514 136984.885:0008:0041:trace:advapi:ParseStringSidToSid only size requested, returning TRUE with 28 136984.885:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0xf60b0): returning TRUE 136984.886:0008:0041:trace:heap:RtlAllocateHeap (0x10000,7000006a,00000058): returning 0x46340 136984.886:0008:0041:trace:heap:LocalAlloc (flags=0040) returning 0x46340 136984.886:0008:0041:trace:heap:RtlAllocateHeap (0x10000,70000062,00000062): returning 0x46420 136984.886:0008:0041:trace:advapi:ParseStringAclToAcl L"P(A;;GRGW;;;BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)" 136984.886:0008:0041:trace:advapi:ParseStringSidToSid L"BA)(A;;GRGW;;;S-1-5-21-0-0-0-1000)", 0x46364, 0x19e1f514 136984.886:0008:0041:trace:advapi:ParseStringSidToSid returning TRUE 136984.886:0008:0041:trace:advapi:ParseStringSidToSid L"S-1-5-21-0-0-0-1000)", 0x4637c, 0x19e1f514 136984.886:0008:0041:trace:advapi:ParseStringSidToSid returning TRUE 136984.887:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0x46420): returning TRUE 136984.887:0008:0041:trace:advapi:ConvertStringSecurityDescriptorToSecurityDescriptorW ret=1 136984.887:0008:0041:Ret advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW() retval=00000001 ret=6447f2c4d3e 136984.887:0008:0041:Call ntdll.RtlFreeHeap(00010000,00000000,000f5f30) ret=6447f2c4dc8 136984.887:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0xf5f30): returning TRUE 136984.887:0008:0041:Ret ntdll.RtlFreeHeap() retval=00000001 ret=6447f2c4dc8 136984.887:0008:0041:trace:ntdll:RtlGetSaclSecurityDescriptor (0x46340,0x19e1f716,0x19e1f718,0x19e1f715) 136984.887:0008:0041:trace:ntdll:RtlGetDaclSecurityDescriptor (0x46340,0x19e1f717,0x19e1f720,0x19e1f715) 136984.887:0008:0041:trace:heap:RtlAllocateHeap (0x10000,7000006a,0000009c): returning 0x46570 136984.888:0008:0041:trace:heap:RtlFreeHeap (0x10000,70000062,0x46570): returning TRUE 136984.888:0008:0041:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x6447f1d6f19 ip=6447f1d6f19 tid=0041 136984.888:0008:0041:trace:seh:NtRaiseException info[0]=0000000000000000 136984.888:0008:0041:trace:seh:NtRaiseException info[1]=0000000000000010 136984.888:0008:0041:trace:seh:NtRaiseException rax=0000000000000000 rbx=000006447f27fd30 rcx=0000000019e1fce0 rdx=0000000019e21ad0 136984.888:0008:0041:trace:seh:NtRaiseException rsi=0000000019e1fce0 rdi=0000000000000000 rbp=0000000019e1fe00 rsp=0000000019e1fc20 136984.888:0008:0041:trace:seh:NtRaiseException r8=0000000019e1f298 r9=0000000000000010 r10=0000000019e21b25 r11=ffffffffffffffa9 136984.888:0008:0041:trace:seh:NtRaiseException r12=0000000000000000 r13=0000000000000000 r14=0000000000044860 r15=0000000000000000 136984.888:0008:0041:trace:seh:call_vectored_handlers calling handler at 0x6447f30a954 code=c0000005 flags=0 ... 136984.967:0008:0041:err:eventlog:ReportEventW L"Application: Console64.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an internal error in the .NET Runtime at IP 000006447F1D6F19 (000006447F100000) with exit code 80131506.\n" Possibly related to https://bugs.winehq.org/show_bug.cgi?id=27680? -- 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 22

[Bug 58932] New: Some comboboxes are no longer size correctly after commit in version 10.16
by WineHQ Bugzilla Nov. 28, 2025

Nov. 28, 2025

http://bugs.winehq.org/show_bug.cgi?id=58932 Bug ID: 58932 Summary: Some comboboxes are no longer size correctly after commit in version 10.16 Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)list.winehq.org Reporter: cayok52759(a)wivstore.com Distribution: --- Certain combo boxes are no longer sized correctly beginning in Wine 10.16 and have extra spacing below the text in them. This can be seen in a Bible study program that can be downloaded at https://www.theword.net/files/setup/getmulti.php/en. To see the problem, the program can be installed using the "Basic" layout. From the View|Toolbars menu, enable the Formatting toolbar. In the Book documents view there should be a button called "My Subject-notes." Select that book and click inside the view. The Formatting toolbar should now appear at the top with the other toolbars. Now position all toolbars so that they are on the same row. Alternately click between the book view and another view. Because the font size combobox is now slightly too large when an editable book view is active, the program will shift its views in order to compensate. If another view is clicked in, then the Formatting toolbar will disappear and the views will shift again. Other comboboxes in the program are also affected by this regression. The comboboxes are sized properly after reverting the commit "comctl32/combo: Don't update item height on WM_SETFONT for owner drawn CB" at https://gitlab.winehq.org/wine/wine/-/commit/9efece4a98774a9ee12bfd4d221e4e…. The program that this is happening in is written in Delphi 12. I do not know if any non-Delphi programs exhibit this problem or not. -- 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 56577] New: QuarkXPress 2024 crashes on start with assertion error "symt_check_tag(&func->symt, SymTagFunction) || symt_check_tag(&func->symt, SymTagInlineSite)"
by WineHQ Bugzilla Nov. 28, 2025

Nov. 28, 2025

https://bugs.winehq.org/show_bug.cgi?id=56577 Bug ID: 56577 Summary: QuarkXPress 2024 crashes on start with assertion error "symt_check_tag(&func->symt, SymTagFunction) || symt_check_tag(&func->symt, SymTagInlineSite)" Product: Wine Version: 9.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 76332 --> https://bugs.winehq.org/attachment.cgi?id=76332 Terminal output On start, the program displays an error dialog titled "Wine C++ Runtime Library" which says: Assertion failed! Program: C:\Program Files\Quark\QuarkXPress 2024\QuarkXPress 2024.exe File: ../wine/dlls/dbghelp/symbol.c Line: 543 Expression: "symt_check_tag(&func->symt, SymTagFunction) || symt_check_tag(&func->symt, SymTagInlineSite)" Press OK to exit the program, or Cancel to start the Wine debugger. $ sha256sum QX2024_57226_Win.zip d3da582f0836db1bd6930e94b0f5c56b8e91c60a49928647acf75e4bb85e8b2c -- 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 6