- Wine-Bugs - list.winehq.org

[Bug 57958] New: Caps lock issue when holding Caps lock with other key and Caps lock state was already on
by WineHQ Bugzilla Feb. 10, 2026

Feb. 10, 2026

https://bugs.winehq.org/show_bug.cgi?id=57958 Bug ID: 57958 Summary: Caps lock issue when holding Caps lock with other key and Caps lock state was already on Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: daniel.gaba(a)protonmail.com Distribution: --- Hello, most of the time when holding Caps lock with another button game will register double click first on CAPS LOCK. In "Arma 3" and in "Arma: Reforger" CapsLock is used as push to talk button for radio and you are often holding it alongside other buttons. How to reproduce: 1. Caps lock state need to be on. 2. Hold other key, for example W for walking forward 3. Hold CAPS LOCK 4. In Arma 3 it will start broadcasting for ms and stop and after 1s it will start broadcasting again. In Arma: Reforger this will toggle between Squad <-> Platoon radio instead because it detected double click on Caps Lock. Game will ignore you are still holding caps lock. There is small chance that bug will not trigger. There is also possibility that game may mistakenly detect that you are still holding the Caps Lock key after releasing it, causing it to continue broadcasting until you press it again. I don't know how to reproduce this one. This is very common issue for Arma players on Linux. OS: Opensuse Tumbleweed Kernel version: 6.13.6-1-default KDE plasma Version: 6.3.2 Wayland Wine 10.3 but issue also happens on Proton 7,8 and 9 I tested it also with wayland driver and I was not able to reproduce 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.

2 9

[Bug 48874] New: Faststone Image Viewer - pencil colour is black so wrong component
by WineHQ Bugzilla Feb. 10, 2026

Feb. 10, 2026

https://bugs.winehq.org/show_bug.cgi?id=48874 Bug ID: 48874 Summary: Faststone Image Viewer - pencil colour is black so wrong component Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: phil4000n(a)gmail.com Distribution: --- Created attachment 66809 --> https://bugs.winehq.org/attachment.cgi?id=66809 FSViewer 75 pencil colour bug FSViewer75 Wine55 with wine-mono Current behaviour: When using the drawing tools, such as rectangle, lines, etc. it is possible to select the colour of the contour. There is no issue, but with PENCIL Whatever colour you pick, PENCIL stays black. Expected behaviour: Like under Windows, pencil colour must apply. Very strange that only pencil is affected by this bug. Attached: Video to illustrate the 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 8

[Bug 59365] New: d2d1: Text not rendered in VSTGUI applications (Serum2)
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59365 Bug ID: 59365 Summary: d2d1: Text not rendered in VSTGUI applications (Serum2) Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)list.winehq.org Reporter: nen24t(a)gmail.com Distribution: --- Created attachment 80305 --> http://bugs.winehq.org/attachment.cgi?id=80305 d2d1: Force NATURAL rendering mode instead of OUTLINE/ALIASED Xfer Serum2 renders no text or heavily pixelated fonts under Wine. In `dlls/d2d1/device.c`, when `IDWriteFontFace_GetRecommendedRenderingMode()` fails, Wine falls back to `DWRITE_RENDERING_MODE_OUTLINE`. This mode produces empty glyphs with FreeType. Additionally, `DWRITE_RENDERING_MODE_ALIASED` produces unreadable pixelated text. Forcing `DWRITE_RENDERING_MODE_NATURAL` instead fixes both issues. To reproduce: 1. Install Xfer Serum2 via yabridge 2. Load plugin in REAPER 3. Text is invisible or pixelated Tested on Wine 11.1, Ubuntu, X11. Note: This is separate from Bug https://bugs.winehq.org/show_bug.cgi?id=58438 (geometry/bitmap glitches, black boxes). That issue was addressed in Serum 2.0.22 via app-side workarounds. This bug is specifically about DWrite rendering mode selection. Patch attached. -- 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 52838] New: MachStudio Pro renders wrong
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=52838 Bug ID: 52838 Summary: MachStudio Pro renders wrong Product: Wine Version: 7.6 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com Any project is being rendered wrong in MachStudio Pro. The problem is in Wine's D2D1.DLL. When using native Vista's d2d1.dll (7.0.6002.18107 809kb) this issue does not appear. Steps to repro: 1. Run MachStudio Pro 2. Open a project for example by this path \Program Files\StudioGPU\MachStudio Pro\Data\assets\SGPU_MTL_BALL.mab Uploaded two screenshots: Wine's d2d1.dll and native d2d1.dll from Vista. Free GPU MachStudio Pro download link: https://download.cnet.com/MachStudio-Pro/3000-6677_4-75498419.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.

2 7

[Bug 59399] New: Gnome dev sabotage causing crashes
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59399 Bug ID: 59399 Summary: Gnome dev sabotage causing crashes Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: dcrockerjr(a)gmail.com Distribution: --- Created attachment 80361 --> http://bugs.winehq.org/attachment.cgi?id=80361 Sabotaged gnome power menu with a quip where a disable should be and an ineffective screen blank setting A gnome dev [ebassi Emmanuele Bassi GNOME Team] has made it impossible to disable automatic suspend in gnome, see: https://discourse.gnome.org/t/consider-adding-inhibit-suspend-toggle-pill-i… and https://ometer.com/preferences.html His sabotage makes wine games crash after running a while due to his sabotage of the gnome settings menu for automatic suspend making it not only impossible to disable, but also removed the ability to actually disable automatic screen blank and also making it ignore the Automatic screen blank settings so even if you select 15 min it really secretly goes back to 5min. He claims he wants apps like wine to use a inhibition API though that seems like it would hurt non-gnome users who want to limit screen time or something. I am reluctant to suggest humoring him, but if there were an option in wine for gnome users to activate this inhibition API thing it would help ubuntu users and other distros using Gnome play games despite ebassi's sabotage. Sorry, Thank you. -- 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 55364] New: Shadow Empire crashes on startup with an error related to SharpDX and Direct2D.
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=55364 Bug ID: 55364 Summary: Shadow Empire crashes on startup with an error related to SharpDX and Direct2D. Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kindaro(a)gmail.com Distribution: --- _Shadow Empire_ is a computer game. It can be obtained, for example, from Steam or Good Old Games. I installed what I believe to be version 1.21.00. This is the gist of the error message that the game gives me: ``` SharpDX.SharpDXException: HRESULT: [0x88990028], Module: [SharpDX.Direct2D1], ApiCode: [D2DERR_EFFECT_IS_NOT_REGISTERED/EffectIsNotRegistered], Message: Unknown ``` When I run it as `WINEDEBUG=+d2d wine ShadowEmpire.exe`, I see the following warning from Wine: ``` 0114:warn:d2d:d2d_effect_create Effect id {9daf9369-3846-4d0e-a44e-0c607934a5d7} not found. ``` I shall be attaching the full text of the error and Wine's output. My operating system is Arch Linux, recently updated. The failure occurs both with `wine` and `wine-staging`. -- 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 59345] New: Popup menus in audio plugins break for the whole session
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59345 Bug ID: 59345 Summary: Popup menus in audio plugins break for the whole session Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: 96gz52jbf(a)mozmail.com CC: rbernon(a)codeweavers.com Regression SHA1: f24d38e1efe96598918b59ceb268fbfbf17f558d Distribution: --- In many audio plugins popup and dropdown menus work initially but by opening them multiple times they begin to open less and less frequently until clicking on the buttons to open the menus does nothing. The effect then persists across plugins and even newly launched plugins until the window manager is restarted (logging out and logging back in also works). As I was debugging this I did notice that using WINEDEBUG=+relay slowed things down enough for the menus to open again. With yabridge the breakage is reached pretty quickly if the project uses many Windows plugins through Wine. I've been able to consistently reproduce this with the standalone versions Toontrack's plugins (EZBass, EZDrummer 3), which use JUCE although I don't know if that's relevant, by simply clicking on the menus repeatedly. Relatively quickly the clicks seemingly stop working as the menus stop opening. I did regression testing and found out that in the already broken session using Wine 10.4 makes menus open again. The exact commit that results in the menus not working in an already broken session is 30fa691d99df7d6dfe37d16fe708d603919f9fd1. However, reverting it for the Wine 11.1 has no effect and everything remains broken. So I did more regression testing and found out that with Wine 10.16 and a fresh session the breakage never happens. The commit that results in the breakage is f24d38e1efe96598918b59ceb268fbfbf17f558d, which reverted for Wine 10.17 fixes things but not for Wine 11.1. Commit 0a7082d37efba17f5badea361c8727f424192e68 added a condition to f24d38e1efe9 that resulted in a merge conflict so I reverted that as well. With the commits from the previous paragraph reverted, the issue persisted and with more regression testing I discovered that commit c6cab075f512f95b0f350d0d8c51fff3e3c44a9f (related to https://bugs.winehq.org/show_bug.cgi?id=59102) also needed to be reverted. After that the menus open normally and the session-wide breakage doesn't happen. In summary, commits f24d38e1efe96598918b59ceb268fbfbf17f558d and c6cab075f512f95b0f350d0d8c51fff3e3c44a9f result in a session-wide state where the popup menus stop opening entirely in multiple audio plugins. Initially they open normally but by constantly clicking on the menu buttons, they first start to open less reliably until them not opening becomes permanent. Restarting the window manager fixes it. This happens in a KWin Wayland session but not in an X11 session nor did it happen using IceWM. That does mean it could be an issue with XWayland and not Wine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 59398] New: Vulkan child windows not excluded from parent GDI surface clip region
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59398 Bug ID: 59398 Summary: Vulkan child windows not excluded from parent GDI surface clip region Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: dethaway340(a)gmail.com Distribution: --- Created attachment 80359 --> http://bugs.winehq.org/attachment.cgi?id=80359 git format patch Longer explanation in the .patch attachment but TLDR; vkCreateWin32SurfaceKHR → surface added to win->vulkan_surfaces list → update_window_state(hwnd) → [if cross-thread: posts WM_WINE_UPDATEWINDOWSTATE, returns] → get_window_surface(hwnd, ...) → returns NULL (due to window.c change #1) → apply_window_pos(hwnd, ...) → sends SET_WINPOS_PIXEL_FORMAT to server (due to window.c change #2) → server: sets PAINT_HAS_PIXEL_FORMAT on child → server: update_pixel_format_flags() sets PAINT_PIXEL_FORMAT_CHILD on parents → server returns surface_win = parent that owns the GDI surface → update_surface_region(surface_win) → queries server for new surface clip region → server: get_surface_region() → clip_pixel_format_children() subtracts Vulkan child rect → sets XSetClipRectangles on parent's GC, excluding Vulkan child area → Parent GDI flush no longer paints over Vulkan viewport -- 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 59327] New: SketchUp regression in Wine11
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59327 Bug ID: 59327 Summary: SketchUp regression in Wine11 Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: brunojournoud(a)ouvaton.org Distribution: --- SketchUp pro 2025 and 2026 lost their graphical performance (settings values: MSAA: 0 instead of settings values: MSAA: 8) when upgrading Wine-stable10 to Wine-stable11 or wine-staging10.6 until 11.* System Debian GNU/Linux 13 (trixie) Kernel : 6.12.63+deb13-amd64 proc : AMD Ryzen 7 4700U with Radeon Graphics × 8 GPU : Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon Vega Series / Radeon Vega Mobile Series] -- 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 59391] New: Build instructions for Ubuntu has to be updated
by WineHQ Bugzilla Feb. 9, 2026

Feb. 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59391 Bug ID: 59391 Summary: Build instructions for Ubuntu has to be updated Product: WineHQ Gitlab Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: gitlab-unknown Assignee: wine-bugs(a)list.winehq.org Reporter: inferrna(a)gmail.com Distribution: --- I was unable to build wine with 32-bit support following these instructions https://gitlab.winehq.org/wine/wine/-/wikis/Regression-Testing https://gitlab.winehq.org/wine/wine/-/wikis/Building-Biarch-Wine-On-Ubuntu 1. It is impossible to build 32-bit wine on 64-bit Ubuntu, a lot of asm and linker errors 2. 32-bit Ubuntu Noble is broken in both LXC and bootstrap because there is no 32-bit versions of required packages console-tools or kbd. I was succeeded with bootstrap instead of LXC because bootstrap keeps root files after fail, so it is possible to chroot and install 32-bit kbd from Debian stable, then continue normal installation. Also, I was able to build inside 32-bit chroot only with --enable-archs=i386 So the average Ubuntu user can't just do bisecting following these instructions. It needs retesting and review. -- 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