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

[Bug 60168] New: Reget Deluxe - Vertically truncated menu
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=60168 Bug ID: 60168 Summary: Reget Deluxe - Vertically truncated menu Product: Wine Version: 11.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81808 --> http://bugs.winehq.org/attachment.cgi?id=81808 Screenshot Reget Deluxe 5.2: https://www.majorgeeks.com/mg/getmirror/reget_deluxe,1.html Vertically truncated menu -- 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 18790] New: Default search does not include resolved bugs
by wine-bugs＠winehq.org Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=18790 Summary: Default search does not include resolved bugs Product: WineHQ Bugzilla Version: unspecified Platform: PC OS/Version: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P3 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk The default search (the search box at the top of this page) does not include closed bugs (rightly so), but it also does not include resolved bugs. This leads to duplicates that could be avoided. See Bug 18601 - a recent regression that is fixed by the next release, but anyone searching for an open bug for Google Sketchup will not see it unless they choose to run an advanced search, which some users clearly don't. I'm sure this is a simple change to the code. -- 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 60266] New: Window above a full-screen window is drawn behind it
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=60266 Bug ID: 60266 Summary: Window above a full-screen window is drawn behind it Product: Wine Version: 11.14 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: winemac.drv Assignee: wine-bugs(a)list.winehq.org Reporter: realmaitreal(a)deadmail.lat Target Milestone: --- Created attachment 81984 --> http://bugs.winehq.org/attachment.cgi?id=81984 Minimal Win32 reproducer (C source, ~130 lines, no dependencies) Overview A window which the application places above a full-screen window in the Win32 z-order is drawn behind it and is invisible, when the application owns its windows from a common owner window, as Delphi applications do. winemac.drv elevates a full-screen window to NSStatusWindowLevel+1 while the application is active. Reordering or attaching an owned window goes through -[NSWindow addChildWindow:ordered:], which resets window levels. The owner window is not itself full-screen, so it stays at NSNormalWindowLevel, and the attach drops the affected windows to that level. Because the window level dominates the window server ordering, those windows are then ordered behind the full-screen window and are never promoted again by -adjustWindowLevels:, which decides which windows are "in front" from that same ordering. That -addChildWindow: resets a window level is not documented by Apple. Electron saves and restores the parent window's level around the call for this reason: https://github.com/electron/electron/pull/38460 Measured here with CGWindowListCopyWindowInfo(): attaching a newly created dialog also dropped an existing sibling window from level 27 to level 0. Steps to Reproduce Build and run the attached reproducer (about 130 lines, plain Win32): i686-w64-mingw32-gcc -O1 -o repro.exe repro.c -lgdi32 -luser32 -mconsole wine repro.exe It creates four windows, mirroring a Delphi application's arrangement: 1) APP - a 1x1 owner window, created first so it stays at the back and is never elevated (Delphi's hidden TApplication window) 2) MAIN - a full-screen window, owned by APP 3) START - an ordinary window, owned by APP 4) SPLASH - the window which must stay visible, owned by APP Click the WHITE window (SPLASH) so the application becomes active without raising the black full-screen window in the z-order. The program then swaps START and SPLASH in the z-order once per second with SetWindowPos(hwnd, HWND_TOP, ...) and prints the resulting Win32 z-order. Actual Results The white window is invisible while the application is active, although the program reports it as the top of the Win32 z-order: win32: SPLASH > START > MAIN > APP CGWindowListCopyWindowInfo() reports MAIN at window level 26 (NSStatusWindowLevel+1) and SPLASH, START and APP at level 0. All four are on the same Space and all are ordered in; the white window is simply drawn underneath. It reappears as soon as the application is deactivated, and is visible in Mission Control, which ignores window levels. Reproduced on 20 of 20 samples. Expected Results The white window should be drawn over the full-screen one. Windows has no notion of a full-screen window in the z-order. Per "Window Features": "The system maintains the z-order in a single list. It adds windows to the z-order based on whether they are topmost windows, top-level windows, or child windows." "A child window is grouped with its parent in z-order." Position in the z-order is therefore determined by window type, not by a window's size, so a window which happens to cover the screen has no special standing. SetWindowPos() with HWND_TOP "Places the window at the top of the Z order", and after that call the window must not remain obscured. https://learn.microsoft.com/en-us/windows/win32/winmsg/window-features https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setw… Build Date & Hardware wine-11.14, macOS 26.6.2 (Darwin 25.6.0), Apple Silicon running the x86_64 build. -addChildWineWindow:, -setChildWineWindows: and -adjustWindowLevels: are byte-identical in 11.16 and in current master, so those are affected too. Additional Information Found with OMSI 2 (Steam appid 252530): the loading form is invisible for the whole of a map load, leaving a black screen, and the "really quit?" dialog is invisible as well. Both reappear if the application is deactivated and reactivated. The application must be active for the bug to appear, because the elevation only applies while it is. The similar reports Bugzilla suggests (13515, 22944, 31370, 35384, 56021, 58537, 59334) are all on Linux; none is against winemac.drv. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 60265] New: d2d1: ID2D1GeometrySink::Close() never completes on paths with coincident bezier nodes
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=60265 Bug ID: 60265 Summary: d2d1: ID2D1GeometrySink::Close() never completes on paths with coincident bezier nodes Product: Wine Version: 11.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)list.winehq.org Reporter: werner.bundschuh(a)pm.me Target Milestone: --- Distribution: --- Created attachment 81981 --> http://bugs.winehq.org/attachment.cgi?id=81981 Standalone reproducer (build with mingw, see bug description) # d2d1: ID2D1GeometrySink::Close() never completes on paths with coincident bezier nodes ## Summary `d2d_geometry_resolve_beziers()` subdivides overlapping bezier control triangles until they no longer overlap. When the underlying curves genuinely cross -- or when several nodes sit on (nearly) the same coordinates -- subdividing never separates them, and the loop only terminates once the control points become collinear in float precision. Every split appends a segment that is then tested against all earlier ones, so the segment count grows combinatorially. On a real world document this exhausts memory instead of finishing. ## Affected code `dlls/d2d1/geometry.c`, `d2d_geometry_resolve_beziers()`, first phase: /* Split overlapping bezier control triangles. */ while (d2d_geometry_get_next_bezier_segment_idx(geometry, &idx_p)) { d2d_geometry_get_first_bezier_segment_idx(geometry, &idx_q); while (idx_q.figure_idx < idx_p.figure_idx || idx_q.vertex_idx < idx_p.vertex_idx) { while (d2d_geometry_check_bezier_overlap(geometry, &idx_p, &idx_q)) { ... d2d_geometry_split_bezier(geometry, &idx_q or &idx_p); } d2d_geometry_get_next_bezier_segment_idx(geometry, &idx_q); } } Unchanged since 2187a1edb ("d2d1: Split overlapping bezier control triangles.", Henri Verbeet, 2017, Wine 2.15). The only termination condition is in `d2d_geometry_check_bezier_overlap()`: if (d2d_point_ccw(a[0], a[1], a[2]) == 0.0f || d2d_point_ccw(b[0], b[1], b[2]) == 0.0f) return FALSE; That is float exhaustion, not an algorithmic bound. ## Measurements Instrumenting the loop to record the subdivision depth per segment, on the attached reproducer: segments start end max depth avg depth 20 220 1544 25 5.51 40 872 2336 25 3.91 80 3312 14948 25 4.82 160 14144 54057 25 4.18 The maximum depth is exactly 25 in every run -- the point at which halving a control triangle with coordinates around 500 no longer changes the float32 mantissa. The average depth is 4 to 5.5, so only a small tail of pairs runs all the way down; those are the pairs whose curves actually cross. Wall clock for `ID2D1GeometrySink::Close()` on the reproducer, Wine 11.16 release build, measured A/B/A/B interleaved on an otherwise unchanged machine (medians; the two runs per variant agree within 3%): segments unpatched patched factor 20 39.2 ms 20.9 ms 1.87 40 85.1 ms 56.7 ms 1.50 80 3114.2 ms 1844.2 ms 1.69 160 42132.9 ms 28794.4 ms 1.46 Note that the reproducer is dominated by the overlap tests, not by the array shifting, so it mostly exercises the subdivision bound. The array shifting is what dominates in the real world case below, where the unpatched version does not finish at all and no ratio can be given. ## Real world case Affinity Designer 3 (via Wine) freezes when selecting a specific object in a customer document. The object contains a cluster of nodes at practically identical coordinates. Sampled with gdb, 30 samples over three minutes, 100% of the time is in `memmove` reached through: d2d_geometry_sink_Close -> d2d_geometry_resolve_beziers -> d2d_geometry_split_bezier -> d2d_figure_insert_vertex -> memmove The figure had grown to roughly 915,000 vertices and was still growing by about 23,000 per minute after eight minutes; each insertion memmoves 1.3 to 6.5 MB. The operation never completes. ## Two independent problems 1. `d2d_geometry_split_bezier()` inserts into the middle of the figure's vertex, vertex type and control arrays. That is O(n) per split, so the phase is O(splits * vertices) -- this is what dominates in the real world case. The splitting phase only ever reads three points per segment (`d2d_geometry_check_bezier_overlap`, `d2d_geometry_bezier_ccw`), so the array bookkeeping is not needed until the phase ends. 2. The number of splits is not bounded by anything except float precision. ## Reproducer `repro.c` (attached) builds a closed path of N quadratic bezier segments whose control points sit near the centre, so the control triangles overlap, and times `ID2D1GeometrySink::Close()`. No render target is needed. Build with mingw: x86_64-w64-mingw32-gcc -O2 -o repro.exe repro.c -ld2d1 -lole32 -lm ## Notes Also observed while reading this code, not addressed here: the middle loop condition while (idx_q.figure_idx < idx_p.figure_idx || idx_q.vertex_idx < idx_p.vertex_idx) is an OR where lexicographic ordering is intended. It happens to be safe only because q always meets p exactly; the return value of the following `d2d_geometry_get_next_bezier_segment_idx()` is not checked, so if q ever ran past p the loop would index `figures[figure_count]`. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 60264] New: Wine32 FTBFS using clang and --without-mingw
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=60264 Bug ID: 60264 Summary: Wine32 FTBFS using clang and --without-mingw Product: Wine Version: 11.16 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, source Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: imwellcushtymelike(a)gmail.com Target Milestone: --- Distribution: Debian Created attachment 81980 --> http://bugs.winehq.org/attachment.cgi?id=81980 wine-11.16-156-g2ecc2f84b45 logs Trying to build a 32-bit Wine with clang --without-mingw fails, printing hundreds of lines of the type: tmp6a974931/shell32-00000000.spec-00000001.s:42266:10: error: Could not find incbin file 'dlls/shell32/shell32.res' .incbin "dlls/shell32/shell32.res",3114524,1640 ^ tmp6a974931/shell32-00000000.spec-00000001.s:42270:10: error: Could not find incbin file 'dlls/shell32/shell32.res' .incbin "dlls/shell32/shell32.res",3116196,3752 A 64-bit build simply refuses to go ahead ("try installing mingw"), but a new WOW64 build completes without issue. Is this type of build still supported on clang? Workaround is to add -fno-integrated-as to the CFLAGS. -- 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 58040] New: Compiling with clang 20.1.1 results in a lot of mp67e96999/shell32-00000000.spec-00000000.s:32085:10: error: Could not find incbin file 'dlls/shell32/shell32.res' errors when shell32.dll is built.
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=58040 Bug ID: 58040 Summary: Compiling with clang 20.1.1 results in a lot of mp67e96999/shell32-00000000.spec-00000000.s:32085:10: error: Could not find incbin file 'dlls/shell32/shell32.res' errors when shell32.dll is built. Product: Wine Version: 10.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: contact(a)ivanchev.net Distribution: --- Created attachment 78296 --> https://bugs.winehq.org/attachment.cgi?id=78296 Excerpt from the build log Using latest clang (20.1.1) to compile Wine results in weird error about missing incbin file dlls/shell32/shell32.res when shell32.dll is being built although shell32.res is successfully compiled before hand (see log excerpt). -- 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 60259] New: Qt pull-down menus are layered behind main window after interacting with another top-level window in virtual desktop
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=60259 Bug ID: 60259 Summary: Qt pull-down menus are layered behind main window after interacting with another top-level window in virtual desktop Product: Wine Version: 11.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: effects3dee(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81975 --> http://bugs.winehq.org/attachment.cgi?id=81975 Debug log The pull-down menus of Qt applications (in this case Roblox Studio, but I've managed to reproduce this Qt Designer as well) are layered behind the main window after interacting with another top-level window in virtual desktop mode. This can be worked around by either changing the state of the main window (maximized -> windowed or windowed -> maximized) or disabling virtual desktop mode entirely. The way to reproduce this can be found in the bug demonstration, which I will upload shortly. -- 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 60258] New: tuberank jeet bug 2026
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=60258 Bug ID: 60258 Summary: tuberank jeet bug 2026 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: pocomal112(a)codverts.com Target Milestone: --- Distribution: --- I installed on bottle in linux a software by name TUBERANK JEET AI together with the software of windowsdesktop-runtime-10.0.10-win-x64 The whole installation worked smoothly without errors until I saw a problem with the launch. the software didnt launch and no bug report file to show you what bug. please fix it -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 52798] New: Wine32 Configure on x86-64 System Fails due to libdbus 32-bit development files not found
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=52798 Bug ID: 52798 Summary: Wine32 Configure on x86-64 System Fails due to libdbus 32-bit development files not found Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ejmarkow(a)yahoo.com Distribution: --- Created attachment 72178 --> https://bugs.winehq.org/attachment.cgi?id=72178 wine32 config.log When trying to configure Wine32 (on an x86-64 openSUSE Linux system), at the end of the process I'm notified: "configure: libdbus 32-bit development files not found, no dynamic device support." I have all libdbus & related 64 and 32 bit packages installed on my system. The following key fragment appears in the config.log: ----- configure:15903: dbus-1 cflags: -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include configure:15904: dbus-1 libs: -L/usr/lib -ldbus-1 configure:15907: checking for dbus/dbus.h configure:15907: gcc -m32 -c -g -O2 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include conftest.c >&5 In file included from conftest.c:162: /usr/include/dbus-1.0/dbus/dbus.h:29:10: fatal error: dbus/dbus-arch-deps.h: No such file or directory 29 | #include <dbus/dbus-arch-deps.h> | ^~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. ----- Attached is the complete config.log file. -- 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 59769] New: Wine 11.9 FTBFS on Linux aarch64 with Clang: error: call to undeclared library function '_ReadWriteBarrier' with type 'void (void)';
by WineHQ Bugzilla Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=59769 Bug ID: 59769 Summary: Wine 11.9 FTBFS on Linux aarch64 with Clang: error: call to undeclared library function '_ReadWriteBarrier' with type 'void (void)'; Product: Wine-staging Version: 11.9 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: origincode(a)aosc.io CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- With wine-staging patches, Wine 11.9 fails to build on aarch64. Clang defines _MSC_VER when building for Windows [0]. The conditional compilation calls the undefined function `_ReadWriteBarrier`. Build log is attached. [0]: https://clang.llvm.org/docs/MSVCCompatibility.html -- 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