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

[Bug 39004] New: ISAXAttributes.getQName should return an empty string for xmlns attributes
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 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 5

[Bug 57584] New: 8-bit color mode is broken in Wine 9.11 and later
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=57584 Bug ID: 57584 Summary: 8-bit color mode is broken in Wine 9.11 and later Product: Wine Version: 9.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 77694 --> https://bugs.winehq.org/attachment.cgi?id=77694 Regedit on Wine 9.22 in Xephyr Similar to Bug 48088, palette colors are being mapped incorrectly again. Steps to reproduce: 1. In one terminal, run `Xephyr :2 -ac -screen 800x600x8` 2. In a second terminal, run `DISPLAY=:2 openbox` 3. In a third terminal, run `DISPLAY=:2 wine regedit` `git bisect` says: commit 6ace92e0cafcc381f324fc831f3006fb15db4b4e (HEAD) Author: Rémi Bernon <rbernon(a)codeweavers.com> AuthorDate: Mon Jun 3 17:48:30 2024 +0200 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Mon Jun 3 23:24:59 2024 +0200 winex11: Create a HBITMAP for the allocated surface pixels. dlls/winex11.drv/bitblt.c | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------- 1 file changed, 58 insertions(+), 19 deletions(-) -- 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 17

[Bug 48088] New: DIB engine does not work on a 256-color X server
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48088 Bug ID: 48088 Summary: DIB engine does not work on a 256-color X server Product: Wine Version: 1.5.13 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 65646 --> https://bugs.winehq.org/attachment.cgi?id=65646 Regedit in Xephyr To reproduce, run `Xephyr :1 -ac -screen 800x600x8` in one terminal window and `DISPLAY=:1 wine regedit` in another. The window colors are positively psychedelic. A regression test on a Debian 6.0 Squeeze virtual machine revealed: 33ac850c80634c891b0c157bbffa612f70954a40 is the first bad commit commit 33ac850c80634c891b0c157bbffa612f70954a40 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Sep 6 12:39:34 2012 +0200 winex11: Use window surfaces for rendering top-level windows. It can be disabled by setting "ClientSideGraphics"="n". :040000 040000 704eac5fc311e63d373e399c63a2488a6b3dedca 33fb0e5963c1326f8765334e4714060c89b21b5e M dlls And indeed, creating the registry key "HKEY_CURRENT_USER\Software\Wine\X11 Driver\ClientSideGraphics" with the value "N" or "n" allows the window to be displayed normally (except for some unsightly dithering). -- 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 49933] New: Alt+Tab doesn't work with gog installers
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=49933 Bug ID: 49933 Summary: Alt+Tab doesn't work with gog installers Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rtentser(a)yandex.ru Distribution: --- I need to minimize other windows to see progress. When i try to alttab to an installer i'm getting "00f0:fixme:win:WINNLSEnableIME hwnd 0001011C enable 0: stub!" in terminal. When i try to alttab out of it i'm getting "00f0:fixme:win:WINNLSEnableIME hwnd 0001011C enable -1: stub!" So, i'm guessing, implementing WINNLSEnableIME will 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 74

[Bug 9521] New: Improve appdb screenshot handling
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=9521 Summary: Improve appdb screenshot handling Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: d.c.ddcc(a)gmail.com I would suggest adding a method for maintainers to edit any preexisting image (to focus on only application window, hide personal information in games, etc), show who originally uploaded the image and a text summary of what happened in later revisions, and add the ability to include an image description. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 4

[Bug 53572] New: Misbehaving system tray icons on Wayland session
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=53572 Bug ID: 53572 Summary: Misbehaving system tray icons on Wayland session Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryu.ketsueki(a)outlook.com Distribution: --- This is a bit more complex to explain, as this happens more specifically if you are on a Wayland session desktop. May be a duplicate of 48550 but I decided to drop more of what I could find out. Previously this was reported on KDE's Bugzilla as well and currently there may not be an easy fix on Plasma's side for a number of reasons. First, it may be using a deprecated proxy, XEmbedSNIProxy, which may be supported in X11 in a "very hacky way" as described in the bug report and it is completely unsupported in Wayland. Other apps also have this issue, like Anydesk, but Wine may be used for a lot more so it is more common to see those around. What happens is that, while the icon may appear on the tray, the "interactible" part of the icon is usually on the top left corner of the screen. And if there are many tray icons, only one can be interacted with. The icon itself on the tray is completely static and cannot be interacted with. Gnome does not have a system tray by default, requiring the user to install one through extensions. Every other desktop environment, however, does have a native system tray. Currently, KDE Plasma in the Wayland session is where this issue can be replicated, although I imagine other Wayland implementations such as Sway may also work. There is a known workaround but it is not perfect. Essentially involves terminating the XEmbedSNIProxy process and bringing the tray icons from there into a window with the wmsystemtray command. It is very hacky and far from ideal. If something can be done on Wine's side to try sorting this out, it would greatly improve its usability on Wayland, even without a native Wayland driver. Perhaps a new proxy that works both on X11 and Wayland can replace this old one? -- 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 55775] New: game made from unity is not ingame playing video.
by WineHQ Bugzilla Aug. 4, 2026

Aug. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=55775 Bug ID: 55775 Summary: game made from unity is not ingame playing video. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- Created attachment 75260 --> https://bugs.winehq.org/attachment.cgi?id=75260 console output of game that use mf as video playback There are some various game that use mf in win10 as default. but there are no video when they are using mf as dll to play video, there are video when disable mfplat.dll in winecfg. forcing some of the game back using quartz.dll. Test on game "Night Security" in steam at 3F in game. There are TV on the room. -- 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 48

[Bug 59018] New: Font artifacts on glyphs with overhangs
by WineHQ Bugzilla Aug. 4, 2026

Aug. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=59018 Bug ID: 59018 Summary: Font artifacts on glyphs with overhangs Product: Wine Version: 10.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: gamelaster(a)outlook.com Distribution: --- Created attachment 79757 --> http://bugs.winehq.org/attachment.cgi?id=79757 Images of the issue + PoC patch In the game MTA San Andreas (multiplayer modification for GTA San Andreas), in game chat and other parts using relevant API, some glyphs have leftover artifacts (images in attachment). ---------- User vahook from MTA:SA community was so kind that he investigated this issue and found the root cause, with hacky PoC fix provided. Quoting his explanation: >> The DrawText methods in Microsoft's d3dx9 implementation expect the ExtTextOut functions in GDI to opaque overhangs as well (TTF glyphs with a negative abcC value) when invoked with the ETO_OPAQUE option, as DrawText will use abcA + abcB as the glyph width when copying the rasterized glyphs from a (reused) temporary buffer to a texture. However, the current implementation in NtGdiExtTextOutW opaques out an abcA + abcB + abcC wide box, meaning the background behind overhangs won't be cleared, resulting in artifacts in the font texture from previously rasterized glyphs. In the attachment archive, there are images of the bug, also with image of PoC fix applied. PoC Fix patch is there as well. Additionally, there is font texture dump from the game, which shows that the artifacts are present in the texture. Vahook provided reproduction code as well, which I modified a bit to forcefully use d3dx9_42.dll for successful reproduction. The code can be found here: https://github.com/gamelaster/wine-gdi-font-artifact-repro with prebuilt binaries (built by me) available to be downloaded here: https://github.com/gamelaster/wine-gdi-font-artifact-repro/releases/tag/v1.… . -- 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 42182] New: OUT: isn't supported (custom output device)
by wine-bugs＠winehq.org Aug. 4, 2026

Aug. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=42182 Bug ID: 42182 Summary: OUT: isn't supported (custom output device) Product: Wine Version: 1.8.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: kenorb(a)gmail.com Distribution: --- On Windows, OUT: is the special device and doing: echo test > OUT or: echo test > OUT: would redirect this to output device (by default same as NUL). On Wine, "OUT:" file is created. This should work similar as for CON: (which works fine in Wine): echo test > CON or: echo test > CON: See list of special devices at: http://superuser.com/a/613335 -- 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.

3 4

[Bug 50277] New: Haven intro video does not play
by WineHQ Bugzilla Aug. 4, 2026

Aug. 4, 2026

https://bugs.winehq.org/show_bug.cgi?id=50277 Bug ID: 50277 Summary: Haven intro video does not play Product: Wine Version: 6.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: kai.sterker+wine(a)gmail.com Distribution: --- Created attachment 68825 --> https://bugs.winehq.org/attachment.cgi?id=68825 Debug logs with +mfplat,+gstreamer Upon testing Haven with the builtin media foundation implementation, the following error is logged, the intro movie does not play and the game is stuck at launch: 020c:err:mfplat:media_source_constructor Failed to play source, error 0. 0218:err:mfplat:bus_watch qtdemux0: Internal data stream error. 0218:err:mfplat:bus_watch qtdemux.c(6605): gst_qtdemux_loop (): /GstBin:bin0/GstDecodeBin:decodebin0/GstQTDemux:qtdemux0: streaming stopped, reason error (-5) Debug logs with +mfplat,+gstreamer attached. I'm on Ubuntu 20.04. If I can provide any other useful information please let me know. -- 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 88

[Bug 33634] New: [UWIN] simple ls -l from the UWIN gives a lot of warnings
by wine-bugs＠winehq.org Aug. 4, 2026

Aug. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=33634 Bug #: 33634 Summary: [UWIN] simple ls -l from the UWIN gives a lot of warnings Product: Wine Version: 1.5.30 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: simon.toedt(a)gmail.com Classification: Unclassified Running a simple ls -l from the UWIN (Unix emulation on Windows) toolkit in wine gives a lot of warnings. The goal is to use WINE for automated testing without having to fire up a full blown Windows system each time in VMware or real iron. Steps to test: 1. Install UWIN: > wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…' > wine uwin-base.2013-02-08.win32.i386.exe 2. Run ls -l in wine: wine 'C:\Program Files/UWIN/usr/bin/ls.exe' -l fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 log file write failed -- remaining messages will be to the standard error 2013-05-21+12:43:18 64 2048 1 41 26 0 (UWIN) sid.c:538: SetTokenInformation failed [1:Invalid function] 2013-05-21+12:43:26 64 2048 1 41 26 0 (UWIN) spawnve.c:810: waitmsg: line=894 slot=26 pid=40-2048 ppid=1 state=RUNNING threadid=0 inexec=0x10 fixme:ntdll:NtSetInformationToken unimplemented class 4 2013-05-21+12:43:26 64 2048 1 41 26 0 (ls) sid.c:538: SetTokenInformation failed [1:Invalid function] 2013-05-21+12:43:26 64 2048 1 43 26 0 (ls) sig.c:896: init Global\UWIN.event.init.restart open failed [2:File not found] 2013-05-21+12:43:26 64 2048 1 43 26 0 (ls) sig.c:937: init Global\UWIN.mutex.init.running.38 + Global\UWIN.event.init.restart status=WAIT_FAILED [6:Invalid handle] fixme:console:GetNumberOfConsoleMouseButtons (0x77e528): stub total 201482013-05-21+12:43:26 64 2048 1 41 26 0 (ls) passwd.c:618: getdomainentry \\.\pipe\UWIN.passwd p stoe failed (open pipe) [2:File not found] 2013-05-21+12:43:27 64 2048 1 41 26 0 (ls) passwd.c:618: getdomainentry \\.\pipe\UWIN.group g BUILTIN/Administrators failed (open pipe) [2:File not found] -rwxr-xr-x 1 stoe BUILTIN/Administrators 10315673 Feb 9 09:14 uwin-base.2013-02-09.win32.i386-64 wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work as described in bug 33619. -- 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 17

[Bug 33621] New: [UWIN] ksh93 from UWIN generates a lot of fixme warnings
by wine-bugs＠winehq.org Aug. 4, 2026

Aug. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=33621 Bug #: 33621 Summary: [UWIN] ksh93 from UWIN generates a lot of fixme warnings Product: Wine Version: 1.5.30 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: simon.toedt(a)gmail.com Classification: Unclassified Running ksh93 (Korn Shell 93) from the UWIN (Unix emulation on Windows) toolkit generates a lot of "fixme" warnings and the shell is generally not useable. The goal is to use WINE for automated testing without having to fire up a full blown Windows system each time in VMware or real iron. Steps to test: 1. Install UWIN: > wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…' > wine uwin-base.2013-02-08.win32.i386.exe 2. Run Windows/UWIN version of ksh93: wine64 'C:\Program Files/UWIN/usr/bin/ksh.exe' fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000000, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:advapi:LsaOpenPolicy ((null),0x23f980,0x00000001,0x23f950) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netbios:NetServerEnum Stub ((null) 100 0x23f440 -1 0x23fbb8 0x23fbc8 24 (null) (nil)) fixme:netapi32:NetGetDCName ((null), (null), 0x23f448) stub! fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0xf70850,symt:0xfce150) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x20e2370,symt:0x2140480) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e98,symt:0x2970264) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2943cb0,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e90,symt:(nil)) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x36b3448,symt:0x378fa1c) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743718,symt:0x37781b4) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743658,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x37425a0,symt:0x3754e38) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work as described in bug 33619. IMO the most pressing problems are: 1. fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. 2. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented 3. fixme:netapi32:NetUserGetInfo Level 3 is not implemented 4. fixme:ntdll:NtSetInformationToken unimplemented class 4 5. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented -- 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.

3 12

[Bug 55955] New: some part of the software is black, if I click a line it appears, but only a line, never more than a line
by WineHQ Bugzilla Aug. 3, 2026

Aug. 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=55955 Bug ID: 55955 Summary: some part of the software is black, if I click a line it appears, but only a line, never more than a line Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: gerard.labadie(a)sysgroup.fr Distribution: --- Created attachment 75543 --> https://bugs.winehq.org/attachment.cgi?id=75543 Display of Captvty 3 on Windows The resolution of the bug https://bugs.winehq.org/show_bug.cgi?id=55742 allows to launch successfully Captvty V3, but part of the window is black and impossible to read I have attached the file Captvty-3-display-ok, when running on Windows which shows a normal display and the file Captvty-linux which shows that the resume of the replay is Ok, but not the lines with the names of the replays. reproducer have wine 8.20 or after, the latest winetricks create a directory .captvty_V3 download the zip from v3.captvty.fr unzip it to .captvty_V3 export WINEARCH=win64 export WINPREFIX=~/.captvty_V3 wineboot -u winetricks -q dotnet48 corefonts gdiplus fontsmooth=rgb vlc win7 mkdir temp cd temp cabextract ~/.cache/winetricks/win7sp1/windows6.1-KB976932-X64.exe cp -rf ./x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2/comctl32.dll ~/.wine_captvty_V3/drive_c/windows/syswow64/comctl32.dll cd ~ rm -rf temp launch it with wine .captvty_V3/Captvty.exe I noticed from the command line the messages fixme:uxtheme:BeginBufferedPaint painting parameters are ignored and 0024:fixme:uxtheme:AllowDarkModeForWindow 00030048 1: stub using winecfg I tried various options for comctl32, any option with "native" works (with the black display), any other option crashes the sofware. in https://forum.winehq.org/viewtopic.php?t=38088 somebody commented I don't know how to fix the black display, but I strongly believe this might be due to using the native comctl32 (which is not really a good thing). I think it might be a good idea to open a bugreport about the application not being able to load builtin comctl32, maybe one of the developers has an idea how to fix this, and maybe this "black display" issue might be solved then as well -- 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 21

[Bug 59414] New: AAC error when playing Unity game videos
by WineHQ Bugzilla Aug. 3, 2026

Aug. 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59414 Bug ID: 59414 Summary: AAC error when playing Unity game videos Product: Wine Version: 11.2 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: msdmo Assignee: wine-bugs(a)list.winehq.org Reporter: afifsworld132(a)gmail.com Created attachment 80382 --> http://bugs.winehq.org/attachment.cgi?id=80382 Video playback after enabling DisableGstByteStreamHandler System: MacBook Pro M1 (2020), macOS 14.1.1, Wine Staging 11.2, DXMT 0.71 (I downgraded from 0.73 due to it having Shared Handle issues) Related to MR 6442 When playing a Unity game (in this case, Hollow Knight Silksong), any video renders unsmoothly and poorly compared to what it should look like. I see the following in the logs: (wine:64457): GStreamer-Video-CRITICAL **: 08:23:38.263: gst_video_info_from_caps: assertion 'gst_caps_is_fixed (caps)' failed 058c:fixme:mfplat:media_source_get_service_GetService Unsupported service {dd0ac3d8-40e3-4128-ac48-c0add067b714}. But this is an old issue. And only sometimes video playback works just fine. When enabling DisableGstByteStreamHandler OR using MR 5988, I get the following error with no video/audio: ``` 0:00:00.651204750 65255 0x600001b395c0 ERROR aacparse gstaacparse.c:355:gst_aac_parse_sink_setcaps:<aacparse0> Need codec_data for raw AAC 0:00:00.651291416 65255 0x600001b395c0 ERROR aacparse gstaacparse.c:355:gst_aac_parse_sink_setcaps:<aacparse0> Need codec_data for raw AAC 0:00:00.653903500 65255 0x600001b395c0 ERROR WINE unixlib.c:227:link_element_to_sink: Failed to find src pad compatible to <'':sink> on <audioresample1>. 0:00:00.654040541 65255 0x600001b395c0 ERROR WINE wg_transform.c:788:wg_transform_create: Failed to create winegstreamer transform. ``` Full logs added with GST_DEBUG=3 and logging channel mfplat. -- 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 57291] New: SILENT HILL 2 (2024) has rendering issues in DX11 mode
by WineHQ Bugzilla Aug. 3, 2026

Aug. 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=57291 Bug ID: 57291 Summary: SILENT HILL 2 (2024) has rendering issues in DX11 mode Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 77231 --> https://bugs.winehq.org/attachment.cgi?id=77231 output wine-9.19-30-g5b06663a59d -- 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 58180] New: CaptureAge 1.17.1: fails to GetSharedHandle
by WineHQ Bugzilla Aug. 2, 2026

Aug. 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=58180 Bug ID: 58180 Summary: CaptureAge 1.17.1: fails to GetSharedHandle 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: eabesea(a)rambler.ru Distribution: Ubuntu Created attachment 78475 --> http://bugs.winehq.org/attachment.cgi?id=78475 captureage log When I run CaptureAge, it fails to start rendering. It appears that the fail is because dxgi_resource_GetSharedHandle is not implemented. I'm not attaching full wine terminal output since it's very large and appears to be mostly irrelevant. -- 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 58657] New: Reference to swapchain not removed when swapchain is destroyed
by WineHQ Bugzilla Aug. 2, 2026

Aug. 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=58657 Bug ID: 58657 Summary: Reference to swapchain not removed when swapchain is destroyed Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: gingyu02(a)gmail.com Distribution: --- While using OpenGL renderer,when a swapchain is removed,some references to it (such as surfaces,contexts) are not removed,resulting in a null pointer error when calling related fuctions. -- 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 1

[Bug 45364] New: Frostpunk
by wine-bugs＠winehq.org Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=45364 Bug ID: 45364 Summary: Frostpunk Product: Wine Version: 3.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hewanci(a)gmail.com Distribution: --- Frostpunk is so dark that it's unplayable due to not being able to see what's happening. Steam version Staging 3.10 Arch Linux There is already a bug about glitches but I doN't know how related that is: bug 45098 -- 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.

3 29

[Bug 43474] New: Tsukihime fails fullscreen -> windowed transition
by wine-bugs＠winehq.org Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=43474 Bug ID: 43474 Summary: Tsukihime fails fullscreen -> windowed transition Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zaplo00(a)mailfence.com Distribution: --- Switching from fullscreen to windowed mode causes empty window or unmapped window that needs to be restored with xdotool windowmap. Tsukihime can be started in windowed mode but switching to fullscreen and back breaks it (fullscreen always works). Log with fullscreen -> windowed in main menu (after 2 splash screens) is attached, maybe this piece is the culprit?. trace:d3d:context_acquire device 0x188d08, texture (nil), sub_resource_idx 0. trace:d3d:context_enter Entering context 0x1809f8, level 1. warn:d3d:context_set_gl_context Failed to set pixel format 5 on device context 0x17004a. warn:d3d:context_set_gl_context Failed to make GL context 0x61000 current on device context 0x17004a, last error 0. warn:d3d:context_set_gl_context Trying fallback to the backup window. trace:d3d:swapchain_get_backup_dc Creating the backup window for swapchain 0x182cf0. -- 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.

3 10

[Bug 42084] New: Chessmaster 9000 "File Open" dialog does not list subdirectories
by wine-bugs＠winehq.org Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=42084 Bug ID: 42084 Summary: Chessmaster 9000 "File Open" dialog does not list subdirectories Product: Wine Version: 2.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bkbk9(a)yahoo.ca Distribution: --- The "File Open" dialog in Chessmaster 9000 doesn't seem to be able to browse or go down into subdirectories of the current dir, for example when trying to load a wallpaper, an opening book or a chess engine into the game. When the dialog is launched, it won't list any subdirectories, you can only go up to the parent but then you cannot navigate back down, the child directory wouldn't be listed in the box. Likewise if you start at the root (C:\ or D:\). -- 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 58692] New: Incorrect owner-owned windows z-order support
by WineHQ Bugzilla Aug. 2, 2026

Aug. 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=58692 Bug ID: 58692 Summary: Incorrect owner-owned windows z-order support Product: Wine Version: 10.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: goltsov(a)imedis.ru Distribution: --- I create two WS_OVERLAPPED or WS_PPUP (not having WS_CHILD!) windows, one is owned by another: hwnd1 = CreateWindow(....., 0, .....); hwnd2 = CreateWindow(....., hwnd1, .....); In Windows hwnd2 is allways placed over hwnd1 and hides when hwnd1 is minimized. In Wine itself (when graphics options do not allow Window Manager to arrange and decorate Wine windows) hwnd1 and hwnd2 act as windows of the same level: when hwnd1 is activated it is displayed over hmnd2 and vise versa - WHY?! This is the basic windows behaviour, why it is incorrect? If Window Manager is allowed to manage&decorate Wine windows, the behaviour is more similiar to one under native Windows, but with another problems: - "minimize" buttons of all windows are hidden for some unknown reason... - if we have hwnd2 and hwnd3 as owned windows of hwnd1, and hwnd1, then hwnd2, then hwnd3 are activated - and hwnd3 is closed - hwnd1 is activated instead of previously active hwnd2 - differs from native Windows behaviour. Linux Minth dated summer 2025 -- 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 1

[Bug 57519] New: FL Studio 24.2: Slow down and eventual freeze when dragging or with popup menus
by WineHQ Bugzilla Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=57519 Bug ID: 57519 Summary: FL Studio 24.2: Slow down and eventual freeze when dragging or with popup menus Product: Wine Version: 10.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marcelohdez.inq(a)gmail.com Distribution: --- Created attachment 77557 --> https://bugs.winehq.org/attachment.cgi?id=77557 console output of running FL64.exe with wine When using FL Studio 24.2 (new prefix, with .NET installed by Mono Installer, just installed FL's free trial with default options) when i attempt to drag plugin into the channel rack there is a slow down and eventual "This app is not responding" popup. Otherwise, clicking the + on the channel rack in order to add a plugin without dragging, the popup experiences the issue. GNOME 47.1 on Fedora 41, Framework 13 using 150% scaling (NOT using xwayland-native-scaling, so blurry) using Wine's staging binary: `winehq-staging` Additional info: Occurs in Fedora's wine as well (9.15) -- 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 1

[Bug 56028] New: Yakuza 0 not launching on Mac 10.14 with Wine
by WineHQ Bugzilla Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=56028 Bug ID: 56028 Summary: Yakuza 0 not launching on Mac 10.14 with Wine Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dariooliviero09(a)gmail.com Created attachment 75673 --> https://bugs.winehq.org/attachment.cgi?id=75673 Here is the error message I don't know much when it comes to Wine, I installed the latest version the site gave me for MAC. In fact, wine's settings should be the default ones, running a Windows 10 system. For a offline single player game such as Fallout New Vegas, Wine worked pretty well. Thanks to that, I decided to try a newer game: Yakuza 0. After having bought it on GOG.com, I tried running the .exe file to no avail. I admit that I didn't spot the issue as I am a bit clueless when it comes to wine, but I should've attached the error message with this. What do I have to do? Thank you in advance -- 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 51316] New: Office 2010 user form resize bug
by WineHQ Bugzilla Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=51316 Bug ID: 51316 Summary: Office 2010 user form resize bug Product: Wine-staging Version: 6.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yuri6037(a)yuristudio.net CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- When you attempt to resize a user form on an EXCEL macro in both O2007 and O2010 the window freezes and you have to open back the user form. However when you change the value of "width" and "height" manually it does seem to work. This happens on both NVIDIA graphics and Intel Graphics no idea about AMD but I expect the same bug. When running EXCEL from terminal, I can see two fixme logs that occurs everytime I click on the corners of a user form: 0154:fixme:msimtf:ActiveIMMApp_OnDefWindowProc Stub (000C0156 47 0 21eaa4) 0154:fixme:msimtf:ActiveIMMApp_OnDefWindowProc Stub (000C0156 3 0 405ed) This occurs when I release the mouse button: 0154:fixme:msimtf:ActiveIMMApp_OnDefWindowProc Stub (000C0156 47 0 21eaa4) 0154:fixme:msimtf:ActiveIMMApp_OnDefWindowProc Stub (000C0156 3 0 4061f) -- 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 46201] New: Xenia fails to initialize graphics pipeline
by wine-bugs＠winehq.org Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=46201 Bug ID: 46201 Summary: Xenia fails to initialize graphics pipeline Product: vkd3d Version: 1.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: chridye(a)gmail.com Distribution: --- Created attachment 62874 --> https://bugs.winehq.org/attachment.cgi?id=62874 backtrace from today (nov 26 2018) the latest build of xenia can be found at https://ci.appveyor.com/api/projects/benvanik/xenia/artifacts/xenia-d3d12.z… I got this error in the terminal window: vkd3d_dxbc_compiler_get_register_info: Assertion `reg->idx[0].offset < compiler->temp_count' failed. A quick search on google says this was some graceful way of dealing with unimplemented registers. That change was proposed on Jan 9. http://wine.1045685.n8.nabble.com/PATCH-vkd3d-1-7-libs-vkd3d-shader-Handle-… The version of vkd3d I'm using was built from source using a commit from today (nov 26). I'm on ubuntu 18.10 without vkd3d installed via package manager. wine was ran in 64-bit mode and was also built from source today after doing a `git pull`. The exact command I ran was `wine64 xenia.exe.` I have attached the back trace. -- 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.

3 9

[Bug 46003] New: glibc (libpthread.so.0) crashes 64-bit FPUs and freezes screen in 32-bit applications
by wine-bugs＠winehq.org Aug. 2, 2026

Aug. 2, 2026

https://bugs.winehq.org/show_bug.cgi?id=46003 Bug ID: 46003 Summary: glibc (libpthread.so.0) crashes 64-bit FPUs and freezes screen in 32-bit applications Product: Wine Version: 3.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine.fixes(a)gmail.com Distribution: --- The 64-bit glibc libraries (specifically, libpthread.so.0 - version 2.27) apparently use the sysenter / syscall assembly commands in order to initiate the __libc_write() system calls, rather than the "int 0x80" command that the 32-bit libraries use. This is fine for 64-bit Windows applications in Wine, but seems to cause a CPU exception when running certain 32-bit applications on a 64-bit Intel CPU (such as the Core i5), which - in turn - seems to cause stack underflow and NaN errors on the FPU unit under certain circumstances, thus preventing the screen from updating whenever floating point calculations are required in order to calculate the final screen position. It can also cause unhandled exceptions and cause the application to terminate entirely in some applications. I am yet to identify any commercial applications which suffer from this problem, but I have written several simple SDL and Win32 graphical programs (compiled with version 0.9.25 of the TCC Tiny C Compiler) which demonstrate the effects. I have provided sample code of one such application below. This problem also appears to manifest on 64-bit Intel CPUs even when using 32-bit operating systems (such as Ubuntu 18.04-i386), but I can confirm from testing that the 32-bit QEMU virtual machine appears to be unaffected (and, presumably, so are 'real' 32-bit CPUs too). I have been told that 64-bit AMD CPUs (unlike 64-bit Intel CPUs) will not trigger an error when using sysenter / syscall in 32-bit mode, but I am yet to confirm this as I currently only have access to Intel CPUs. Incidentally, I believe that Intel themselves advise against sysenter / syscall in 32-bit mode. I have been able to temporarily fix the problem from within Wine by calling the assembly command "fninit" (which resets the FPU) at the start of the DC_UpdateXforms() function in dlls/gdi32/dc.c, or by calling the "fninit" command from within the application (or, in some circumstances, simply moving the window across the screen), but obviously it would be preferable to fix the error at source from within the glibc libraries... I realise that this is not an error with the Wine source code itself per se, but I have registered it here in case anybody else encounters the same problem in future. SAMPLE CODE (Note: This code requires the 32-bit v.0.9.25 or v.0.9.24 version of the TCC Tiny C Compiler, as the error does not appear to manifest on newer versions) This simple program should display a window which changes colour between red, green, and blue every 0.5 seconds on Windows; however, when run from within Wine on 64-bit Intel CPUs, it appears to freeze on the first colour due to the FPU encountering an error during the __libc_write() routine #include <windows.h> #include <string.h> MSG msg; WNDCLASS wc; HWND hwnd; BITMAPINFO bmp = { { sizeof(BITMAPINFOHEADER), 400, 400, 1, 32 } }; unsigned char *pBits = NULL; HDC hdc, compatibleDC; HBITMAP dib_section; float f = 1.0f; unsigned char color[3][4] = { {255, 0, 0, 255}, {0, 255, 0, 255}, {0, 0, 255, 255} }; unsigned char current_color = 0; unsigned int i; int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow) { ZeroMemory(&wc, sizeof wc); wc.hInstance = hInstance; wc.lpfnWndProc = (WNDPROC)DefWindowProc; wc.lpszClassName = "Test App"; if (RegisterClass(&wc) == FALSE) return 0; hwnd = CreateWindow("Test App", "Test App", WS_OVERLAPPEDWINDOW|WS_VISIBLE, CW_USEDEFAULT, CW_USEDEFAULT, 400, 400, 0, 0, hInstance, 0); hdc = GetWindowDC(hwnd); compatibleDC = CreateCompatibleDC(hdc); dib_section = CreateDIBSection(NULL, &bmp, DIB_RGB_COLORS, (VOID**)&pBits, NULL, (DWORD)NULL); SelectObject(compatibleDC, dib_section); while(TRUE) { while(PeekMessage(&msg,NULL,0,0,PM_REMOVE)) { if (msg.message == WM_QUIT) break; TranslateMessage(&msg); DispatchMessage(&msg); } /* The two float operations below will trigger the error */ f += 1.0f; f -= 1.0f; for(i=0; i < (400 * 400 * 4); i+=4) memcpy(&pBits[i], &color[current_color][0], 4); /* If called here, the "fninit()" assembly routine will reset the FPU and enable the screen to update */ // __asm__ volatile ("fninit"); BitBlt(hdc, 0, 0, 400, 400, compatibleDC, 0, 0, SRCCOPY); current_color++; if (current_color >= 3) current_color = 0; Sleep(500); } return msg.wParam; } -- 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 1

[Bug 24505] New: Plants vs Zombies: Low FPS on seeds menu
by wine-bugs＠winehq.org Aug. 2, 2026

Aug. 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=24505 Summary: Plants vs Zombies: Low FPS on seeds menu Product: Wine Version: 1.3.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: adys.wh(a)gmail.com The seeds menu (presented at the start of each game) in Plants vs Zombies GOTY edition (Steam) makes the game lag noticeably. nvidia 9800gtx+ / 260.xx drivers (official binaries) / xorg 1.9 Happens both on fullscreen and windowed, only tested in virtual desktop. No relevant console output. -- 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.

3 29

[Bug 11412] New: Photoshop CS2: Strange behaviour of window overlays
by wine-bugs＠winehq.org Aug. 2, 2026

Aug. 2, 2026

http://bugs.winehq.org/show_bug.cgi?id=11412 Summary: Photoshop CS2: Strange behaviour of window overlays Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pascal.duersteler(a)gmail.com Created an attachment (id=10543) --> (http://bugs.winehq.org/attachment.cgi?id=10543) Splashscreen and toolbar Windows overlaying strange in CS2 with Wine 0.9.54, see Screenshots for details. Examples for two cases as attachments. Splashscreen overlays every other application like terminal, firefox, ...(funky background is from photoshop main window) The toolbar on the left side is from Photoshop CS2 which is opened fullscreen but overlayed by ImageReady CS2 » Photoshop toolbar overlays everything other Also when working with more than one image, clicking on another image window in photoshop sets it between otehr windows instead of setting it into foreground which is very annoying -- 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.

3 27

[Bug 18715] New: No statusbar in Notepad
by wine-bugs＠winehq.org Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=18715 Summary: No statusbar in Notepad Product: Wine Version: 1.1.22 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: Eldmannen+wine(a)gmail.com The Notepad that comes with Wine has no statusbar. -- 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.

3 10

[Bug 21278] New: python's test_zipimport_support test fails
by wine-bugs＠winehq.org Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=21278 Summary: python's test_zipimport_support test fails Product: Wine Version: 1.1.35 Platform: x86 URL: http://www.python.org OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=25590) --> (http://bugs.winehq.org/attachment.cgi?id=25590) test output Install python and run: wine 'c:\Python31\python.exe' -m test.test_zipimport_support test_doctest_main_issue4197 (__main__.ZipSupportTests) ... Expected line File "C:\windows\temp\tmppzq0bh\script.py", line 2, in __main__.Test Got stdout: ********************************************************************** File "C:\windows\temp\tmppzq0bh\script.py", line 2, in __main__.Test Failed example: 'line 2' Expected nothing Got: 'line 2' Full output attached. Vincent wrote in the wiki that somehow a 'C:' was changed to a 'c:'. -- 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 8

[Bug 56739] New: Alchemy is rotated 90°
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

https://bugs.winehq.org/show_bug.cgi?id=56739 Bug ID: 56739 Summary: Alchemy is rotated 90° Product: Wine Version: 9.8 Hardware: x86-64 URL: https://alchemy.software.informer.com/download/ OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: zzhang(a)codeweavers.com Regression SHA1: 4a330b29212402b9700828be82939112bd11a786 Distribution: Ubuntu Created attachment 76518 --> https://bugs.winehq.org/attachment.cgi?id=76518 Screenshot The game Alchemy is rotated 90°. A bisect points to: 4a330b29212402b9700828be82939112bd11a786 is the first bad commit commit 4a330b29212402b9700828be82939112bd11a786 Author: Zhiyi Zhang Date: Tue Sep 22 15:02:24 2020 +0800 winex11.drv: Support display orientations for XRandR 1.4 display settings handler. Running in an emulated desktop works around this. https://alchemy.software.informer.com/download/ $ sha1sum alchemysetup-en.exe 2fa2bd427e79b7fb585d090891ae368b0cea0156 alchemysetup-en.exe $ xrandr --version xrandr program version 1.5.1 Server reports RandR version 1.6 -- 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 55958] New: [Debian-based]　wiki.winehq.org/Regression_Testing - instructions do not work on modern distros
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

https://bugs.winehq.org/show_bug.cgi?id=55958 Bug ID: 55958 Summary: [Debian-based]　wiki.winehq.org/Regression_Testing - instructions do not work on modern distros Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: NM64+bugs.winehq.org(a)PM.me Distribution: --- Created attachment 75550 --> https://bugs.winehq.org/attachment.cgi?id=75550 video demonstration on Linux Mint 21.2 The instructions provided on wiki.winehq.org/Regreesion_Testing for Debian-based distros seem to not be functional on modern Debian-based distros. See the attached video for a demonstration on the live ISO of Linux Mint 21.2 Cinnamon (and, while not shown in the video, I get the exact same result when trying this on an actual installation of Linux Mint 21.2 rather than using a live ISO session) -- 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 40401] New: Built-in services do not run on first boot
by wine-bugs＠winehq.org July 31, 2026

July 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=40401 Bug ID: 40401 Summary: Built-in services do not run on first boot Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ariscop(a)gmail.com Distribution: --- When running on an empty prefix, services.exe does not launch any services For applications this isn't an issue, however it does prevent wine services services from starting, such as plugplay.exe services.exe seems to be launched before the registry is populated, causing this bug -- 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 1

[Bug 44351] New: [Feature Request] Test Result Draft
by wine-bugs＠winehq.org July 31, 2026

July 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=44351 Bug ID: 44351 Summary: [Feature Request] Test Result Draft Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: asembus(a)gmail.com Distribution: --- i thought it would be nice to have test result draft system in appdb just like in blog service. Why ? because IMO testing an app need a lot of *click and some misclick will deliver me to another page and lost all my progress. and sometime where i don't have stable internet to test a game i would like try every offline feature first and test it again when i got more reliable connection. Thank you for keep working on this awesome project. -- 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 7

[Bug 25229] New: rejected test cases never go back to queue
by wine-bugs＠winehq.org July 31, 2026

July 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=25229 Summary: rejected test cases never go back to queue Product: WineHQ Apps Database Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Severity: major Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: virtuousfox(a)gmail.com when test case is rejected instead of outright deleted it does not go back into queue to be reviewed even after being edited by submitter. this issue was discussed sometime year or two ago but apparently never was fixed. example here: user have submitted result and it got rejected for better detailing, it was edited by submiter and mail notification was sent to me. "test result" is http://appdb.winehq.org/objectManager.php?sClass=version&iId=4976&iTestingI… but it not anywhere in my queue list. i want to reject it second time anyway since submitter didn't bothered to read damn notes and howtos at app test page again or look at other, proper submits but i can't even do that now since it's not in queue and i can't do anything with it. -- 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 21

[Bug 25699] New: The URL in the "Test Results submitted" email does not show the Test Results
by wine-bugs＠winehq.org July 31, 2026

July 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=25699 Summary: The URL in the "Test Results submitted" email does not show the Test Results Product: WineHQ Apps Database Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Severity: minor Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alexandru.balut(a)gmail.com I got an email about Test Results submitted for a (new) version of Total Commander (http://appdb.winehq.org/objectManager.php?sClass=application&iId=614) SUBJECT: [AppDB] Test Results submitted for version 7.56a of Total Commander (a.k.a. Windows Commander) by StefanDe BODY: Test Results submitted for version 7.56a of Total Commander (a.k.a. Windows Commander) by StefanDe ------------------------------------------------------- http://appdb.winehq.org/objectManager.php?sClass=version&iId=22423&iTesting… This test data has been queued. [...] To be honest, I don't know why I got this email, maybe because I'm a maintainer or I monitor version 7.50a.. The problem is that I cannot view these "Test Results", the AppDB URL from the email, which is supposed to do this, shows: Queued Entry This entry is currently queued, and may not be visible to all users. -- 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 4

[Bug 57537] New: Steuersparerklärung 2024 fails to install
by WineHQ Bugzilla July 31, 2026

July 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=57537 Bug ID: 57537 Summary: Steuersparerklärung 2024 fails to install Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Found while testing a report from the forums: https://forum.winehq.org/viewtopic.php?t=39775 Ran in a clean WINEPREFIX, used trial version and express installation. It gives a messagebox with > Die Installation von >>Steuersparerklärung 2024<< konnte nicht durchgeführt werden! Prüfen Sie bitte, ob die notwendigen Installationsvoraussetzungen erfüllt sind Translated: The installation of >>Steuersparerklärung 2024<< could not be completed! Please check whether the necessary installation requirements are met -- 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 15

[Bug 59333] New: VNyan leaks memory (race in __wine_syscall_dispatcher $rsp switching breaks Unity GC)
by WineHQ Bugzilla July 31, 2026

July 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=59333 Bug ID: 59333 Summary: VNyan leaks memory (race in __wine_syscall_dispatcher $rsp switching breaks Unity GC) Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: lina(a)lina.yt Distribution: --- Created attachment 80270 --> http://bugs.winehq.org/attachment.cgi?id=80270 Debug & gdb logs VNyan (https://suvidriel.itch.io/vnyan) under recent versions of Wine starts leaking memory at a random time (from minutes to hours after startup). It took a few days of debugging and reverse engineering, but I tracked this down to an issue with Unity's GC observing a weird stack switch in Wine. For reference, Proton 8-5 seems to be fine and GE Proton 10-15 triggers the problem. The problem reproduces with plain `wine-11.0 (Staging)` (wine-11.0-2.fc43.x86_64 from Fedora 43), which is what I used for the traces in this bug. This is the Win32 threads code in the Unity fork of bdwgc: https://github.com/Unity-Technologies/bdwgc/blob/unity-master/win32_threads… Normally, bdwgc will use SuspendThread() on all application threads (see GC_suspend()) and then call GetThreadContext() to retrieve the thread context. It then uses the sp value to determine which stack segment to mark as roots for GC. The logic is complex and there is a safety check in case sp is out of bounds (then it collects the whole stack). However, on line 1695 above, sp is blindly subtracted from thread->stack_base and used to compute the stack usage in bytes, without any bounds checks. This means that when sp ends up above the stack, the subtraction overflows and returns a bogus huge stack size. This ends up throwing off the GC collection threshold, and the GC never runs again. During a normal stop-the-world GC ([1] in vnyan_debug.txt), all threads are stopped with $rip in Windows code (0x00006fffffxxxxxx) (other than the main thread which is in 0x000000018xxxxxx because I patched the Mono DLL to not relocate, for consistent debugging). Most threads are in NtWaitForSingleObject or NtWaitForAlertByThreadId, a couple in NtDelayExecution/NtNotifyChangeKey/NtUserMsgWaitForMultipleObjectsEx/NtWaitForMultipleObjects, and two threads in a mmdevapi wine_unix_call(). When the bug occurs, one thread is caught in the middle of UNIX code ([2] in vnyan_debug.txt). The stack pointer changes from this (pre-bug): Thread 82 (Thread 32.0x2c0): $201 = 0x7a8bf3e8 To this (during bug): Thread 82 (Thread 32.0x2c0): $295 = 0x12938eab0 The GC logs this warning (needs patches to enable debug logs): --> Marking for collection #2607 after 3617216 allocated bytes Marked from 150 dirty pages GC Warning: Thread stack pointer 000000012938EAB0 out of range, pushing everything Pushed 34 thread stacks And then the GC stops working. In the particular repro logged, rip is pointing here in __wine_syscall_dispatcher (it's usually within a few instructions of this area): https://github.com/wine-mirror/wine/blob/db11d0fe6a169c457e23d007e20404643d… This means that is_inside_syscall() returned false and allowed the thread state to be captured directly from native thread state. This is defined as: static inline BOOL is_inside_syscall( ULONG_PTR sp ) { return ((char *)sp >= (char *)ntdll_get_thread_data()->kernel_stack && (char *)sp <= (char *)get_syscall_frame()); } Just a few lines before the instruction the thread was stopped in: "leaq 0x70(%rcx),%rsp\n\t" /* %rsp > frame means no longer inside syscall */ Indeed, %rsp as seen by the user app is 0x70 into syscall_frame (which is 0x12938ea40). Later in the function the stack is switched to the proper user stack: /* switch to user stack */ "movq 0x88(%rcx),%rsp\n\t" I believe when a thread is stopped in the entire range between those two instructions, user code can observe %rsp set to a bogus value that should not be possible. This code was moved around by commit 245e8cedf059 and previously introduced by 0a5f7a71036. I'm not sure why %rsp is being set to point into &frame->rip instead of simply restoring it to the user stack pointer earlier. -- 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 46

[Bug 16147] New: MSN Messenger 7.0: Webcam doesn't work
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=16147 Summary: MSN Messenger 7.0: Webcam doesn't work Product: Wine Version: 1.1.9 Platform: PC URL: http://www.microsoft.com/downloads/details.aspx?familyid =d78f2ff1-79ea-4066-8ba0-ddbed94864fc&displaylang=en OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jaimerave(a)gmail.com If you try to use the webcam through MSN Messenger, you will just see a weird image. The webcam works perfectly in Cheese, so the webcam is working fine. I'm using Ubuntu 8.10 and Wine 1.1.9. I think this lines are related: fixme:qcap:fnCaptureGraphBuilder2_FindInterface (0x1a7f278/0x1a7f278)->({fb6c4281-0353-11d1-905f-0000c0cc16ba}, (null), 0x1a81e60, {c6e13340-30ac-11d0-a18c-00a0c9118956}, 0xbd5158) - workaround stub! fixme:qcap:KSP_Get () Not adding a pin with PIN_CATEGORY_CAPTURE fixme:qcap:fnCaptureGraphBuilder2_Release Release IGraphFilter or w/e fixme:qcap:fnCaptureGraphBuilder2_FindInterface (0x1a7f290/0x1a7f290)->({fb6c4281-0353-11d1-905f-0000c0cc16ba}, (null), 0x1a81e60, {c6e13340-30ac-11d0-a18c-00a0c9118956}, 0xbd5158) - workaround stub! fixme:qcap:KSP_Get () Not adding a pin with PIN_CATEGORY_CAPTURE fixme:qcap:AMStreamConfig_GetNumberOfCapabilities 0x1a81e64: 0x32ebd0 0x32ebdc - stub, intentional fixme:qcap_v4l:qcap_driver_get_prop Not implemented 7 fixme:qcap_v4l:qcap_driver_get_prop Not implemented 5 fixme:qcap:fnCaptureGraphBuilder2_Release Release IGraphFilter or w/e -- 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.

3 44

[Bug 28457] New: Gecko rendering of Skype login page not rendering correctly
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=28457 Summary: Gecko rendering of Skype login page not rendering correctly Product: Wine Version: 1.3.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: xsist10(a)gmail.com Created an attachment (id=36495) --> (http://bugs.winehq.org/attachment.cgi?id=36495) Wine debug output Gecko rendering of Skype's HTML login page not rendering correctly. No HTML formating or javascript/css applied. Unable to complete login process due to this. I then manually updated gecko to wine_gecko-1.3-x86.msi (from 1.1 which was installed by default) and the issue still remained. -- 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.

3 30

[Bug 32074] New: 1by1 Player: music time indicators too fast
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=32074 Bug #: 32074 Summary: 1by1 Player: music time indicators too fast Product: Wine Version: 1.5.16 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: turbolad995(a)hotmail.co.uk Classification: Unclassified When playing mp3 files in 1by1 Player via Wine, the song time at the bottom is going faster than playback. Also the song progress slider at the top is going faster than playback. This bug has only occurred recently i.e. past few weeks, since I always get the latest development Wine releases with the Ubuntu updates. To reproduce: download 1by1 Player: http://mpesch3.de1.cc/1by1.html and use it to play some mp3 files. You will notice that the song time counter is going too fast, but the songs play at normal speed. -- 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.

3 19

[Bug 39091] New: Installing Lync Web App in Wine/Firefox
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=39091 Bug ID: 39091 Summary: Installing Lync Web App in Wine/Firefox Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: staal1978(a)gmail.com Distribution: --- Lync Web app requires Windows version >7 (set in winecfg) most likely this will be the same for "Skype for Business" web app Visit a page seving an invitation for a Lync meeting (can be found via Google, or if you have your own invitation) Firefox will crash due to unimplemented functions in mfplat.dll Download native mfplat.dll from somewhere and Firefox will not crash and the page will load and allow you to download LWAPlugin32BitInstaller.msi The msi can not be installed: fixme:advapi:RegisterTraceGuidsA (0x6307379f, 0x630b1cf8, {0cfe0455-93ba-440d-a3fe-553973d0b723}, 1, 0x32fc98, (null), (null), 0x630b1d00): stub fixme:advapi:RegisterTraceGuidsA (0x6307379f, 0x630b1d18, {797fabac-7b58-4796-b924-d51178a59ce4}, 1, 0x32fc98, (null), (null), 0x630b1d20): stub fixme:advapi:EventRegister {43d1a55c-76d6-4f7e-995c-64c711e5cafe}, 0x6309ce28, (nil), 0x630b1500 fixme:ntdll:NtLockFile I/O completion on lock not implemented yet err:msi:custom_get_thread_return Invalid Return Code 4447 err:msi:ITERATE_Actions Execution halted, action L"CA_TranslateAllAppPkgs" returned 1603 err:msi:ITERATE_Actions Execution halted, action L"ExecuteAction" returned 1603 fixme:advapi:EventUnregister deadbeef: stub -- 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 33

[Bug 40570] New: Skype 7 - Unhandled exception in thread 9 or Unhandled page fault on read access
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=40570 Bug ID: 40570 Summary: Skype 7 - Unhandled exception in thread 9 or Unhandled page fault on read access Product: Wine Version: 1.9.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rmoisto(a)gmail.com Distribution: --- The latest Skype desktop client for Windows (currently 7.23.0.105) does not work with wine 1.9.9 but works fine with 1.9.7 and 1.9.8. Starting Skype with 1.9.9 spits out various errors. In some instances Skype.exe will go in an infinite loop and the debugger hangs, other times the debugger exists instantly. Exists cleanly: wine: Unhandled exception 0xc0000409 in thread 9 at address 0x115d6b8 (thread 0009), starting debugger... Hangs forever: wine: Unhandled page fault on write access to 0x65756cf1 at address 0x63656ee6 (thread 0009), starting debugger... I can attach more console output if needed. -- 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.

3 9

[Bug 57595] New: Login repeated requested to submit bugs
by WineHQ Bugzilla July 30, 2026

July 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=57595 Bug ID: 57595 Summary: Login repeated requested to submit bugs Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: dav75uk(a)yahoo.co.uk CC: austinenglish(a)gmail.com Distribution: --- It doesn't seem to remember the login session (on firefox at least) when submitting bugs and screenshots. Cookie 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 9

[Bug 39009] New: "Importance" link on bug report form opens in wrong place on fields descriptions page
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=39009 Bug ID: 39009 Summary: "Importance" link on bug report form opens in wrong place on fields descriptions page Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Distribution: --- The fields description page has two sections for Importance. The first one is right below the status definitions table; right below it are the definitions for Priority and Severity (which is what users need to see). The second Importance section is toward the bottom of the page, and it just describes the field as "the combination of its Priority and Severity" without the severity definitions anywhere in sight. Clicking the Importance link on the bug report form opens the page at the second Importance section when it should open at the first one (or even better, at the Severity section, since that's what we really want users to see). The result is that users don't see the actual definitions for severity even if they do bother to click the link. -- 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.

3 5

[Bug 24566] New: bugzilla adds mr.bugs to cc list?
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=24566 Summary: bugzilla adds mr.bugs to cc list? Product: WineHQ Bugzilla Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Bugs start out with Mr. Bugs as the default assignee, which is evidently intended so the mailing list gets copied on all bug changes. That's fine. But under some situations, bugzilla seems to also automatically add mr. bugs to the cc list. For instance, here: http://www.winehq.org/pipermail/wine-bugs/2010-September/251648.html Whereupon Dmitry promptly removed it from the cc: http://www.winehq.org/pipermail/wine-bugs/2010-September/251690.html Austin verified that this had been done automatically by repeating his component change: http://www.winehq.org/pipermail/wine-bugs/2010-September/251728.html and then removed the extra cc manually in the next change. What's going on here? Should that cc be added automatically or not? -- 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.

3 9

[Bug 41731] New: vb custom control not work
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=41731 Bug ID: 41731 Summary: vb custom control not work Product: Wine-staging Version: 1.9.23 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lokesh.bhandari(a)enjayworld.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- I have a visual basic 6 base application. In application enter key will go cursor to next field in windows and in backspace will go to cursor to previous field in windows. But in wine-staging 1.9.23 and all other version this functionality not work. So please suggest me for this. Download link is below for application. http://piracyfreeos.org/partner/down.php log for application is fixme:winediag:start_process Please report bugs at http://bugs.wine-staging.com (instead of winehq.org) fixme:ntoskrnl:IoGetConfigurationInformation partial stub fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} -- 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.

3 12

[Bug 40421] New: it is the function used by Windows SetFilePointer
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=40421 Bug ID: 40421 Summary: it is the function used by Windows SetFilePointer Product: Wine-staging Version: 1.9.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: p.lemonnier1(a)free.fr CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Using a program published by the Milec company I discovered that a functionality did not work correctly with Wine . According to the editor, it is the function used by Windows "SetFilePointer" which does not detect an anomaly whereas and with wine the software is blocked. I am surprised because wine functions very well with a large number of programs and this software uses only basic functions of Windows. Thank you very much for the interest which you will carry to this anomaly Very sincerely Patrice Lemonnier -- 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 12

[Bug 19800] New: cygwin's tar -cz crashes when run from a shell script
by wine-bugs＠winehq.org July 30, 2026

July 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=19800 Summary: cygwin's tar -cz crashes when run from a shell script Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com To reproduce, create a dummy tar file, e.g. echo foo > foo then create the one-line shell script bad.sh containing tar -czvf foo.tar.gz foo then run bad.sh in a cygwin shell. It crashes, and leaves behind the file tar.exe.stacktrace containing Exception: STATUS_ACCESS_VIOLATION at eip=2D313133 eax=00000000 ebx=36313637 ecx=00851682 edx=FFFFFFFB esi=32313232 edi=39372D31 ebp=38353136 esp=0064C640 program=C:\cygwin\bin\tar.exe, pid 46, thread main cs=0023 ds=002B es=002B fs=0063 gs=006B ss=002B Stack trace: Frame Function Args 12 [main] tar 46 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Switching to bsdtar (another package in cygwin) gives same results, so it's not a bug in tar per se. tar -xz crashes similarly when given a large input file, and when that happens, one also sees 'gzip: stdout: Communication error on send' Found by trying to automate the chromium build setup instructions, http://dev.chromium.org/developers/how-tos/install-gclient -- 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 8

[Bug 59438] New: jscript crashes
by WineHQ Bugzilla July 30, 2026

July 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=59438 Bug ID: 59438 Summary: jscript crashes Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: jscript Assignee: wine-bugs(a)list.winehq.org Reporter: wine(a)ivank.me Distribution: --- When testing out Wine's jscript implementation I came across a couple of code samples where the engine crashes due to a null pointer dereference. One is an example from compat-table (https://github.com/compat-table/compat-table/blob/8f4179ffb5e7a06a12739400f…) ``` function testCode() { try { RegExp.prototype.exec(); return false; } catch(e) {} try { Date.prototype.valueOf(); return false; } catch(e) {} if (![Error, EvalError, RangeError, ReferenceError, SyntaxError, TypeError, URIError].every(function (E) { return Object.prototype.toString.call(E.prototype) === '[object Object]'; })) { return false; } return true; } testCode() ``` This crash can be reproduced with wine's cscript.exe. It crashes both when built from git (revision eaea4240c4efb618be6d20c05f7fc9f3db9a104c) and using wine shipped with Debian (version 10.0~repack-6): ``` $ wine cscript.exe Z:/tmp/misc.prototypes-not-instances.js wine: Unhandled page fault on read access to 00000000 at address 789A1F83 (thread 01e8), starting debugger... WineDbg attached to pid 01e4 ``` Another crash in a tricky String.prototype.replace call: ``` var s6 = "abcdefghij".replace(/(a)(b)(c)(d)(e)(f)(g)(h)(i)(j)/, "$10-$09-$08-$07-$06-$05-$04-$03-$02-$01"); ``` The second crash only happens using 64-bit jscript.dll, not the 32-bit build so won't reproduce with default cscript.exe. I have a custom DLL host and build scripts that build the 64-bit jscript.dll and reproduce this bug: ``` $ git clone https://github.com/ivankra/javascript-zoo.git src && cd src $ REV=eaea4240c4efb618be6d20c05f7fc9f3db9a104c make -C engines/wine sh $ wine /dist/wine-dist/jscript64.exe /zoo/conformance/es3/String.prototype.replace.capture.js wine: Unhandled page fault on read access to FFFFFFFFFFFFFFFF at address 00006FFFFC6BC2C2 (thread 0128), starting debugger... ``` -- 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