wine-bugs

wine-bugs@winehq.org

1 participants
159325 discussions

[Bug 56709] New: PackTouchHitTestingProximityEvaluation not located in USER32.dll when attempting to run Clip Studio Paint 3.0
by WineHQ Bugzilla 26 Jun '25

26 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=56709 Bug ID: 56709 Summary: PackTouchHitTestingProximityEvaluation not located in USER32.dll when attempting to run Clip Studio Paint 3.0 Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: animaloser(a)gmail.com Distribution: --- Clip Studio Paint 3.0 fails to open, with a pop-up message that reads "The procedure point PackTouchHitTestingProximityEvaluation could not be located in the dynamic link library USER32.dll" The launcher does run however, even if it's all white, it's been documented in the appdb entry for the program. The main software, CLIPStudioPaint.exe, does not. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 58377] New: winegcc -m32 fails to link when using the new WoW64 mode
by WineHQ Bugzilla 25 Jun '25

25 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58377 Bug ID: 58377 Summary: winegcc -m32 fails to link when using the new WoW64 mode Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Distribution: --- Created attachment 78787 --> http://bugs.winehq.org/attachment.cgi?id=78787 winegcc command output Prompted by Arch switching to the new WoW64 mode in their packages. 32-bit winelib binaries seem to fail to link with the new WoW64 mode. I attached the output of compiling the following file with winegcc from a Wine build configured with `--enable-archs=i386,x86_64`: /* main.c */ int main() { return 0; } /* compiled with: LANG=C wineg++ -v -m32 -lole32 -o main main.c */ Swapping `-m32` out for `-m64` the winelib binary builds as expected. Most notably, the underlying GCC invocations include both `-m64` and `-m32` in that order (though it may have always done that), and the core Windows libraries cannot be found (which kind of makes sense since Wine no longer ships actual 32-bit libraries). On a related note: is it possible to detect whether Wine has been configured with the new WoW64 mode? I may need to detect this at runtime to be able to distribute a build of yabridge that works with both the old and new WoW64 modes. -- 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 12

[Bug 58413] New: osu!stable steals focus after Alt+Tab
by WineHQ Bugzilla 25 Jun '25

25 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58413 Bug ID: 58413 Summary: osu!stable steals focus after Alt+Tab Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: marshnelloosu(a)gmail.com Distribution: --- Created attachment 78822 --> http://bugs.winehq.org/attachment.cgi?id=78822 KDE Plasma X11, +x11drv,+trace logs. osu!stable has always been quirky when it comes to alt-tabbing and window management, but recently, the game consistently steals focus after Alt+Tab on most DE/WMs, sometimes even in borderless mode. I've ran a few tests on different DEs and in both X11/Wayland (with XWayland) and noticed some funny behavior: the few times the alt-tab actually goes through, it's when the tab involves an Electron app (e.g. Discord or Visual Studio Code). Additionally, on KDE the game seems to sometimes reposition itself in a very bad way, uploaded an example at: https://i.imgur.com/SLN9hRL.png Logs contain a test ran on KDE Plasma X11, with 'WINEDEBUG=+x11drv,+trace'. Thanks 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.

1 1

[Bug 48283] New: Pegasus Mail 4.73 crashes after install
by WineHQ Bugzilla 25 Jun '25

25 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=48283 Bug ID: 48283 Summary: Pegasus Mail 4.73 crashes after install Product: Wine Version: 4.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: daveypy(a)outlook.com Distribution: --- Created attachment 65965 --> https://bugs.winehq.org/attachment.cgi?id=65965 Saved backtrace from crash After installing Pegasus Mail in Wine, Pegasus Mail crashes upon launch. I would be willing to test this in Wine STAGING, but I don't know how to install STAGING alongside STABLE in Ubuntu. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 35684] New: Wine Internet Explorer crash when accessing amazon.com
by wine-bugs＠winehq.org 24 Jun '25

24 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=35684 Bug ID: 35684 Summary: Wine Internet Explorer crash when accessing amazon.com Product: Wine Version: 1.7.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: daniel.maccabe(a)gmail.com Created attachment 47650 --> http://bugs.winehq.org/attachment.cgi?id=47650 Backtrace of Wine failure when accessing amazon.com OS: Linux Mint 16 (Petra) with KDE desktop Using Wine 1.7.13 in WIN7 mode (also tried WIN XP mode) Running Wine internet explorer from C:\program files (x86) Internet Explorer seems to start normally, although slowly. The Winehq web page loads and appears to render correctly. If I try to access www.amazon.com (http, or https) the program experiences an error and quits. The following window is displayed: report says: Program Error The program iexplore.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. This can be caused by a problem in the program or a deficiency in 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.

2 5

[Bug 58409] New: Black Mirror 2 needs support for Write fx 2.0 parameter class 0x11
by WineHQ Bugzilla 24 Jun '25

24 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58409 Bug ID: 58409 Summary: Black Mirror 2 needs support for Write fx 2.0 parameter class 0x11 Product: vkd3d Version: 1.16 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 09b0:err:d3dcompiler:D3DCompile2 <anonymous>:291:14: E5017: Aborting due to not yet implemented feature: Write fx 2.0 parameter class 0x11. 1.16-261-gd8edf20c -- 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 44236] New: Poisson Superfish: Slow to write binary file.
by wine-bugs＠winehq.org 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=44236 Bug ID: 44236 Summary: Poisson Superfish: Slow to write binary file. Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: raphaelcervantes(a)protonmail.com Distribution: --- Discussion is in this forum. https://forum.winehq.org/viewtopic.php?f=2&t=29936 I am using Wine to run Poisson Superfish. This program essentially does some calculations and then writes the results into a binary file. This action is performed in less than a second in a Windows environment. Unfortunately, it takes about 10 seconds to write this binary file under Wine. Here is how to reproduce the error: 1. Install Poisson Superfish on linux using Wine. You have to scroll all the way down and click register. http://laacg.lanl.gov/laacg/services/download_sf.phtml 2. Once installed, open a unix terminal in this directory .../.wine/drive_c/LANL/Examples/RadioFrequency/Waveguides/ 3. Run wineconsole cmd. 4. In the new window, run RUNWG.BAT. 3. Several windows will pop up. The ones that stall for a bit are in the process of writing to a file named something.T35. The T35 refers to tape 35 (I guess that's how a sector of harddrive memory would be referred as back in the 80s). This is the binary file with the solution in it. It will finish eventually, but it is pretty slow. -- 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 52646] New: Trying to run wit (Wimms Iso Tools) , it works, its just when I start the iso extraction it gives me this error.
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=52646 Bug ID: 52646 Summary: Trying to run wit (Wimms Iso Tools) , it works, its just when I start the iso extraction it gives me this error. Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: madeinclt26(a)gmail.com Distribution: --- Created attachment 71966 --> https://bugs.winehq.org/attachment.cgi?id=71966 After it starts extracting the iso it says " The program wit.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. After it starts extracting the iso it says " The program wit.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience. -- 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 13

[Bug 54975] New: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=54975 Bug ID: 54975 Summary: win32u:win32u exits prematurely, leaves child process behind, interferes with windows.globalization:globalization Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- win32u:win32u exits prematurely, leaves child process behind: win32u:win32u start dlls/win32u/tests/win32u.c [...] win32u.c:1037: Test marked todo: res = 4 win32u.c:1040: Test marked todo: buf[1] = 0 win32u:win32u:09f0 done (0) in 0s 1295B win32u.c:1045: Test failed: res = 0 win32u.c:1046: Test failed: buf = d win32u.c:1049: Test failed: res = 0 win32u.c:1059: Test failed: res = 0 09e0:win32u: 14 tests executed (2 marked as todo, 0 as flaky, 4 failures), 0 skipped. See https://test.winehq.org/data/patterns.html#win32u:win32u There are two things to notice in the above log: * The main win32u:win32u process is 09e0 but it did not issue a 'tests executed' summary. This means it exited prematurely. * 09e0 is a child process that continues running and printing messages which interferes with the next test, specifically windows.globalization:globalization. Also on the TestBot one can find the corresponding Wine log which contains these lines that seem strongly correlated to this issue: 0480:err:seh:KiUserCallbackDispatcher ignoring exception 0480:err:seh:KiUserCallbackDispatcher ignoring exception wine client error:480: partial write 57344 Running: win32u:win32u (694 of 774) Running tests - 6 failures This issue only happens on Linux and happens systematically but only on three configurations: fg-deb64-t32 but not for the wow32 and wow64 builds on the same machine fgtb-debian11-wow64 but not for the wow32 build on the same machine debian11b-wow64 but but not for the wow32 build on the same machine (and none of the 32-bit builds on debian11 is impacted) And I have been unable to reproduce this failure on my machine (fg-deb64-t32). So it's unclear what causes this failure but it clearly started on 2023-05-15 so it's probably some commit on that day. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 58408] New: win32u:input: Performance regression in Resident Evil 2 due to internal messages.
by WineHQ Bugzilla 23 Jun '25

23 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58408 Bug ID: 58408 Summary: win32u:input: Performance regression in Resident Evil 2 due to internal messages. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: lojorix20(a)yandex.ru Regression SHA1: b053e924e8e13b3637f2a5a8ffe88d84c2d17075 Distribution: --- There is a performance regression in some games like Resident Evil 2 and NFS: Most Wanted (2012). After removing peek_message call in win32u:input:check_for_events the fps is back to normal. -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs