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

[Bug 52838] MachStudio Pro renders wrong

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=52838 --- Comment #6 from Nikolay Sivov <bunglehead(a)gmail.com> --- I was able to reproduce this on Linux with current Wine. However I'm not sure it's necessarily a D2D problem. It is used, but I don't see any rendering attempts with it at all. But I do see some shader processing fixmes. One option is to try with dxvk to compare. -- 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.

Feb. 9, 2026

[Bug 59399] Gnome dev sabotage causing crashes

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59399 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |11.2 CC| |z.figura12(a)gmail.com --- Comment #2 from Zeb Figura <z.figura12(a)gmail.com> --- We use XResetScreenSaver() to prevent sleep when a joystick is in use (though only from dinput so far). There's probably other instances where we could be doing that, but it's not clear. Is XResetScreenSaver() sufficient or does Gnome effectively ignore it? Or, if it is sufficient, do you have a specific instance of an application that inhibits sleep on Windows and not yet on Wine? (I also feel compelled to point out that the merge request linked from that page [1] contains a more detailed argument for the feature you want, and has not been fundamentally rejected in the same way.) [1] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2507 -- 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.

Feb. 9, 2026

[Bug 58913] Photoshop CC interface is broken on recent wine dev

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58913 --- Comment #7 from herobrinecat <noaaweatherradiostatus(a)gmail.com> --- (In reply to Nikolay Sivov from comment #6) > Could you retest with current Wine? It has a fix for AddArc(), so at least > that one should not appear in the logs anymore. Ok, I can try that once I get home and on my computer -- 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.

Feb. 9, 2026

[Bug 59399] Gnome dev sabotage causing crashes

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59399 mata <sutupud(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud(a)yahoo.com --- Comment #1 from mata <sutupud(a)yahoo.com> --- And how should wine know when to use the inhibitor API? It would be the running application that would need to use it. On windows, from what I can see the rough equivalent would be: https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-powe… Looking at dlls/kernel32/powermgnt.c that and the related functions are currently stubs. So maybe it would be possible to implement that windows API using the inhibitor API if available. But even then, the application would need to use ti. In any case, souldn't it be possible to just run the application using systemd-inhibit wine ...application... to force inhibit even if the app doesn't cooperate? -- 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.

Feb. 9, 2026

[Bug 59372] Regression: wine completely broken in the presence of non-graphics gl devices since 11.1

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59372 --- Comment #20 from uvos <devnull(a)uvos.xyz> --- Yes that patch solves 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.

Feb. 9, 2026

[Bug 58913] Photoshop CC interface is broken on recent wine dev

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58913 --- Comment #6 from Nikolay Sivov <bunglehead(a)gmail.com> --- Could you retest with current Wine? It has a fix for AddArc(), so at least that one should not appear in the logs anymore. -- 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.

Feb. 9, 2026

[Bug 55364] Shadow Empire crashes on startup with an error related to SharpDX and Direct2D.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=55364 --- Comment #9 from Nikolay Sivov <bunglehead(a)gmail.com> --- Could you retest with current Wine? We have stubs for many effects now, and we will see what this game needs next. -- 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.

Feb. 9, 2026

[Bug 58913] Photoshop CC interface is broken on recent wine dev

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58913 --- Comment #5 from herobrinecat <noaaweatherradiostatus(a)gmail.com> --- (In reply to Paul Gofman from comment #4) > Likely the added function triggered the use of more (unimplemented) d2d > stuff. Could you please describe how exactly I can get (free demo is best, > or minimal possible purchase) matching version of Photoshop CC, install it > with Wine and reproduce the problem? I used Adobe Photoshop 2024 (25.9 to be specific, it used to be on Creative Cloud's older versions feature before they removed the 2024 versions) to replicate the issue, since the issue didn't appear in 10.12, but did when 10.13 came out. Also, since the free trial generally uses the same thing, the issue should be present on there too (I used DXVK along with 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.

Feb. 9, 2026

[Bug 59323] Guild Wars 2 crashes with Wine 11.1 and Winewayland enabled with dev builds of DXVK (newer than Jan 23rd)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59323 Britt Yazel <bwyazel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Britt Yazel <bwyazel(a)gmail.com> --- This appears to have been fixed with 11.2 with this patch: https://github.com/wine-mirror/wine/commit/6ea70e7d7c5710df325cd66abb30efb1… -- 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.

Feb. 9, 2026

[Bug 59400] New: Minecraft: Story Mode has broken cursor bounding boxes

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59400 Bug ID: 59400 Summary: Minecraft: Story Mode has broken cursor bounding boxes Product: Wine Version: 11.2 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: afifsworld132(a)gmail.com System: MacBook Pro M1 (2020) Wine: Staging. Happening at least since V9.0 Renderer: dgVoodoo 2 to DXMT 0.73 Basically, if I set the resolution to the maximum in MCSM (2880x1800), the cursor becomes smaller, moves slower and importantly the bounding box for the cursor becomes halved such where the bottom-right corner is now situated at the middle of the screen, so the cursor can only go from top-right to middle of the screen. Note this all happens with High Resolution mode on, The cursor's movement speed, bounding box and size are correct when the resolution is set at the minimum (800x600) resolution. I can't tell if this is a dgVoodoo issue or a DXMT issue, so I report here. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Feb. 9, 2026