September 2022 - Wine-bugs - list.winehq.org

[Bug 53665] New: rawinput: Gamepad input lost after disconnect/reconnect
by WineHQ Bugzilla 12 Sep '22

12 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=53665 Bug ID: 53665 Summary: rawinput: Gamepad input lost after disconnect/reconnect Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Regression SHA1: 8962ec5a83286488da6f839ceba3c39ad1cf00b3 Distribution: --- Since Wine 7.10 (at least on Linux), when a gamepad is disconnected and subsequently reconnected, a running program accessing that gamepad using the rawinput interface can no longer receive input from the gamepad (the gamepad is effectively lost). Testing indicates that GetRawInputDeviceInfo() on the device after reconnect fails with error 6 (invalid handle), preventing detection of the reconnect. git bisect blames 8962ec5a, which broke gamepad input completely (the gamepad is never detected by the application). 4c584fe7 fixes initial detection, but the gamepad is lost after a disconnect/reconnect cycle. -- 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 53664] New: Exceptions in std::async not handled properly
by WineHQ Bugzilla 11 Sep '22

11 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=53664 Bug ID: 53664 Summary: Exceptions in std::async not handled properly Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tteu.ingog(a)gmail.com Distribution: --- Created attachment 73070 --> https://bugs.winehq.org/attachment.cgi?id=73070 The source code for a minimal example Found this bug while investigating crashes of NTKDaemon.exe on launch, which is required in Native Access 2.4.0. When a C++ exception is thrown inside a callable passed in std::async with std::launch::async policy, the unhandled exception is rethrown in the main thread when getting the value of the std::future returned by std::async. When executing a program compiled in Visual Studio 2022, However, it didn't work as expected. The program will either execute as if the thread exited normally at the point of `throw`, or somehow crash without forwarding the exception to the caller thread of std::async(especially when winegdb is attached). I'm not sure if it's related, but it seems like std::current_exception is also not working as expected. -- 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 4418] black screen when starting Warlords Battlecry
by WineHQ Bugzilla 11 Sep '22

11 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=4418 --- Comment #27 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still occurs with wine-7.17. -- 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 0

[Bug 53541] New: After upgrade from fedora 34 to 35, wine fails with "The explorer process failed to start."
by WineHQ Bugzilla 11 Sep '22

11 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=53541 Bug ID: 53541 Summary: After upgrade from fedora 34 to 35, wine fails with "The explorer process failed to start." Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: a_schapira(a)verizon.net Distribution: --- Created attachment 72903 --> https://bugs.winehq.org/attachment.cgi?id=72903 Text file of wine failure error messages After upgrading fedora from fc34 to fc35, wine fails to run anything, not even notepad. uname[ads(a)ADS2 ~]$ uname -a Linux ADS2 5.18.16-100.fc35.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 4 02:06:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux [ads(a)ADS2 ~]$ wine --version wine-7.12 (Staging) [ads(a)ADS2 ~]$ inxi -G Graphics: Device-1: Intel 82G33/G31 Express Integrated Graphics driver: i915 v: kernel Display: x11 server: X.Org v: 1.20.14 driver: X: loaded: intel unloaded: fbdev,modesetting,vesa gpu: i915 resolution: 1280x1024~60Hz OpenGL: renderer: Mesa DRI Intel G33 v: 1.4 Mesa 21.3.9 [ads(a)ADS2 ~]$ -- 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 53648] New: Update from 7.15> 7.16 many applications show glitches
by WineHQ Bugzilla 11 Sep '22

11 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=53648 Bug ID: 53648 Summary: Update from 7.15> 7.16 many applications show glitches Product: Wine-staging Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gizmo_1979(a)yahoo.it CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Today I upgraded from 7.15 to 7.16 and several programs that I was using that worked correctly with 7.15 started showing an unusable window full of glitches, one of these programs is benubird PDF https://benubird-pdf.download. it/ but also the configuration window of wine appears glitched, even the same wine config appears unusable and for this reason I have reported the bug as serious because it makes it impossible to use wine. I use kubuntu 22.04, graphics card is: 00:02.0 VGA compatible controller: Intel Corporation GeminiLake [UHD Graphics 605] (rev 03) I am attaching the screenshot of what happens with wine 7.16 and how the applications are displayed with wine 7.15 Wine 7.15 work ok https://postimg.cc/mcbrmwQc Wine 7.16 also the wine configurator does not work and various applications that were installed have stopped working, but not all! some continue to function correctly. https://postimg.cc/VJ969TbQ -- 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 53660] New: wait_for_withdrawn_state
by WineHQ Bugzilla 11 Sep '22

11 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=53660 Bug ID: 53660 Summary: wait_for_withdrawn_state Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: antoine(a)nagafix.co.uk Distribution: --- We have an issue where something in wine behave differently when receiving a WM_DELETE_WINDOW message: with some window managers it unmaps the window (ie: fluxbox) but with others (ie: xpra) it does not and this triggers the wait_for_widthdrawn_state timeout: https://github.com/Xpra-org/xpra/issues/3478#issuecomment-1237260437 Can you please clarify what wine is waiting for and why? As per the link above, which points to the wine source for map_window / unmap_window and X11DRV_WindowPosChanging / X11DRV_WindowPosChanged, it is really not clear to me why the window would not be unmapped when receiving WM_DELETE_WINDOW. -- 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 0

[Bug 40349] New: Window close delay and "fixme:event:wait_for_withdrawn_state ... wait timed out" messages
by wine-bugs＠winehq.org 11 Sep '22

11 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=40349 Bug ID: 40349 Summary: Window close delay and "fixme:event:wait_for_withdrawn_state ... wait timed out" messages Product: Wine Version: 1.9.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aptget(a)cock.lu Distribution: --- This bug is extremely similar to https://www.winehq.org/pipermail/wine-bugs/2008-September/136228.html . (bug 15483 is gone?) Every Wine window I try to close lingers for about 1 to 1.5 seconds before disappearing, and finally when it does, a fixme error is being printed that looks like this: fixme:event:wait_for_withdrawn_state window 0x1002a/1200005 wait timed out I'm using wine 1.9.6 on Arch Linux. The same problem happens with a clean wineprefix. -- 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 52713] New: Nota Bene installer has black background
by WineHQ Bugzilla 10 Sep '22

10 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=52713 Bug ID: 52713 Summary: Nota Bene installer has black background Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 72073 --> https://bugs.winehq.org/attachment.cgi?id=72073 Screenshot See attachment. -- 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

[Bug 53655] New: Bvckup2 - EXCEPTION_ACCESS_VIOLATION c0000005 / Unhandled page fault on read access
by WineHQ Bugzilla 10 Sep '22

10 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=53655 Bug ID: 53655 Summary: Bvckup2 - EXCEPTION_ACCESS_VIOLATION c0000005 / Unhandled page fault on read access Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 1nikolas(a)hotmail.gr Distribution: --- Created attachment 73057 --> https://bugs.winehq.org/attachment.cgi?id=73057 Wine log, openning executable after install You can download the trial version of the app here: https://bvckup2.com/ Installer runs fine. It's just the executable which throws the EXCEPTION_ACCESS_VIOLATION error. I have no idea were to even start debugging this. Also the debugger fails to run for some reason. The app of course runs fine both on Windows 10 and Windows 7. The executable after installing is in C:\Program Files\Bvckup 2\bvckup2.exe. Attached is a "+debugstr,+loaddll,+pid,+seh,+timestamp" log of the bvckup2.exe. (Log is from 7.15 wine-stagging on ArchLinux but has same behavior on 7.16) Thanks -- 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 24705] New: Unhandled page fault on write access to address in 32-bit code.
by wine-bugs＠winehq.org 10 Sep '22

10 Sep '22

http://bugs.winehq.org/show_bug.cgi?id=24705 Summary: Unhandled page fault on write access to address in 32-bit code. Product: Wine Version: 1.3.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: publio.escipion.el.africano(a)gmail.com Created an attachment (id=31216) --> (http://bugs.winehq.org/attachment.cgi?id=31216) wine execution output, with debbuging information. The present issue affect wine-1.1.28 & wine-1.3.4, and, I guess, the versions between. The application is an educational software, available from: http://static.cedeti.cl/software/sl/SuenaLetrasInstalador_mx.exe My SO is: openSuSE 11.2 x86_64 + Updates, which relevant specifications are: Linux **** 2.6.31.14-0.1-desktop #1 SMP PREEMPT 2010-09-17 11:32:00 +0200 x86_64 x86_64 x86_64 GNU/Linux GNU bash, version 4.0.35(1)-release (x86_64-suse-linux-gnu) The problem takes place after the installation, when the program is launched. Wine complained: "wine: Unhandled page fault on write access to 0x00000000 at address 0x******** (thread ****), starting debugger... Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x********)." I also saw calls, or paths with character codification (MS Windows ISO-8859-1 or ISO-8859-15 vs. Linux UTF-8) issues. But I do not know if this is a relevant part of the problem, or simply a noise. Every thing is collected in the file attached. I do not know whether this information be enough so you might solve it, or whether it requires a workaround configuration to make it run. Thank you. -- 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 14