- wine-bugs - winehq.org

[Bug 54676] New: winetricks --verify dotnet20 (AutoHotKey) fails in a wow64 build
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54676 Bug ID: 54676 Summary: winetricks --verify dotnet20 (AutoHotKey) fails in a wow64 build Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: NEW Keywords: dotnet, download, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian Created attachment 74190 --> https://bugs.winehq.org/attachment.cgi?id=74190 terminal output The install itself seems to go okay (at least, it exits successfully in quiet mode). Running --verify (which should run the .Net verifier tool) instead just hangs on: /opt/oldwownew/wine-8.3/bin/wine y:\ahk\AutoHotkeyU32.exe C:\windows\Temp\dotnet20.ahk -- 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 55127] New: httpapi:httpapi - test_v2_bound_port() sometimes succeeds in connecting on Windows 10
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55127 Bug ID: 55127 Summary: httpapi:httpapi - test_v2_bound_port() sometimes succeeds in connecting on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: httpapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com httpapi:httpapi - test_v2_bound_port() sometimes succeeds in connecting on Windows 10: httpapi.c:1426: Test failed: Connecting to socket succeeded, 0. httpapi.c:1427: Test failed: Unexpected error connecting to socket, 0. See https://test.winehq.org/data/patterns.html#httpapi:httpapi This failure first happened on 2023-02-09 and has happened 4 times since then: * 2023-02-09 win22H2_fgtb-w10pro64-32 * 2023-03-30 win22H2_fgtb-w10pro64-32 * 2023-05-30 win2009_newtb-w1064v2009-64 * 2023-06-15 win2009_newtb-w1064v2009-64 -- 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 54866] New: ieframe:webbrowser - test_SetQueryNetSessionCount() sometimes gets an unexpected session count on Windows
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54866 Bug ID: 54866 Summary: ieframe:webbrowser - test_SetQueryNetSessionCount() sometimes gets an unexpected session count on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ieframe:webbrowser - test_SetQueryNetSessionCount() sometimes gets an unexpected session count on Windows: webbrowser.c:4440: init_count 1 webbrowser.c:4443: Test failed: count = 3 webbrowser.c:4446: Test failed: count = 3 webbrowser.c:4449: Test failed: count = 2 webbrowser.c:4452: Test failed: count = 2 See https://test.winehq.org/data/patterns.html#ieframe:webbrowser These failures only happen on Windows 10 21H1 to 22H2. On Windows 10 init_count is either 1 or 2 (on w8adm is can be 0 too), but all the failures so far happened with an init_count of 1. That said there are also a lot of successful runs with init_count == 1. This looks a lot like the browser creates a net session for its own purposes: * Either init_count is 1 and the extra net session is never created or gets created after test_SetQueryNetSessionCount() is done so all is fine. * Or the extra net session is created it before test_SetQueryNetSessionCount() starts and outlives it so our tests pass. * Or the extra net session gets created after we get init_count but before the next test so that all our tests are off by one. * But it seems the extra net session never gets created after the first SESSION_INCREMENT test. Note that on my Windows 10 VM when I start iexplorer.exe by hand and then run the test I always get init_count == 2. But if IE is not already running I get init_count == 0. In any case if it's a race condition I could send a patch to retry a couple of times. -- 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 54073] New: ws2_32:sock - test_close_events() sometimes fails in Wine
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54073 Bug ID: 54073 Summary: ws2_32:sock - test_close_events() sometimes fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ws2_32:sock - test_close_events() sometimes fails in Wine: sock.c:6775: Test succeeded inside todo block: event series matches sock.c:6785: Test failed: got unexpected event 0x20 sock.c:6785: Test failed: event series matches See https://test.winehq.org/data/patterns.html#ws2_32:sock This happens in the nightly WineTest runs about twice per month but also impacts merge requests (for instance MR!1524 and MR!1525 where it happened on the GitLab CI). -- 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 48621] New: Civilization 6 crashes on startup.
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=48621 Bug ID: 48621 Summary: Civilization 6 crashes on startup. Product: Wine Version: 5.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: charles2000wang(a)gmail.com Distribution: --- Created attachment 66468 --> https://bugs.winehq.org/attachment.cgi?id=66468 Game Log file Launching the game opens a black window before promptly crashes with the Firaxis Crash Reporter asking to submit a report. Digging around the game files, I found a log file (GameOverlayRenderer.log) with messages about "Aborting HookFunc because pRealFunctionAddr is null" and other errors. -- 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 36564] New: 'Candytron' demo: certain objects are black with GLSL enabled
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=36564 Bug ID: 36564 Summary: 'Candytron' demo: certain objects are black with GLSL enabled Product: Wine Version: 1.6-rc1 Hardware: x86 URL: http://www.pouet.net/prod.php?which=9424 OS: Linux Status: NEW Keywords: download, regression Severity: trivial Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: 2014141a253a791fc9c79aae3c8ef3c35b73e658 Created attachment 48657 --> http://bugs.winehq.org/attachment.cgi?id=48657 screenshot (comparison) Some of the rectangles that appear in the demo nearly at 00:30 and at 01:10 are black. They should appear as glowing green rectangles as can be seen in the attached screenshot. Terminal output doesn't reveal anything interesting. Disabling GLSL is a workaround. This is a regression from Wine 1.6-rc1: 2014141a253a791fc9c79aae3c8ef3c35b73e658 is the first bad commit commit 2014141a253a791fc9c79aae3c8ef3c35b73e658 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Wed May 29 09:45:35 2013 +0200 wined3d: Add support for GLSL based fixed function vertex shaders. :040000 040000 d1b4b75f643d4851d4f51454aa47740261f7857f c46794f61b1952b1e78746272d838574c0948010 M dlls Fedora 20 Nvidia 250 gfx card / Nvidia binary drivers 337.19 wine-1.7.19-70-gd6a59f7 -- 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 20

[Bug 55367] New: Trying to run WatchFaceStudio with wine 8.0 and Ubuntu 23 (lunar)
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55367 Bug ID: 55367 Summary: Trying to run WatchFaceStudio with wine 8.0 and Ubuntu 23 (lunar) Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tda.bkp(a)gmail.com Distribution: --- Created attachment 74949 --> https://bugs.winehq.org/attachment.cgi?id=74949 WatchFaceStudio.exe crash trace Installed WatchFaceStudio successfully, but won't run. Trace 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 2

[Bug 54831] New: GStreamer gst_init_check() crashes when called from winegstreamer on recent macOS
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54831 Bug ID: 54831 Summary: GStreamer gst_init_check() crashes when called from winegstreamer on recent macOS Product: Wine Version: 8.5 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com On macOS Ventura (and I suspect Monterey), gst_init_check() crashes (trying to jump to 0x0) when called by winegstreamer. This is caused by the macOS preloader, here's how: * gst_init_check() calls init_static_plugins() <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/1.22/subprojects/…>, which through some GModule abstractions does a dlopen(NULL) and dlsym() for a symbol that doesn't exist. dlsym() returns NULL, but GModule also calls dlerror() which returns NULL (signaling no error). * init_static_plugins() therefore thinks that the dlsym() was successful, doesn't do a NULL pointer check, and jumps to the NULL pointer. The issue here is dlerror() returning NULL despite there being an error to report. Looking at the macOS dyld source code (<https://github.com/apple-oss-distributions/dyld/blob/dyld-1042.1/dyld/DyldA…>), dlerror() always returns NULL if libSystem was not initialized in the process. And sure enough, when running vmmap on a Wine process, the message "Process exists but has not fully started -- dyld has initialized but libSystem has not" is printed. After more searching in dyld, it turns out that dyld initializes libSystem for binaries targeting 10.5 and newer. The Wine preloader targets 10.7 (since that's the newest target that will generate an LC_UNIXTHREAD binary, critical to how the preloader works). But dyld determines the target OS based on where the program vars (argc, argv, environ, etc) are stored, and a 10.6/10.7 binary should contain a __program_vars section for those. The preloader is missing that, and so (I believe) it falls down to being considered a 10.4 binary. A 10.4 binary should init libSystem in its own _start, but the preloader also doesn't do this, and libSystem stays uninitialized. (See <https://github.com/apple-oss-distributions/dyld/blob/dyld-1042.1/common/Mac…> for where this is determined) I see several possible solutions: * The most obvious one: add a __program_vars section to the preloader, to make it a correct 10.7 binary. In fact, the code can basically be copied out of Apple's C startup code (<https://github.com/apple-opensource/Csu/blob/88/crt.c#L47>). This does work, and libSystem gets initialized. However, libSystem is initialized before any preloader code runs, and malloc zones are already in the middle of areas we want to reserve. That's bad; by itself this approach won't work, but it might if we also: - add linker zerofill sections to block off the entire low 4GB. This is desirable to reserve as much address space as possible for 32-bit EXEs in wow64 mode. - and if zerofill sections are also added to reserve the area where 64-bit EXEs generally load (0x14000000), it might even be possible to stop using the preloader altogether on 64-bit. * Alternately, go the other way, and lean in to being a 10.4 binary. In that case, _start in the preloader needs to call back into dyld to initialize things (like this: <https://github.com/apple-opensource/Csu/blob/88/crt.c#L219>). We could do this after reserving our areas. I'm leery of this approach, mainly because x86_64/10.4 was not a popular target (GUI apps were not supported, they could only link against libSystem). If possible, I'd rather not target such an obscure combination. The preloader has been a source of problems with new OS versions, and I'd like to decrease the amount of black magic it's doing, not increase it. (Running 10.4 x86_64 binaries on modern macOS is still supported though, and Xcode can even still build them.) I'd like to make the __program_vars+zerofill approach work if possible. -- 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 54748] New: Greenshot GDI+ status: PropertyNotFound
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54748 Bug ID: 54748 Summary: Greenshot GDI+ status: PropertyNotFound Product: Wine Version: 8.3 Hardware: x86-64 URL: https://objects.githubusercontent.com/github-productio n-release-asset-2e65be/36756917/23e6800e-7d29-11e7-8ac 5-aa92e5646973?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz- Credential=AKIAIWNJYAX4CSVEH53A%2F20230328%2Fus-east-1 %2Fs3%2Faws4_request&X-Amz-Date=20230328T165105Z&X-Amz -Expires=300&X-Amz-Signature=311e88c8da4b8ba0ff5ac6008 cf054338cd6e18afcf64471443530ddae088db0&X-Amz-SignedHe aders=host&actor_id=0&key_id=0&repo_id=36756917&respon se-content-disposition=attachment%3B%20filename%3DGree nshot-NO-INSTALLER-1.2.10.6-RELEASE.zip&response-conte nt-type=application%2Foctet-stream OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: lukasz.wojnilowicz(a)gmail.com Distribution: --- Steps to reproduce: 1) unpack Greenshot-NO-INSTALLER-1.2.10.6-RELEASE.zip 2) wine Greenshot.exe 3) RMB on Greenshot icon in the system tray 4) LMB on "Capture region" 5) Draw a rectangel on your screen Behavior: Error window with contents as below. Expected behavior: No error window. Error window contents: Software version: 1.2.10.6-RELEASE-c2414cf0149a1475ea00520effc01b40087c225c (32 bit) .NET runtime version: 4.0.30319.42000+ Time: 2023-03-28 18:59:01 +02:00 OS: unknown (x32) 10.0 build 2600 revision 30000 GDI object count: 0 User object count: 0 Exception: System.Exception Message: Unknown Error [GDI+ status: PropertyNotFound] Stack: at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x0022b] in <fc2ea6474c6d4315858618f13de6e72a>:0 at System.Drawing.Image.get_PropertyItems () [0x00017] in <fc2ea6474c6d4315858618f13de6e72a>:0 at (wrapper remoting-invoke-with-check) System.Drawing.Image.get_PropertyItems() at GreenshotPlugin.Core.ImageHelper.CloneArea (System.Drawing.Image sourceImage, System.Drawing.Rectangle sourceRect, System.Drawing.Imaging.PixelFormat targetFormat) [0x00172] in <68959698d73243a09b84293d02c00b84>:0 at GreenshotPlugin.Core.ImageHelper.Crop (System.Drawing.Image& image, System.Drawing.Rectangle& cropRectangle) [0x00046] in <68959698d73243a09b84293d02c00b84>:0 at GreenshotPlugin.Core.Capture.Crop (System.Drawing.Rectangle cropRectangle) [0x0001a] in <68959698d73243a09b84293d02c00b84>:0 at Greenshot.Helpers.CaptureHelper.CaptureWithFeedback () [0x00085] in <64ca337812514938b5bb8fc98fce780b>:0 at Greenshot.Helpers.CaptureHelper.MakeCapture () [0x008a0] in <64ca337812514938b5bb8fc98fce780b>:0 at Greenshot.Helpers.CaptureHelper.CaptureRegion (System.Boolean captureMouse) [0x00008] in <64ca337812514938b5bb8fc98fce780b>:0 at Greenshot.MainForm+<>c.<CaptureAreaToolStripMenuItemClick>b__52_0 () [0x00000] in <64ca337812514938b5bb8fc98fce780b>:0 at System.Windows.Forms.Control.InvokeMarshaledCallbackDo (System.Windows.Forms.Control+ThreadMethodEntry tme) [0x000c0] in <d22f8be2dd674c49bd49b314423240b8>:0 at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper (System.Object obj) [0x00029] in <d22f8be2dd674c49bd49b314423240b8>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 at System.Windows.Forms.Control.InvokeMarshaledCallback (System.Windows.Forms.Control+ThreadMethodEntry tme) [0x0004d] in <d22f8be2dd674c49bd49b314423240b8>:0 at System.Windows.Forms.Control.InvokeMarshaledCallbacks () [0x0008a] in <d22f8be2dd674c49bd49b314423240b8>:0 Terminal output: 0024:fixme:dwmapi:DwmGetWindowAttribute (0003008E 9 0021DA80 16) stub 0024:fixme:uiautomation:UiaClientsAreListening () 0024:fixme:dwmapi:DwmGetWindowAttribute (00050086 9 0021D620 16) stub 0024:fixme:dwmapi:DwmGetWindowAttribute (00050070 9 0021C850 16) stub Additional info: seems to happen on NET 4.5 and Mono as well -- 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 10

[Bug 54546] New: ws2_32:sock - test_write_watch() gets unexpected write counts on Windows 11
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54546 Bug ID: 54546 Summary: ws2_32:sock - test_write_watch() gets unexpected write counts on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock - test_write_watch() gets unexpected write counts on Windows 11: sock.c:7670: Test failed: wrong count 0 sock.c:7701: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 See https://test.winehq.org/data/patterns.html#ws2_32:sock -- 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 52889] New: Freelancer with Crossfire mod crashes on startup
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52889 Bug ID: 52889 Summary: Freelancer with Crossfire mod crashes on startup Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: poweroverwhelming982(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 6857cb56957d691bee76cfe28ef88714cca00f29 Distribution: Ubuntu Created attachment 72282 --> https://bugs.winehq.org/attachment.cgi?id=72282 Wine log at commit 6857cb56957d691bee76cfe28ef88714cca00f29 Since wine-6.19, Freelancer with Crossfire 2.0 mod crashes immediately on startup (as soon as the mod window is shown). Bisecting points to this commit: > commit 6857cb56957d691bee76cfe28ef88714cca00f29 > Author: Jacek Caban <jacek(a)codeweavers.com> > Date: Wed Sep 29 14:09:21 2021 +0200 > > gdi32: Move ntgdi functions to Unix library. I've attached the relevant logs, let me know if there's anything else I can do. Additional info: OS: Ubuntu Focal 20.04.3 LTS Kernel: 5.13.0-30-generic x86_64 Wine Prefix: 32 bit, clean GPU: NVIDIA Corporation GF108 [GeForce GT 730] (rev a1) Graphics Driver: Proprietary NVIDIA ver. 390.144 -- 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 52474] New: ws2_32:sock fails intermittently - 'Test failed: expected timeout'
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52474 Bug ID: 52474 Summary: ws2_32:sock fails intermittently - 'Test failed: expected timeout' Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Distribution: --- The test_connect_events() function contains the following checks, where the check (2) fails intermittently: 1. check_events(ctx, FD_CONNECT, FD_WRITE, 200); 2. check_events(ctx, 0, 0, 0); A hypothesis for the cause of the test failure is that the WSAEnumNetworkEvents() call inside the check (1) races with the server setting the event. Note that WSAEnumNetworkEvents performs the following steps: a. It calls ResetEvent on the given event. b. It issues IOCTL_AFD_GET_EVENTS command on the socket to retrieve the events so far. It's possible that the event may be set by the server between (a) and (b), which lingers until the next call to WSAEnumNetworkEvents(). This explains why the event wait in check (2) is satisfied immediately but subsequent tests report no events. -- 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 34678] New: Not all serial port work in wine
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=34678 Bug #: 34678 Summary: Not all serial port work in wine Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rewineland(a)gmail.com Classification: Unclassified I have wine 1.6 install on Ubuntu 12.04 with kernel 3.8.0-31-generial. I have 2 serial ports on board and an add-on card with 8 more.I can get the the on board and 7 of the add-on to work as 1 though 9 comports but com10 I can not get any data though. the port is listed as ttyCTI7, when I connect to that I have data going back and forth. It just wont go into the windows program. Any ideas on what to do. I need to have all 10 ports. -- 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 10

[Bug 55283] New: amstream:amstream systematically crashes and times out on gitlab-debian-32
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55283 Bug ID: 55283 Summary: amstream:amstream systematically crashes and times out on gitlab-debian-32 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- amstream:amstream systematically crashes and times out on gitlab-debian-32: Unhandled exception: assertion failed in wow64 32-bit code (0xf7f19559). Backtrace: =>0 0xf7f9a559 __kernel_vsyscall+0x9() in [vdso].so (0xf7f34ff4) 1 0xf7da21d7 in libc.so.6 (+0x8a1d7) (0xf7f34ff4) 2 0xf7d510d1 in libc.so.6 (+0x390d1) (0xf7f34ff4) 3 0xf7d3a26a in libc.so.6 (+0x2226a) (0xf7f34ff4) 4 0x71a4de79 in libllvm-15.so.1 (+0x875e79) (0x0022e910) 5 0x00000040 (0x00000040) 0xf7f9a559 __kernel_vsyscall+0x9 in [vdso].so: pop %ebp See https://test.winehq.org/data/patterns.html#amstream:amstream The failures started on 2023-07-10 which corresponds to the GitLab CI switch to Debian 12. What makes this very bad is that the failure is systematic so every single merge request has been getting a GitLab CI error since then. So it is pretty urgent to either: 1. Fix the test if something is wrong with it. 2. Fix the gitlab-debian-32 test environment if it is wrong. 3. Skip amstream:amstream if neither of the above is doable in a reasonable timeframe. -- 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 15

[Bug 53171] New: advapi32:registry - test_performance_keys() sometimes fails due to time going backwards!
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53171 Bug ID: 53171 Summary: advapi32:registry - test_performance_keys() sometimes fails due to time going backwards! Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry - test_performance_keys() sometimes fails due to time going backwards: registry.c:3757: Test failed: key FFFFFFFF80000004: value (null): got times 132999520626290092, 132999520626290092, 132967560392269933 registry.c:3763: Test failed: key FFFFFFFF80000004: value (null): got times 132999520626290092, 132999520626290000, 132967560392269933 https://test.winehq.org/data/patterns.html#advapi32:registry This failure is pretty rate: I only found 4 cases (~0.9%): win2009_newtb-w1064-tsign, win21H1_newtb-w10pro64-mx-MX, 2x win21H2_fgtb-w10pro64. The failure lines above happened on w10pro64-mx-MX on 2022-06-17. Here are the corresponding timestamps: systime1 = 132999520626290092 = 2022-06-17 15:07:42.629009 file_time = 132999520626290000 = 2022-06-17 15:07:42.629000 systime2 = 132967560392269933 = 2022-05-11 15:20:39.226993 file_time is a little lower than systime1 which is normal due to its granularity. What is totally wrong however is that systime2 is way lower than systime1. The interesting part is that the live snapshot was created on 2022-05-11 which matches systime2. This scenario is confirmed it two of the other instances; the snapshot creation time for the last case is unknown but a match with systime2 is plausible. After restoring the VM from the live snapshot LibvirtTool sets the VM time through TestAgent::SetTime(): https://gitlab.winehq.org/winehq/tools/-/blob/master/testbot/bin/LibvirtToo… https://gitlab.winehq.org/winehq/tools/-/blob/master/testbot/src/testagentd… So it looks like in rare cases the system time gets reset backwards precisely between this test's two NtQuerySystemTime() calls, which is really unlucky... or lucky: maybe it happens in other cases causing less obvious failures. I don't know if TestAgentd sets the time wrong, if there's something wrong with Windows, or if this is an artifact of the QEmu clocks: <clock offset='localtime'> <timer name='rtc' tickpolicy='delay'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> <timer name='hypervclock' present='yes'/> </clock> -- 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 52492] New: stack overflow from GdipFlattenPath
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52492 Bug ID: 52492 Summary: stack overflow from GdipFlattenPath Product: Wine Version: 7.1 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: rjfeuerbach(a)gmail.com Created attachment 71787 --> https://bugs.winehq.org/attachment.cgi?id=71787 test patch to replicate the curves and stack overflow I have a third party application, unfortunately not available for download, that is generating a virtual stack overflow error. Using +replay and eventually +gdiplus messages, the cause was narrowed down to be due to calls to GdipFlattenPath. Attached is a patch to gdiplus/test/graphicspath.c to include the precise curves that cause the stack overflow. I believe the problem is due to the comparison of REALs with == in the flatten_bezier helper function. -- 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 22

[Bug 55422] New: mfmediaengine:mfmediaengine - test_GetDuration() fails in Wine
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55422 Bug ID: 55422 Summary: mfmediaengine:mfmediaengine - test_GetDuration() fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mfmediaengine:mfmediaengine - test_GetDuration() fails in Wine: mfmediaengine.c:1961: Test failed: Unexpected res 0x102. See https://test.winehq.org/data/patterns.html#mfmediaengine:mfmediaengine This failure started with the commit that introduced the tests: commit 613d7b099986828212299a8e98179f22c86b80ab Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Fri Aug 4 17:35:04 2023 +0800 mfmediaengine/tests: Test IMFMediaEngine::GetDuration(). -- 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 54720] New: Spider-Man: Shattered Dimensions - dialogue audio doesn't play
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54720 Bug ID: 54720 Summary: Spider-Man: Shattered Dimensions - dialogue audio doesn't play Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)tutanota.com Distribution: --- Created attachment 74226 --> https://bugs.winehq.org/attachment.cgi?id=74226 Logs taken with a clean 32 bit prefix with 32 bit Wine devel 8.4, WINEDEBUG=+xactengine,+xaudio2,+x3daudio. In Spider-Man: Shattered Dimensions, the audio that is supposed to be played by the characters during in-game dialogues doesn't play. All the other kinds of audio work. A workaround to this is by installing xact with winetricks. -- 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 44816] New: Cygwin/ MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=44816 Bug ID: 44816 Summary: Cygwin/MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-Deal… Mentioned here: https://wine-staging.com/news/2015-08-23-release-1.7.50.html --- quote --- Do not allow to deallocate thread stack for current thread (MSYS2, Wine Staging Bug #241) --- quote --- After some archaeology I found the Cygwin mailing list discussion here: https://cygwin.com/ml/cygwin/2015-09/msg00114.html --- quote --- > Ah, ok. What OS does Wine emulate here? Have a look at > https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… > > The terminate_thread_frees_stack flag is set to false for XP/2003 and to > true for any newer OS. I guess this is a double-free because Wine's > TerminateThread already freed the stack and Cygwin got the info it's > supposedly running under XP/2003, so it tries to workaround the fact > that TerminateThread on these systems didn't free the stack by themselves. > Wine emulates Windows XP here, I double checked Wine source code and I can confirm Wine doesn't free the stack: NtTerminateThread() -> abort_thread() -> terminate_thread() https://github.com/wine-compholio/wine-patched/blob/8b3a785e97a7e28ff58731b… Cygwin reports wincap as wincap_xpsp2 which is also correct here. > we need to know what address ret=61005767 is refering to. addr2line would help. As you point out, ret=61005767 is the call to VirtualFree() inside cygthread::terminate_thread () https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… After combine the information we have so far, I think the problem is clear now. It's not Cygwin's fault, it's Wine's fault. Wine's WaitForSingleObject() needs to wait long enough after the TerminateThread() call, so the target thread has enough time to finish the system cleanup and return correct exit_code before Cygwin call VirtualFree to free the stack. But in our current implementation Wine's WaitForSingleObject returns too early, it shouldn't return before the system thread cleanup done, as a result there is a race here. We are thinking of a solution in Wine. Thanks again for the great help! --- quote --- $ wine --version wine-3.4 Regards -- 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 30655] New: GRID2: Low (1 - 3) FPS during race, but not in in-game menus.
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=30655 Bug #: 30655 Summary: GRID2: Low (1 - 3) FPS during race, but not in in-game menus. Product: Wine Version: 1.5.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: linards.liepins(a)gmail.com Classification: Unclassified Created attachment 40128 --> http://bugs.winehq.org/attachment.cgi?id=40128 in-game benchmark test #! Game itself installed with latest winetricks. -- 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 25

[Bug 28603] New: Winedbg sometimes receives invalid parameters
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=28603 Bug #: 28603 Summary: Winedbg sometimes receives invalid parameters Product: Wine Version: 1.3.29 Platform: x86 URL: http://www.winehq.org/pipermail/wine-patches/2011-Sept ember/106508.html OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: julliard(a)winehq.org Classification: Unclassified Created attachment 36753 --> http://bugs.winehq.org/attachment.cgi?id=36753 relay,seh,tid,dbghelp,winedbg I sent a patch to eliminate this dialog: http://www.winehq.org/pipermail/wine-patches/2011-September/106508.html but Alexandre said this should never happen. I see it occasionally on various systems, but since I wrote the patch, haven't found a very reliable testcase. I've found a reliable testcase with make test on Alpine Linux (which uses uclibc). It may not be the best testcase, since it's not using glibc (and also use PaX), but AJ asked for a log, so here we go :). relay,seh,tid,dbghelp,winedbg attached the testcase used was oleaut32/tmarshal wine-1.3.29-217-g5432611 -- 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 6

[Bug 55258] New: steam: small window floating on top of all windows even in fullscreen mode
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55258 Bug ID: 55258 Summary: steam: small window floating on top of all windows even in fullscreen mode Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru Distribution: --- Created attachment 74873 --> https://bugs.winehq.org/attachment.cgi?id=74873 steam_window_bug.png When running steam with new versions of wine, I'm getting a small square window which is always on top of all windows, even when I'm playing fullscreen game. It's usually located around center of screen for me, but during bisecting I also got a few builds when it appeared at top left corner. I've tested it with following wine versions: wine 7.0.2: win7 prefix: good wine 7.0.2: win10 prefix: does not start wine 8.0.1: win7 prefix: good wine 8.0.1: win10 prefix: good wine 8.9: win10 prefix: bad wine 8.12: win10 prefix: bad After that I ran git bisect with following build: mkdir build32 build64 cd build64 ../configure --with-mingw --enable-win64 --prefix=/tmp/wineinstall cd ../build32 ../configure --with-mingw --with-wine64=../build64 --prefix=/tmp/wineinstall cd ../build64 make $JOBS cd ../build32 make $JOBS make $JOBS install cd ../build64 make $JOBS install My results are: 2504a2d7bca47fc77bb523114d7b0b6e60213116 is the first bad commit commit 2504a2d7bca47fc77bb523114d7b0b6e60213116 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Mar 27 11:58:50 2023 +0200 imm32: Keep the IME UI window on the default input context. dlls/imm32/imm.c | 61 ++++++++++++++++++++++++++++++++------------------------ 1 file changed, 35 insertions(+), 26 deletions(-) $ git bisect log # bad: [9ffeb2622d087a6189ca916553529824791010c3] Release 8.9. # good: [d8b2687760f7c07eaf481aba2835b820d3092b3e] Release 8.0.1. git bisect start 'wine-8.9' 'wine-8.0.1' # skip: [6677c044abb711f423fadfb61f2c9a37da6ff686] Release 8.0. git bisect skip 6677c044abb711f423fadfb61f2c9a37da6ff686 # good: [7771a9ae79930d112051cfe18b27dec1e5edd245] widl: Simplify attribute creation with either int or ptr value. git bisect good 7771a9ae79930d112051cfe18b27dec1e5edd245 # bad: [d1c317720ab6a92811c013408844ffd9e581b2a2] mfreadwrite: Fix an address of operator typo. git bisect bad d1c317720ab6a92811c013408844ffd9e581b2a2 # bad: [66bef6db20f72e88a38c4b264e13639015d7817d] msvcrt: Use the sinhf() implementation from the bundled musl library. git bisect bad 66bef6db20f72e88a38c4b264e13639015d7817d # bad: [17fbef91929af9c6ab98e53fb2a54942f0f1a0a5] wmvcore/tests: Don't cast NULL to another pointer type. git bisect bad 17fbef91929af9c6ab98e53fb2a54942f0f1a0a5 # skip: [83f0862b43f7b1b7bd23830b4339894c35febea7] wineps: Handle EMR_SETARCDIRECTION record in spool files. git bisect skip 83f0862b43f7b1b7bd23830b4339894c35febea7 # good: [6a88500af29b82040f0518eb87171ca047fb95aa] hidparse.sys: Include zero-count reports in cap count. git bisect good 6a88500af29b82040f0518eb87171ca047fb95aa # good: [62ef3c5be1d2c5374399984588a9daa75663d030] taskkill: Factor out get_task_pid(). git bisect good 62ef3c5be1d2c5374399984588a9daa75663d030 # bad: [956541c9c823fb6048047893545dcee4c108730e] d3d10/effect: Add support for umin/umax instructions. git bisect bad 956541c9c823fb6048047893545dcee4c108730e # good: [4b04d357739f261457316d55b79ecbcff9c0be84] imm32/tests: Add explicit ImmLoadIME / ImmFreeLayout calls. git bisect good 4b04d357739f261457316d55b79ecbcff9c0be84 # bad: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the IME UI window on the default input context. git bisect bad 2504a2d7bca47fc77bb523114d7b0b6e60213116 # good: [9117ce4185146a5edd47467d370b3e4dfa588191] imm32/tests: Test ImmProcessKey with the installed IME. git bisect good 9117ce4185146a5edd47467d370b3e4dfa588191 # good: [43e22eaa76a443e3053868df1bd8c5d4130a9fde] imm32/tests: Test IME UI window and IME window presence. git bisect good 43e22eaa76a443e3053868df1bd8c5d4130a9fde # good: [0ddad3564f3260f53e5a50b615f6aa6ba27e032b] imm32: Update existing input contexts on layout change. git bisect good 0ddad3564f3260f53e5a50b615f6aa6ba27e032b # first bad commit: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the IME UI window on the default input context. OS: Gentoo Linux Amd64 Kernel: 6.1.38-gentoo DE: KDE 5.27.5 glxinfo: OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.49, 6.1.38-gentoo.65) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.3 OpenGL core profile shading language version string: 4.60 -- 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 54413] New: ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54413 Bug ID: 54413 Summary: ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows: sock.c:12512: Test failed: got 1. sock.c:12513: Test failed: got 0. See https://test.winehq.org/data/patterns.html#ws2_32:sock This failure is pretty rare, there are only 4 known instances: * 2022-09-27 on w1064 64 bit (21h2) * 2022-11-15 on w10pro64-hi-u8 64 bit (21h1) * 2023-01-25 on w11pro64 64 bit (21h2) * 2023-01-25 on w1064v2009 64 bit The test creates a socket, treats it as a handle and duplicates it, then checks whether the duplicate handle behaves like a socket which it normally does not, causing WSAGetOverlappedResult() to fail (return 0) and WSAGetLastError() to be set to WSAENOTSOCK. But in these four cases WSAGetOverlappedResult() succeeded which would indicate the duplicate handle looked like a socket? -- 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 44546] New: The Settlers II: 10th Anniversary runs very slow when CSMT enabled
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=44546 Bug ID: 44546 Summary: The Settlers II: 10th Anniversary runs very slow when CSMT enabled Product: Wine Version: 3.2 Hardware: x86 URL: https://www.fileplanet.com/165168/160000/fileinfo/The- Settlers-II:-10th-Anniversary-Demo-v9801 OS: Linux Status: NEW Keywords: performance Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- The game is running painfully slow in Wine 3.2. Can be observed while it is playing the opening video, in the menus and during gameplay too. Loading times are also incredibly long when csmt is enabled. Disabling csmt makes the game run smoothly. There is nothing suspicious in the terminal. Can be reproduced with the demo version. I have native d3dcompiler_43 and d3dx9_29 installed. settlers2_demo2_multilang.exe (318M) md5sum: c738916e0f5f4c9b780898f66e50941f Wine 3.2 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 -- 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

[Bug 55291] New: gdi32:dc - print_something() gets a bad signature on fg-deb64-*
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55291 Bug ID: 55291 Summary: gdi32:dc - print_something() gets a bad signature on fg-deb64-* Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:dc - print_something() gets a bad signature on fg-deb64-*: dc.c:1501: Test failed: wrong signature: See https://test.winehq.org/data/patterns.html#gdi32:dc This does not depend on bitness, happens systematically and a bisect shows that the failure started with the commit below: commit d5373ef6f92d36971859db0746600188ada22a7d Author: Piotr Caban <piotr(a)codeweavers.com> Date: Sun Jul 9 13:05:42 2023 +0200 wineps: Buffer data sent to printer port. -- 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 55231] New: Warframe: camera/mouse stuck in X-axis
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55231 Bug ID: 55231 Summary: Warframe: camera/mouse stuck in X-axis Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pmargeti34(a)gmail.com Distribution: --- Wine 8.12 introduces a regression in Warframe: there seems to be a hard limit to how much camera can be turned on the X-axis. After spinning the camera in the same direction a few times, it gets stuck and it's no longer possible to turn in in that direction until it is first turned in the opposite direction. This happens when Warframe is either in full screen mode or borderless fullscreen mode. Windowed mode isn't affected. Warframe is a free to play game and the installer can be obtained here: https://www.warframe.com/download OS: Archlinux Linux 6.4.3 -- 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 17

[Bug 55152] New: Crash in Notepad++ processing a WM_DRAWITEM message
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55152 Bug ID: 55152 Summary: Crash in Notepad++ processing a WM_DRAWITEM message Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: julliard(a)winehq.org Distribution: --- Running the 32-bit Notepad++ 8.5.4 in new wow64 mode crashes on startup when processing a WM_DRAWITEM message. The exception is swallowed by win32u so it still works, but we get a message: 0024:err:seh:KiUserCallbackDispatcher ignoring exception The root cause is that because Notepad++ added a WH_CALLWNDPROC hook, in win32u process_message(), instead of returning to SendMessageW and have it call the winproc, we call it ourselves through KeUserModeCallback. But at that point the message has been converted to 64-bit so we pass a (truncated) 64-bit lparam to the 32-bit winproc. The crash was revealed by a82238fad52761114ab2488d422fad3f70dbb854, which moves the 64-bit stack to high memory. Previously the lparam pointer would fit in 32-bit which avoided the crash, but it would still point to a 64-bit DRAWITEMSTRUCT. -- 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 51443] New: Test fails in remove_dir_all crate when creating file
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=51443 Bug ID: 51443 Summary: Test fails in remove_dir_all crate when creating file Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- Hi, Steps to reproduce on clear wine-devel 6.12 ``` wget https://static.rust-lang.org/dist/rust-1.53.0-x86_64-pc-windows-gnu.msi msiexec /i rust-1.53.0-x86_64-pc-windows-gnu.msi git clone https://github.com/XAMPPRocky/remove_dir_all.git cd remove_dir_all git checkout 9b164cecdb4a0590af68be8b22f9c747402237e3 wine cargo test ``` should print this ``` running 4 tests test removes_read_only ... FAILED test removes_empty ... ok test removes_files ... ok test removes_dirs ... ok failures: ---- removes_read_only stdout ---- thread 'removes_read_only' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 5, kind: PermissionDenied, message: "Access denied." }', tests\windows.rs:68:49 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace failures: removes_read_only test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s error: test failed, to rerun pass '--test windows' ``` I tested it and this works fine in Windows Server 2019 Source code of failed test - https://github.com/XAMPPRocky/remove_dir_all/blob/9b164cecdb4a0590af68be8b2… ``` fn removes_read_only() { env_logger::init(); for i in 0..5 { let path = format!("./readonly/{}/subdir", i); fs::create_dir_all(&path).unwrap(); let file_path = format!("{}/file.txt", path); { let file = File::create(&file_path).unwrap(); ``` -- 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 55449] New: Yaesu Wires-X offline and no internet
by WineHQ Bugzilla 16 Aug '23

16 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55449 Bug ID: 55449 Summary: Yaesu Wires-X offline and no internet Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: oleacc Assignee: wine-bugs(a)winehq.org Reporter: michael.vencio(a)gmail.com Distribution: --- Created attachment 75008 --> https://bugs.winehq.org/attachment.cgi?id=75008 debug output Yaesu Wires-X is an amateur radio application https://www.yaesu.com/jp/en/wires-x/index.php the application is installed and running but cannot connect to the internet. attached is the debug 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.

1 0

[Bug 34374] New: Mac driver does not respect "Emulate a virtual desktop" option
by wine-bugs＠winehq.org 16 Aug '23

16 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=34374 Bug #: 34374 Summary: Mac driver does not respect "Emulate a virtual desktop" option Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winemac.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: samael5(a)verizon.net Classification: Unclassified The Mac driver launches all apps in fullscreen mode, regardless of whether "Emulate a virtual desktop" is set. Virtual desktop still functions as expected when using the X11 driver on Mac. -- 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 6

[Bug 39012] New: Game "Yesterday" crashes while being played (OS X Yosemite)
by wine-bugs＠winehq.org 15 Aug '23

15 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=39012 Bug ID: 39012 Summary: Game "Yesterday" crashes while being played (OS X Yosemite) Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: deka95500(a)hotmail.com Hi everyone, I have a version of Yesterday that was built using a wrapper from this website(external link). Everything worked fine until I reached the 3rd stage. The game was stuck on a loading screen and eventually crashed before showing a message saying: "Yesterday.exe has encountered a serious problem and needs to close." The wrapper is using Wineskin 2.5.8 / WS8Wine1.3.16. I'm using Mac OS X Yosemite 10.10.3 on a 2013 MBP. Can you please help me figure out what the issue is? 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.

2 10

[Bug 14713] New: Xara Xtreme 4: Resizing handles not visible
by wine-bugs＠winehq.org 15 Aug '23

15 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=14713 Summary: Xara Xtreme 4: Resizing handles not visible Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: info(a)linopus.de Xara Xtreme 4: Resizing handles not visible Xara Xtreme 4, the latest edition of the vector drawing application from Xara (30 days trial available at http://www.xara.com/us/downloads/xtreme/ ), shows no resizing handles when selecting an object. The resizing handles should be visible when clicking an object with the select tool. By contrast, the turning/shearing handles are visible. The turning/shearing handels appear when clicking an object twice with the select tool. Additionally, Bezier handles and points on curves do appear, but in wrong colors (cyan instead of red). Bezier handles and points appear when using the edit shape tool. This is on a wine 1.1.2 install on Ubuntu Linux 8.04 in its standard settings. The same bug is present when using Xara Xtreme X1, which is the thirdlast edition. The bug is also present in earlier versions of wine (e.g. 0.9.56) and CrossOver (e.g. 7.0.1). Yours sincerely Tobias Hilbricht -- 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 10

[Bug 10471] New: Radmin viewer 3.1: Ungrayed disabled menu item in the " Connection Properties" window
by wine-bugs＠winehq.org 15 Aug '23

15 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=10471 Summary: Radmin viewer 3.1: Ungrayed disabled menu item in the "Connection Properties" window Product: Wine Version: 0.9.48. Platform: PC URL: http://www.famatech.com/download/rview31.exe OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: wine-gui AssignedTo: wine-bugs(a)winehq.org ReportedBy: bugs.radmin(a)gmail.com We got an error: 1. Installed Radmin server 3.1 (http://www.famatech.com/download/rserv31.exe) on a windows computer. 2. Installed Radmin viewer 3.1 on a linux computer with wine installed. 3. Started Radmin viewer and open "Connection Properties" window (can be reached "Right click on connection icon" --> "Properties" or "Connection" --> "Connect to"). The list of intermediate hosts in "Advanced settings" should be grayed (disabled) until checkbox "Connect through host" is marked. The error was tested on Fedora Core 7 installation with the last wine package from fedora update site (fedora_mirror/fedora/linux/updates/7/i386/). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 12

[Bug 41267] New: Black ops 2 crashes with "Unhandled exception caught"
by wine-bugs＠winehq.org 15 Aug '23

15 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=41267 Bug ID: 41267 Summary: Black ops 2 crashes with "Unhandled exception caught" Product: Wine Version: 1.9.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spleefer90(a)gmail.com Distribution: --- Created attachment 55567 --> https://bugs.winehq.org/attachment.cgi?id=55567 crash log when trying to launch the game(BO2:MP) from Steam Game crashes on startup with the message: "Error during initialization: Unhandled exception caught" -- 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 51

[Bug 55447] New: wine cannot parse valid javascript
by WineHQ Bugzilla 15 Aug '23

15 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55447 Bug ID: 55447 Summary: wine cannot parse valid javascript Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: jscript Assignee: wine-bugs(a)winehq.org Reporter: yshuiv7(a)gmail.com Distribution: --- jscript cannot parse the code below: var O = { continue: 1 }; var x = { label: O.continue }; it reports: 0024:warn:jscript:script_parse parser failed around L"bel: O.continue\n };\n});\n" in line L"sync_test(\"ASDF\", function() {" Native Windows jscript doesn't have a problem with this. The cause, I believe, is jscript inserted a semicolon after the "continue". -- 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 55434] New: socialclubhelper.exe serious problem in wine unable to run GTA v via steam but worked for past 4 weeks
by WineHQ Bugzilla 14 Aug '23

14 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55434 Bug ID: 55434 Summary: socialclubhelper.exe serious problem in wine unable to run GTA v via steam but worked for past 4 weeks Product: Wine Version: unspecified Hardware: arm OS: Windows Status: UNCONFIRMED Severity: major Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: lynxmyster(a)gmail.com Created attachment 74995 --> https://bugs.winehq.org/attachment.cgi?id=74995 error log report /Users/lyntonhartill/Downloads/backtrace.txt -- 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 55420] New: The Legend of Sisyphus by Andromeda Software Development fails to run
by WineHQ Bugzilla 14 Aug '23

14 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55420 Bug ID: 55420 Summary: The Legend of Sisyphus by Andromeda Software Development fails to run 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: arabek+wine(a)gmail.com Distribution: --- Created attachment 74980 --> https://bugs.winehq.org/attachment.cgi?id=74980 backtrace.txt Source: https://files.scene.org/view/parties/2023/assembly_summer23/demo/asd-theleg… (free download) Problem: ubuntu-23.04, clean prefix, wine-staging-8.13 installed from winehq repo - demo fails to run. Attached is the backtrace.txt generated. -- 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 55441] New: after update rawinput patch scroll wheel is not working on some game.
by WineHQ Bugzilla 14 Aug '23

14 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55441 Bug ID: 55441 Summary: after update rawinput patch scroll wheel is not working on some game. Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- After latest rawinput update. I found the code x11drv_xinput_disable() is added, seems due to this code. the scroll wheel is no longer working. I fallback to 8.13 it working again. -- 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 55440] New: StarCraft 2: can no longer input Chinese via fcitx5
by WineHQ Bugzilla 14 Aug '23

14 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55440 Bug ID: 55440 Summary: StarCraft 2: can no longer input Chinese via fcitx5 Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: allfoxwy(a)gmail.com Distribution: --- Greetings. I'm switching from Wine-staging 8.5 to Wine-staging 8.13. Then I see that in StarCraft 2 I can no longer input Chinese into the game via fcitx 5. In the game, I could use key shortcut to call up fcitx 5 into Chinese mode. I press some key then I could see the word candidates in the top left corner of the screen (not following the cursor). However if I select one of them, nothing goes into the game's textbox. I also tried wine notepad, I could input Chinese in it. The Battle.net client also work. But the actual StarCraft 2 game do not accept my input. StarCraft 2 version 5.0.11.90136 fcitx 5 from Debian version 5.0.23-2 Wine-staging-amd64 8.13 from https://github.com/Kron4ek/Wine-Builds/releases/tag/8.13 In fact, it's not only StarCraft 2, Diablo 4 also have such symptom. However StarCraft 2 is a free game so it's easier to get and debug: https://starcraft2.blizzard.com And I read the Wine What's New and see that there are some work going into IME recently. There is a FIXED bug report: https://bugs.winehq.org/show_bug.cgi?id=54991 It says Wine 8.8 was working, so I tried it, and yes in Wine 8.8 I could input in StarCraft 2 either. However the supposed fix which was landed in Wine 8.10 did NOT fix the problem in StarCraft 2. I tried to get a console log. However this game need Battle.net client to bootstrap up. If I run wine "Battle.net Launcher.exe" & > sc2log.txt" the resulting file is empty. Any help is appreciated. -- 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 54664] New: ZeroMQ 4.3.4#6 (from vcpkg) hangs in wine on macOS Catalina
by WineHQ Bugzilla 14 Aug '23

14 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54664 Bug ID: 54664 Summary: ZeroMQ 4.3.4#6 (from vcpkg) hangs in wine on macOS Catalina Product: Wine Version: 8.3 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: steven.schumacher(a)dtn.com Created attachment 74179 --> https://bugs.winehq.org/attachment.cgi?id=74179 Example app with source and results Attached is a sample ZMQ pub/sub app including source (and project files but they might need tweaking) code built against zeromq4.0.5 as a static lib vs zeromq4.3.4#6 as a dll from vcpkg (at the time of submission, this is the current version). Unfortunately I've had issue building newer versions of zmq from source and zmq no longer maintains windows builds ever since MS took over with vcpkg. The build environment is VS 2019 on windows 10 (both fully updated). Both versions of the app run the same on windows. On macOS Catalina (not sure about earlier or later...my macOS resources are slim) under wine (both Crossover 22.0.1 and bare wine 8.3), only the version usign zmq4.0.5 works with the 4.3.4 version of zmq hangs as soon as zmq is initialized. Text files with output for both on both OS is also included. -- 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 50206] New: Cinebench R23 fails to start (needs dcomp.dll implementation?)
by WineHQ Bugzilla 12 Aug '23

12 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=50206 Bug ID: 50206 Summary: Cinebench R23 fails to start (needs dcomp.dll implementation?) Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aidas957(a)gmail.com Distribution: --- Created attachment 68717 --> https://bugs.winehq.org/attachment.cgi?id=68717 Cinebench R23 Windows 10 Wine log As I've said in the title, CInebench R23 fails to start probably because of missing dcomp.dll which is needed by one of the app's important libraries and thus the app spits out a bunch of warnings and then closes (with both Windows 7 and Windows 10 versions set in Wine) I've tried to copy a 64-bit dcomp.dll from a Windows 10 installation, but there are even more errors of libraries missing (and I can't locate them all) I'm also using wine-staging. but I doubt that's going to affect anything in this case Log with Windows 10 version is 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 8

[Bug 50459] New: Unimplemented function dcomp.dll.DCompositionCreateDevice called in 64-bit code (Studio One 5)
by WineHQ Bugzilla 12 Aug '23

12 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=50459 Bug ID: 50459 Summary: Unimplemented function dcomp.dll.DCompositionCreateDevice called in 64-bit code (Studio One 5) Product: Wine Version: 6.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: moseskim84(a)gmail.com Distribution: --- Created attachment 69083 --> https://bugs.winehq.org/attachment.cgi?id=69083 Winedbg log file I'm running Ubuntu 20.10, Wine-6.0-rc5 and have installed Studio One 5 Professional (music production program) into it's own prefix. The program does not open at all and crashes when I run it with the following error: wine: Call from 000000007B01135E to unimplemented function dcomp.dll.DCompositionCreateDevice, aborting wine: Unimplemented function dcomp.dll.DCompositionCreateDevice called at address 000000007B01135E (thread 0244), starting debugger... I have installed the following libraries: corefonts, atmlib, d3dcompiler43, d3dx9, d9vk/dxvk, fontsmooth-rgb, gdiplus_winxp, msxml3, msxml6, vcrun2008, vcrun2010, vcrun2012 I have tried it on wine-stable as well (5.0) but it still won't load. Any help would be appreciated. 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 13

[Bug 50357] New: Star Stable Online crashes with unimplemented function dcomp.dll.DCompositionCreateDevice2
by WineHQ Bugzilla 12 Aug '23

12 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=50357 Bug ID: 50357 Summary: Star Stable Online crashes with unimplemented function dcomp.dll.DCompositionCreateDevice2 Product: Wine Version: 6.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vojtech.dockal(a)gmail.com Distribution: --- Created attachment 68955 --> https://bugs.winehq.org/attachment.cgi?id=68955 Backtrace Star Stable Online crashes with unimplemented function dcomp.dll.DCompositionCreateDevice2 called in 32-bit code (0x7b010bf6). Steps to reproduce: 1) Download installer from https://launcher-data.starstable.com/Star+Stable+Online+Setup+2.6.0.exe and install it - Run launcher - Launcher crashes Backtrace is included in 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 12

[Bug 55436] New: hi so each time i open the rockstar games social club i keep getting a message saying the application has entered a serious problem and needs to close here is the crash report i got :Unhandled exception: page fault on read access to 0x0000000000000000 in
by WineHQ Bugzilla 12 Aug '23

12 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55436 Bug ID: 55436 Summary: hi so each time i open the rockstar games social club i keep getting a message saying the application has entered a serious problem and needs to close here is the crash report i got :Unhandled exception: page fault on read access to 0x0000000000000000 in Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Voyager1928(a)gmail.com hi so each time i open the rockstar games social club i keep getting a message saying the application has entered a serious problem and needs to close here is the crash report i got from crossover: Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000183843848). Register dump: rip:0000000183843848 rsp:000000000021e120 rbp:00000318eca3d8c8 eflags:00000202 ( - -- I - - - ) rax:000000000021e148 rbx:0000000000000000 rcx:000004ac5c8232ac rdx:000000018720b270 rsi:0000000186ce7d30 rdi:0000051fb2c21b40 r8:0000000000000011 r9:00000000ff000000 r10:000000018720b270 r11:000004ac5c8232ac r12:0000000000000000 r13:0000000000000000 r14:000000000021e148 r15:000000000021e1e0 Stack dump: 0x0000000021e120: 00000318eca3d8c8 00002f7ef439cf78 0x0000000021e130: 00002f7ef439cf78 0000051fb2c21b40 0x0000000021e140: 00000318eca3d680 000004ac5c8232a0 0x0000000021e150: 000000000021e260 00000318eca3d680 0x0000000021e160: 000006b582481c81 00000318eca3d8c8 0x0000000021e170: 0000000000000000 00002f7ef439cf58 0x0000000021e180: 000000000021e1e0 0000051fb2c21b40 0x0000000021e190: 0000000186ce7d30 0000000000000000 0x0000000021e1a0: 00000318eca3d6a8 0000000183843986 0x0000000021e1b0: 000000000352ee90 0000000182504cdc 0x0000000021e1c0: 00000318eca3d680 00000318eca73f80 0x0000000021e1d0: 000000000352f040 000000000352f070 Backtrace: =>0 0x00000183843848 CrashForExceptionInNonABICompliantCodeRange+0x1d3b818() in libcef (0x000318eca3d8c8) 1 0x00000183843986 CrashForExceptionInNonABICompliantCodeRange+0x1d3b956() in libcef (0x000318eca3d8c8) 2 0x000001839763f5 CrashForExceptionInNonABICompliantCodeRange+0x1e6e3c5() in libcef (0x000318eca3d8c8) 3 0x0000018397605b CrashForExceptionInNonABICompliantCodeRange+0x1e6e02b() in libcef (0x000000004264c0) 4 0x00000183975fc4 CrashForExceptionInNonABICompliantCodeRange+0x1e6df94() in libcef (0x0000000352ec01) 5 0x00000182d2ad15 CrashForExceptionInNonABICompliantCodeRange+0x1222ce5() in libcef (0x0000018722d7c0) 6 0x00000182d2cb1a CrashForExceptionInNonABICompliantCodeRange+0x1224aea() in libcef (0x00000000000008) 7 0x00000183a22f12 CrashForExceptionInNonABICompliantCodeRange+0x1f1aee2() in libcef (0x00000000000008) 8 0x000001808dbc2b cef_add_cross_origin_whitelist_entry+0x8da351() in libcef (0x00000000000008) 9 0x000001824f9578 CrashForExceptionInNonABICompliantCodeRange+0x9f1548() in libcef (0x00000080000003) 10 0x00000182e82604 CrashForExceptionInNonABICompliantCodeRange+0x137a5d4() in libcef (0x00000080000003) 11 0x00000182e80bcb CrashForExceptionInNonABICompliantCodeRange+0x1378b9b() in libcef (0x000001879acf88) 12 0x00000182412900 CrashForExceptionInNonABICompliantCodeRange+0x90a8d0() in libcef (0x000001879acf88) 13 0x00000182da1627 CrashForExceptionInNonABICompliantCodeRange+0x12995f7() in libcef (0x00000182e80543) 14 0x00000182da1386 CrashForExceptionInNonABICompliantCodeRange+0x1299356() in libcef (0x7fffffffffffffff) 15 0x00000182d9320c CrashForExceptionInNonABICompliantCodeRange+0x128b1dc() in libcef (0x7fffffffffffffff) 16 0x00000182da1c88 CrashForExceptionInNonABICompliantCodeRange+0x1299c58() in libcef (0x00000000000001) 17 0x000001823fcb6a CrashForExceptionInNonABICompliantCodeRange+0x8f4b3a() in libcef (0x0000000021eec8) 18 0x00000182d2ff44 CrashForExceptionInNonABICompliantCodeRange+0x1227f14() in libcef (0x0000000021eec8) 19 0x0000018234f475 CrashForExceptionInNonABICompliantCodeRange+0x847445() in libcef (0x0000000021f060) 20 0x00000182bcfa66 CrashForExceptionInNonABICompliantCodeRange+0x10c7a36() in libcef (0000000000000000) 21 0x00000182bd007c CrashForExceptionInNonABICompliantCodeRange+0x10c804c() in libcef (0000000000000000) 22 0x0000018234eb8e CrashForExceptionInNonABICompliantCodeRange+0x846b5e() in libcef (0000000000000000) 23 0x00000182d5b239 CrashForExceptionInNonABICompliantCodeRange+0x1253209() in libcef (0000000000000000) 24 0x000001823805b5 CrashForExceptionInNonABICompliantCodeRange+0x878585() in libcef (0000000000000000) 25 0x00000180001137 cef_execute_process+0x57() in libcef (0000000000000000) 26 0x000001400b9e7c in socialclubhelper (+0xb9e7c) (0000000000000000) 27 0x00000140081955 in socialclubhelper (+0x81955) (0x0000000021f7f0) 28 0x0000014008156f in socialclubhelper (+0x8156f) (0000000000000000) 29 0x000001401dfcd6 in socialclubhelper (+0x1dfcd6) (0000000000000000) 30 0x0000007b62bbc9 ActivateActCtx+0x1ffe9() in kernel32 (0000000000000000) 31 0x0000017005bd93 A_SHAFinal+0x39293() in ntdll (0000000000000000) 0x00000183843848 libcef+0x3843848: movq (%rbx),%rax Modules: Module Address Debug info Name (94 modules) ELF 0000000000001000-000000000000c000 Deferred <wine-loader> ELF 00000000000f9000-0000000000105000 Deferred netapi32.so PE 0000000000540000-000000000063e000 Deferred chrome_elf PE 0000000010000000-0000000010002000 Deferred usp10 PE 0000000068900000-0000000068910000 Deferred libwine.1.0.dylib ELF 0000000068918000-0000000068928000 Deferred ws2_32.so ELF 0000000068933000-0000000068943000 Deferred dnsapi.so ELF 000000006894c000-000000006895c000 Deferred user32.so ELF 0000000068964000-0000000068978000 Deferred secur32.so ELF 000000006898a000-0000000068a5e000 Deferred ntdll.so ELF 0000000068b1a000-0000000068b2a000 Deferred crypt32.so ELF 0000000068b4b000-0000000068b63000 Deferred bcrypt.so ELF 0000000068b79000-0000000068b89000 Deferred dwrite.so ELF 0000000068b94000-0000000068ba4000 Deferred winspool.so ELF 000000006d000000-000000006d1b0000 Deferred win32u<elf> \-PE 000000006d010000-000000006d1a0000 \ win32u PE 000000006d1b0000-000000006d26c000 Deferred libcxfreetype.6.dylib ELF 000000006d485000-000000006d491000 Deferred kerberos.so ELF 000000006d49e000-000000006d4ae000 Deferred msv1_0.so ELF 000000006d504000-000000006d66c000 Deferred opengl32<elf> \-PE 000000006d510000-000000006d65c000 \ opengl32 ELF 000000006f531000-000000006f5e1000 Deferred winemac<elf> \-PE 000000006f540000-000000006f5cd000 \ winemac PE 0000000078eca000-0000000078f52000 Deferred libgmp.10.dylib PE 00000000790d2000-00000000792da000 Deferred libgnutls.30.dylib PE 000000007b000000-000000007b24e000 Deferred kernelbase PE 000000007b600000-000000007b65e000 Export kernel32 PE 000000007d400000-000000007d40b000 Deferred wine64-preloader PE 0000000140000000-00000001403c2000 Export socialclubhelper PE 0000000170000000-000000017009d000 Export ntdll PE 0000000180000000-000000018809a000 Export libcef PE 00000001c4ee0000-00000001c4f10000 Deferred winspool PE 00000001c69e0000-00000001c72fe000 Deferred shell32 PE 00000001c8b40000-00000001c8b60000 Deferred msacm32 PE 00000001c8db0000-00000001c8e47000 Deferred msvcrt PE 00000001cfdf0000-00000001cfe13000 Deferred dxva2 PE 00000001dd3f0000-00000001dd4be000 Deferred crypt32 PE 00000001ec2b0000-00000001ec2d6000 Deferred ws2_32 PE 00000001f51e0000-00000001f51f0000 Deferred hid PE 00000001fdfd0000-00000001fdff8000 Deferred wintrust PE 0000000201cf0000-0000000201d0f000 Deferred secur32 PE 000000021ff70000-000000022010f000 Deferred wined3d PE 0000000228450000-000000022847b000 Deferred propsys PE 0000000231ae0000-0000000231b62000 Deferred rpcrt4 PE 000000023d820000-000000023d9ec000 Deferred user32 PE 0000000240030000-000000024005d000 Deferred iphlpapi PE 000000024f470000-000000024f48f000 Deferred mpr PE 00000002522e0000-0000000252324000 Deferred oleacc PE 000000025d740000-000000025d74e000 Deferred dwmapi PE 000000026b4c0000-000000026b53b000 Deferred gdi32 PE 00000002739c0000-0000000273af6000 Deferred oleaut32 PE 0000000274a50000-0000000274a5e000 Deferred kerberos PE 000000028dfa0000-000000028dfac000 Deferred nsi PE 00000002967b0000-00000002967e4000 Deferred d3d9 PE 00000002998f0000-000000029992e000 Deferred dxgi PE 000000029cfc0000-000000029cfd6000 Deferred dnsapi PE 00000002a4090000-00000002a409e000 Deferred wtsapi32 PE 00000002bb750000-00000002bb88f000 Deferred comctl32 PE 00000002bc640000-00000002bc650000 Deferred imagehlp PE 00000002cc880000-00000002cc88c000 Deferred wevtapi PE 00000002cd450000-00000002cd4b8000 Deferred d3d11 PE 00000002d23f0000-00000002d2417000 Deferred credui PE 00000002d4d40000-00000002d4d57000 Deferred bcrypt PE 00000002d64d0000-00000002d6536000 Deferred libvkd3d-1 PE 00000002e3540000-00000002e3591000 Deferred shlwapi PE 00000002e8f10000-00000002e902b000 Deferred ole32 PE 00000002f1fa0000-00000002f1fad000 Deferred version PE 00000002f3920000-00000002f3930000 Deferred esent PE 00000002f7230000-00000002f7265000 Deferred uxtheme PE 00000002fca80000-00000002fcb12000 Deferred libvkd3d-shader-1 PE 000000030a950000-000000030a9c2000 Deferred dwrite PE 00000003126f0000-0000000312709000 Deferred shcore PE 000000031f800000-000000031f8ff000 Deferred comdlg32 PE 0000000327020000-0000000327073000 Deferred combase PE 000000032a700000-000000032a729000 Deferred sechost PE 0000000330260000-000000033029f000 Deferred advapi32 PE 0000000330a70000-0000000330a81000 Deferred uiautomationcore PE 00000003422e0000-000000034237c000 Deferred urlmon PE 0000000346ba0000-0000000346bc1000 Deferred jsproxy PE 0000000358120000-0000000358166000 Deferred winhttp PE 00000003673d0000-00000003673f8000 Deferred netapi32 PE 0000000388e20000-0000000388e2e000 Deferred userenv PE 000000039c380000-000000039c391000 Deferred msv1_0 PE 00000003a0440000-00000003a04c3000 Deferred wininet PE 00000003a19e0000-00000003a19ef000 Deferred ncrypt PE 00000003aa4c0000-00000003aa4cc000 Deferred dhcpcsvc PE 00000003af670000-00000003af730000 Deferred ucrtbase PE 00000003afd00000-00000003afd1a000 Deferred imm32 PE 00000003b8f00000-00000003b8fc1000 Deferred winmm PE 00000003bb250000-00000003bb358000 Deferred cryptui PE 00000003be590000-00000003be604000 Deferred dbghelp PE 00007ff80e933000-00007ff80e96f000 Deferred libsystem_kernel.dylib PE 00007ff80e96d000-00007ff80e979000 Deferred libsystem_pthread.dylib PE 00007ff80e99d000-00007ff80e9a9000 Deferred libsystem_platform.dylib Threads: process tid prio name (all IDs are in hex) 00000030 services.exe 00000034 0 00000038 0 0000004c 0 00000064 0 0000007c 0 000000b0 0 0000010c 0 0000081c 0 00000044 svchost.exe 00000048 0 00000054 0 00000058 0 0000005c plugplay.exe 00000060 0 00000068 0 0000006c 0 00000070 0 00000118 0 0000013c 0 00000140 0 0000011c 0 00000040 0 00000074 winedevice.exe 00000078 0 00000080 0 00000084 0 00000088 0 000000d0 0 000000d4 0 00000094 explorer.exe 00000098 0 0000009c 0 000000a0 0 000000a8 rpcss.exe 000000ac 0 000000b4 0 000000b8 0 000000bc 0 000000c0 0 000000c4 0 00000150 0 00000104 winedevice.exe 00000108 0 00000110 0 00000114 0 00000120 0 00000124 0 00000128 0 0000012c 0 00000730 LauncherPatcher.exe 00000734 0 00000750 0 00000758 Launcher.exe 0000075c 0 00000784 0 00000790 -2 00000794 -2 00000798 -2 0000079c 0 000007a0 0 000007a4 0 000007a8 0 000007ac 0 000007b0 0 000007b4 0 000007b8 0 000007bc 0 000007c0 0 000007c4 0 000007c8 0 000007cc 0 000007d0 0 000007d4 0 000007d8 0 000007dc 0 000000cc 0 000000e0 0 000000e8 0 000000dc 0 000000d8 0 000000f8 0 000000f4 0 000000f0 0 000000ec 0 000000fc 0 0000002c 0 00000028 0 00000134 0 00000024 0 00000130 0 00000020 0 000000c8 0 00000144 0 000001c8 0 00000760 RockstarErrorHandler.exe 00000764 0 00000768 0 0000076c 0 00000770 0 00000774 0 00000778 0 0000077c 0 00000780 0 000007fc RockstarService.exe 00000800 0 00000804 0 00000808 0 0000003c 0 00000138 SocialClubHelper.exe 0000015c 0 00000164 0 00000158 0 00000160 0 0000016c 0 00000174 0 00000168 -2 00000170 0 00000154 0 0000014c 0 00000184 0 0000017c 0 00000180 0 00000178 0 00000194 0 0000018c 1 0000019c 0 00000190 0 00000188 0 00000198 1 000001a4 0 000001a0 0 00000050 -2 000001c0 0 000001c4 -2 000001bc 0 000001b4 0 000001d4 0 000001d0 0 000001d8 -2 000001b8 SocialClubHelper.exe 000001b0 0 000001e0 0 00000208 0 00000214 0 0000022c -2 0000023c 0 00000238 0 0000021c 0 00000220 0 00000234 0 00000230 0 00000228 -2 00000250 0 000001dc (D) C:\Program Files\Rockstar Games\Social Club\SocialClubHelper.exe 000001cc 0 <== 00000218 0 00000224 0 00000210 0 00000204 -2 000001fc 1 0000020c 0 00000200 0 000001f8 0 00000254 1 0000024c 0 00000244 0 00000248 0 00000240 0 00000264 0 00000260 -2 0000027c 0 00000268 conhost.exe 00000258 0 System information: Wine build: wine-7.7-8868-g7eaa13362c5 Platform: x86_64 Version: Windows 7 Host system: Darwin Host version: 22.5.0 -- 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 54933] New: Wine slow on certain fuse filesystems, with fix
by WineHQ Bugzilla 12 Aug '23

12 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54933 Bug ID: 54933 Summary: Wine slow on certain fuse filesystems, with fix Product: Wine Version: 8.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: hwertz10(a)gmail.com Distribution: --- Created attachment 74452 --> https://bugs.winehq.org/attachment.cgi?id=74452 CIOPFS speed patch I found a description of users experiencing slowdowns (even using explorer.exe) on an MTP filesystem, and I experienced similar slowdowns on an s3ql filesystem. In short, even using explorer on certain filesystems is slow, and opening programs that open up more than a handful of files is very slow off these filesystems.: https://forum.winehq.org/viewtopic.php?t=36400 I found the root cause courtesy of strace -- in dlls/ntdll/unix/file.c in get_dir_case_sensitivity_stat (which is called very frequently, I think on any file open or creation, among others), there is a fstatat system call, then a check on that result to see if the filesystem is a FUSE filesystem, then if it is it looks for a .ciopfs directory (because presumably CIOPFS -- Case Insensitive On Purpose Filesystem -- places a .ciopfs in every directory specifically so wine can do this test.) It turns out the fstatat call gets used and free inode count, used and free disk space, etc. along with filesystem type, and on my large s3ql filesystem at least this takes *8/10ths* of a second, versus the .ciopfs lookup being in dentry cache -- I don't recall if it used 0.0001 or 0.00001 seconds, but either way extremely fast compared to the other call. Reversing the order of these calls (check for .ciopfs first, then if it's there run fstatat and check result to see if it's a FUSE filesystem) should not cause a performance regression on any filesystem (since it's usually going to be out of the dentry cache) while avoiding this slowdown on a filesystems with slow filesystem stats. Just a note, I see the equivalent "is filesystem case sensitive?" check for MacOS actually only runs any tests once then caches the results; using a similar "case sensitivity" cache for Linux would also be effective (since it would only run this piece of code once per wine run then.) Finally, I wonder if CIOPFS is actually used? I see the last update on it is from 2011, it may have turned out that Wine's case insensitivity support is fast enough that CIOPFS did not prove useful. If it's not actually being used by anyone, removing the CIOPFS tests from file.c could be a reasonable thing to do. Please find attached a small patch to implement this change for Linux -- it simply reverses the order of 3 lines of code, so it runs the (fast) .ciopfs directory existence test first, then only runs the (on some filesystems much slower) fstatat call and "is it FUSE filesystem?" test if the.ciopfs directory actually exists. Thanks, and keep up the good work!!! --Henry -- 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 30550] New: Invisibles sprites in Rayman Origins
by wine-bugs＠winehq.org 12 Aug '23

12 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=30550 Bug #: 30550 Summary: Invisibles sprites in Rayman Origins Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: olivier.luraine(a)gmail.com Classification: Unclassified Created attachment 39961 --> http://bugs.winehq.org/attachment.cgi?id=39961 Screenshot that shows the bug. They are missing sprites on rayman origins. For exemple ropes and other things that rayman catch are invisible. I'm using an up to date archlinux with nvidia 295.40. The game run smoothly. -- 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 44

[Bug 37355] New: Tages Protection v5.x needs ntoskrnl 'MmMapLockedPagesSpecifyCache' implementation
by wine-bugs＠winehq.org 11 Aug '23

11 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=37355 Bug ID: 37355 Summary: Tages Protection v5.x needs ntoskrnl 'MmMapLockedPagesSpecifyCache' implementation Product: Wine Version: 1.7.27 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, reported here: https://github.com/compholio/wine-compholio/issues/80 Michael Müller from FDS team: --- quote --- Sadly this is not enough to make the Tages copy protection happy. The issue you are now running into is: fixme:ntoskrnl:MmMapLockedPagesSpecifyCache (0x111988, 0, 1, (nil), 0, 32): stub The MmMapLockedPagesSpecifyCache command is used to map memory of a process into the kernel, so that a kernel driver can write / read it. This is necessary since the kernel does not share the same address space as the process. The problem is that this command is a stub and always returns 0 as mapped address. The Tages protection does not check for NULL pointers and tries to write to the address resulting in: wine: Unhandled page fault on write access to 0x00000000 at address 0x57fe27 (thread 0018), starting debugger... The problem is that there is no way to properly implement this on Linux since there is no way to simply map the memory of a different process if you are not inside the kernel. Since wine is no kernel module it can only use memory of different processes, when they explicitly create it as shared memory block. Sadly you can not declare a memory block as shared after it was allocated, so this does not help implementing this command. Anyway in the case of the Tages protection we have some luck since it seems like the process is paused (I think it was waiting for the response of the DeviceIoControl function) while the memory is changed by the windows kernel driver. This allows us to emulate the mapping of the memory by using ReadProcessMemory and WriteProcessMemory. I wrote some hack to implement this, but this only prevented the crash and made the application to exit silently. I either made a mistake in my hack or there is still something else which prevents it from working. --- quote --- Regards -- 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 56

[Bug 55431] New: wine-staging to have same Component as wine
by WineHQ Bugzilla 11 Aug '23

11 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55431 Bug ID: 55431 Summary: wine-staging to have same Component as wine Product: WineHQ Bugzilla Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com CC: austinenglish(a)gmail.com Distribution: --- Could wine-staging bugs have the same Component list as 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 3

[Bug 47996] New: Battlefield 2 - d3d:debug_d3dformat Unrecognized 0x4642564e - Unhandled exception
by WineHQ Bugzilla 11 Aug '23

11 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=47996 Bug ID: 47996 Summary: Battlefield 2 - d3d:debug_d3dformat Unrecognized 0x4642564e - Unhandled exception Product: Wine Version: 4.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: consolelogger(a)rhyta.com Distribution: --- Created attachment 65519 --> https://bugs.winehq.org/attachment.cgi?id=65519 console log with WINEDEBUG=+loaddll Ubuntu 19.10 - wine-mono-4.9.3.msi Battlefield 2 crashes during startup. Console log is attached. I am happy to provide more details and do tests when asked to. -- 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 55416] New: psapi:psapi_main - check_QueryWorkingSetEx() sometimes fails on Windows 10
by WineHQ Bugzilla 11 Aug '23

11 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55416 Bug ID: 55416 Summary: psapi:psapi_main - check_QueryWorkingSetEx() sometimes fails on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - check_QueryWorkingSetEx() sometimes fails on Windows 10: psapi_main.c:1165: Test failed: exe expected Valid=1 but got 0 psapi_main.c:1169: Test failed: exe expected Win32Protection=2 but got 0 See https://test.winehq.org/data/patterns.html#psapi:psapi_main This first happened on 2023-07-11 and there has been three instances so far: * 2023-07-11 win22H2_fgtb-w10pro64-32 * 2023-07-19 win21H2_gitlab-win10-21h2-32 * 2023-08-04 win22H2_newtb-w1064-32 -- 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 55426] New: user32:msg - test_swp_paint_region_on_show() sometimes fails on w7u
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55426 Bug ID: 55426 Summary: user32:msg - test_swp_paint_region_on_show() sometimes fails on w7u Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:msg - test_swp_paint_region_on_show() sometimes fails on w7u: msg.c:9471: Test failed: GetRgnBox (on parent) returned 1 msg.c:9475: Test failed: parent update region: got (0,0)-(0,0), expected (10,10)-(100,100) msg.c:9508: Test failed: GetRgnBox (on parent) returned 1 msg.c:9512: Test failed: parent update region: got (0,0)-(0,0), expected (20,20)-(120,120) See https://test.winehq.org/data/patterns.html#user32:msg This first happened on 2023-07-13 and has happened about once a week since, always on w7u. In particular it does not happen on w7pro64 but then that VM only runs 64-bit tests so maybe this is just 32-bit-specific. * 2023-07-13 win7_newtb-w7u-pt-PT_1 * 2023-07-14 win7_newtb-w7u-de * 2023-07-19 win7_newtb-w7u-es * 2023-08-01 win7_newtb-w7u-2qxl See also bug 55425 which is similar but happens in test_swp_paint_region_on_extend_zerosize() and started one month earlier. -- 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 55425] New: user32:msg - test_swp_paint_region_on_extend_zerosize() sometimes fails on w7u
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55425 Bug ID: 55425 Summary: user32:msg - test_swp_paint_region_on_extend_zerosize() sometimes fails on w7u Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:msg - test_swp_paint_region_on_extend_zerosize() sometimes fails on w7u: msg.c:9569: Test failed: parent update region: got (10,10)-(100,58), expected (10,10)-(100,100) See https://test.winehq.org/data/patterns.html#user32:msg This first happened on 2023-06-13 and has happened about twice a week since, always on w7u. In particular it does not happen on w7pro64 but then that VM only runs 64-bit tests so maybe this is just 32-bit-specific. * 2023-06-13 win7_newtb-w7u-adm * 2023-06-22 win7_newtb-w7u-2qxl * 2023-06-23 win7_newtb-w7u * 2023-06-26 win7_newtb-w7u-2qxl * 2023-07-13 win7_newtb-w7u-2qxl_1 * 2023-07-19 win7_newtb-w7u-el * 2023-08-01 win7_newtb-w7u-adm * 2023-08-08 win7_newtb-w7u-adm -- 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 55381] New: installing synaptics fingerprint reader driver fails
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55381 Bug ID: 55381 Summary: installing synaptics fingerprint reader driver fails Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usb Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 74955 --> https://bugs.winehq.org/attachment.cgi?id=74955 log file trying to install synaptics fingerprint reader driver Attached is the log file when trying to install the synaptics fingerprint reader driver https://download.lenovo.com/pccbbs/mobiles/nz3gf09w.exe It seems to fail with this error: 012c:err:ntdll:NtQueryInformationToken Unhandled token information class 26 When selecting to "extract only" (and not install), this error is not shown. The files are extracted in both cases, when selecting extract only, as well as "install". -- 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 54095] New: quartz:filtermapper sometimes crashes on exit in Wine
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54095 Bug ID: 54095 Summary: quartz:filtermapper sometimes crashes on exit in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- quartz:filtermapper sometimes crashes on exit in Wine: quartz:filtermapper start dlls/quartz/tests/filtermapper.c 0c18:filtermapper: 251 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. quartz:filtermapper:0c18 done (-1073741819) in 0s 94B See https://test.winehq.org/data/patterns.html#quartz:filtermapper Where -1073741819 == 0xc0000005 The crash is pretty rare: one per month on average but there are some two months stretches with no crash. What's interesting is that the invalid memory access happens after the main process has printed the 'test summary' line, which means the crash happened on exit. So it must be caused by previous memory corruption. Also MR!1703 got a timeout on exit which is probably the same underlying issue: quartz:filtermapper start dlls/quartz/tests/filtermapper.c 0af0:filtermapper: 253 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. quartz:filtermapper:0af0 done (258) in 120s 94B -- 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 54845] New: Fusion 360: key_import_pair unsupported key type L"CAPIPRIVATEBLOB"
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54845 Bug ID: 54845 Summary: Fusion 360: key_import_pair unsupported key type L"CAPIPRIVATEBLOB" Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: benjackson990(a)gmail.com Distribution: --- The recent update has changed the login process to allow for a Single Sign On, but in the process seemingly used a encryption not supported in any version of Wine that I'm aware of. Can anyone please advise how I should go about resolving the following issue ``` 0178:fixme:bcrypt:key_import_pair unsupported key type L"CAPIPRIVATEBLOB" 0178:fixme:bcrypt:get_key_property unsupported algorithm 9 ``` -- 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 53712] New: ole32:moniker is broken on Windows 7 in the GitLab WineTest builds
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53712 Bug ID: 53712 Summary: ole32:moniker is broken on Windows 7 in the GitLab WineTest builds Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ole32:moniker is broken on Windows 7 in the GitLab WineTest builds: moniker.c:2280: ACP is 1252 0a18:4þ": 5504 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. ole32:moniker:0a18 done (-1073740791) in 0s 115B Test failed: crash (c0000409) https://test.winehq.org/data/patterns.html#ole32:moniker Where 0xc0000409 == STATUS_STACK_BUFFER_OVERRUN. The failures started on 2022-07-26 which is when the WineTest builds switched from the old build system to GitLab. A test with winetest-889fe64d9f2e.exe (built on 2022-07-25) confirms that this test still succeeds when using binaries from the old build system. -- 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 54545] New: ieframe:webbrowser test_WebBrowser() gets unexpected OnFocus_FALSE calls on Windows 7
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54545 Bug ID: 54545 Summary: ieframe:webbrowser test_WebBrowser() gets unexpected OnFocus_FALSE calls on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ieframe:webbrowser - test_WebBrowser() gets unexpected OnFocus_FALSE calls on Windows 7. For instance: webbrowser.c:1202: Test failed: unexpected call OnFocus_FALSE and sometimes a second failure happens later: webbrowser.c:3434: Test failed: expected OnFocus_FALSE See https://test.winehq.org/data/patterns.html#ieframe:webbrowser The unexpected calls don't happen during a specific test_WebBrowser() call. Up to 2022-11-04 this failure was only happening on w1064v1709 when that stopped. Then on 2023-01-25 is started happening about 3 times per month on the w7u* TestBot VM. -- 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 55430] New: ddraw:ddraw1, ddraw:ddraw2 & ddraw:ddraw7 - test_coop_level_mode_set() is sometimes missing WM_DISPLAYCHANGE on Windows
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55430 Bug ID: 55430 Summary: ddraw:ddraw1, ddraw:ddraw2 & ddraw:ddraw7 - test_coop_level_mode_set() is sometimes missing WM_DISPLAYCHANGE on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw1, ddraw:ddraw2 & ddraw:ddraw7 - test_coop_level_mode_set() is sometimes missing WM_DISPLAYCHANGE on Windows: ddraw1.c:3141: Test failed: Expected message 0x7e, but didn't receive it. ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got (0,0)-(1024,768). ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768. See https://test.winehq.org/data/patterns.html#ddraw:ddraw1 https://test.winehq.org/data/patterns.html#ddraw:ddraw4 https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Where 0x7e == WM_DISPLAYCHANGE This first happened on 2023-04-11 [1] and has happened a bit over once per month since on both Windows 8 and 10. Most of the time it's the first failure in the WineTest run. * 2023-04-11 win81_newtb-w8 (ddraw:ddraw4) * 2023-04-13 win81_newtb-w8adm (ddraw:ddraw1) * 2023-04-25 win81_newtb-w8 (ddraw:ddraw7) * 2023-05-25 win21H1_newtb-w10pro64-he-64 (ddraw:ddraw7) * 2023-05-25 win81_newtb-w8adm (ddraw:ddraw4, preceded by clip rect failures in ddraw 1, 2, 4) * 2023-08-01 win21H1_newtb-w10pro64-ar-64 (ddraw:ddraw4) * 2023-08-03 win81_newtb-w8adm (ddraw:ddraw1) [1] There are older instances but I think those were the consequence of previous failures. -- 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 55429] New: psapi:psapi_main - test_GetPerformanceInfo() sometimes fails on Windows
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55429 Bug ID: 55429 Summary: psapi:psapi_main - test_GetPerformanceInfo() sometimes fails on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - test_GetPerformanceInfo() sometimes fails on Windows: psapi_main.c:716: Test failed: expected approximately 1131 but got 1125 See https://test.winehq.org/data/patterns.html#psapi:psapi_main There are three known instances so far: * 2023-06-16 win1607_newtb-w1064v1607-32 * 2023-06-28 win21H1_newtb-w10pro64-pt-BR-64 * 2023-08-08 win2004_newtb-w10pro64v2004-64 The test counts the total number of threads on the machine in two different ways and expects to find the same or a close enough result. In this case some process with 6 threads must have stopped while the test was running, thus causing the failure. The test also counts handles and processes, both of which could probably also fail in the same way. I think this is another good candidate for the tryok() patch from MR!3418. -- 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 44051] New: Rendering compressed .avi outputs error on program or crashes it
by wine-bugs＠winehq.org 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=44051 Bug ID: 44051 Summary: Rendering compressed .avi outputs error on program or crashes it Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvidc32 Assignee: wine-bugs(a)winehq.org Reporter: lanfrda1(a)gmail.com Distribution: Ubuntu Created attachment 59727 --> https://bugs.winehq.org/attachment.cgi?id=59727 msvidc32 compressed avi render bug log. If you use any codec, it will make an error on the program (E.G. Flash 8), or the program will crash (E.G. SidWiz 2). -- 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 4

[Bug 12428] New: win16 test suite: profile test fails
by wine-bugs＠winehq.org 09 Aug '23

09 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=12428 Summary: win16 test suite: profile test fails Product: Wine Version: CVS/GIT Platform: PC URL: http://win16test.googlecode.com OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=11967) --> (http://bugs.winehq.org/attachment.cgi?id=11967) Backtrace in git +++ This bug was initially created as a clone of Bug #9850 +++ The code can be downloaded from http://win16test.googlecode.com with svn, and is quite easy to run; see http://win16test.googlecode.com/svn/trunk/src/README for instructions. The profile test crashes in current git. Attached is the backtrace in current git. -- 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 9

[Bug 55427] New: ddraw:ddraw7 - test_lighting() sometimes fails on Windows
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55427 Bug ID: 55427 Summary: ddraw:ddraw7 - test_lighting() sometimes fails on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw7 - test_lighting() sometimes fails on Windows: ddraw7.c:4728: Test failed: Lit quad without normals has color 0x00ffff00, expected 0x00000000. ddraw7.c:4741: Test failed: Lit quad with normals has color 0x00ffff00, expected 0x00000000. ddraw7.c:4786: Test failed: Lit quad with light has color 0x00ffffff. ddraw7.c:4786: Test failed: Lit quad with singular world matrix has color 0x00ffffff. ddraw7.c:4786: Test failed: Lit quad with transformation matrix has color 0x00ffffff. ddraw7.c:4786: Test failed: Lit quad with non-affine matrix has color 0x00ffff00. See https://test.winehq.org/data/patterns.html#ddraw:ddraw7 The number of test failures changes from one run to the next, as well as the unexpected color, although it's always a mix of ff and 00. This issue has been there since at least 2023-01-20 and has happened regularly, about 1.5 times per month, on Windows 8 to Windows 10 22H2. -- 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 55374] New: user32:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on Windows 7
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55374 Bug ID: 55374 Summary: user32:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on Windows 7: msg.c:9471: Test failed: GetRgnBox (on parent) returned 1 msg.c:9475: Test failed: parent update region: got (0,0)-(0,0), expected (10,10)-(100,100) msg.c:9508: Test failed: GetRgnBox (on parent) returned 1 msg.c:9512: Test failed: parent update region: got (0,0)-(0,0), expected (20,20)-(120,120) See https://test.winehq.org/data/patterns.html#user32:msg The oldest known failure happened on 2023-06-22 and it has happened a bit over once per week since, always on a w7u test configuration: * 2023-06-22 win7_newtb-w7u-2qxl * 2023-06-23 win7_newtb-w7u * 2023-06-26 win7_newtb-w7u-2qxl * 2023-07-13 win7_newtb-w7u-2qxl_1 * 2023-07-14 win7_newtb-w7u-de * 2023-07-14 win7_newtb-w7u-de * 2023-07-19 win7_newtb-w7u-es * 2023-07-19 win7_newtb-w7u-es -- 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 12427] New: win16 test suite: printdlg test fails
by wine-bugs＠winehq.org 09 Aug '23

09 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=12427 Summary: win16 test suite: printdlg test fails Product: Wine Version: CVS/GIT Platform: PC URL: http://win16test.googlecode.com OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=11966) --> (http://bugs.winehq.org/attachment.cgi?id=11966) Backtrace in git +++ This bug was initially created as a clone of Bug #9850 +++ The code can be downloaded from http://win16test.googlecode.com with svn, and is quite easy to run; see http://win16test.googlecode.com/svn/trunk/src/README for instructions. The printdlg test crashes in current git. Attached is the backtrace in current git. -- 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 8

[Bug 55423] New: dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55423 Bug ID: 55423 Summary: dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows 10: device8.c:695: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:698: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005 device8.c:703: Test failed: GetRegisteredRawInputDevices returned 1, raw_devices_count: 3 device8.c:705: Test failed: Unexpected raw device flags: 0 device8.c:707: Test failed: Unexpected raw device flags: 0 See https://test.winehq.org/data/patterns.html#dinput:device8 Where 0x80070005 == E_ACCESSDENIED This failure mode has been jumping around: * From 2023-01-06 to 2023-03-20 this was happening exclusively on w7u, with one exception, w10pro64-ru-64 on 2023-01-13 (all with "raw_devices_count: 3"). * Then from 2023-03-21 to 2023-05-16 it happened exclusively on various debian11-win32 locales, but with "raw_devices_count: 1". * And since 2023-05-30 it has been happening exclusively on w1064v1507 and w10pro64v2004 (both in 32 and 64-bit) with 12 instances so far, all with "raw_devices_count: 3". See also bug 54558 about other access denied errors in dinput:device8. -- 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 55413] New: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55413 Bug ID: 55413 Summary: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw1 sometimes fails on w1064v1507 and w1046v2004: ddraw1.c:2495: Test failed: Expected message 0x46, but didn't receive it. ddraw1.c:2618: Test failed: Failed to set foreground window. ddraw1.c:2626: Test failed: Failed to set foreground window. ddraw1.c:2652: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2655: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2662: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2671: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2680: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2683: Test failed: Failed to set foreground window. ddraw1.c:2690: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2693: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2706: Test failed: Failed to set foreground window. ddraw1.c:2731: Test failed: Failed to set foreground window. ddraw1.c:2746: Test failed: Failed to set foreground window. ddraw1.c:2755: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2775: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2778: Test failed: Failed to set foreground window. ddraw1.c:2781: Test failed: Expected window style 0x34cf0000, got 0x14cf0000. ddraw1.c:2784: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:3129: Test failed: Failed to set foreground window. ddraw1.c:3130: Test failed: Expected message 0x6, but didn't receive it. ddraw1.c:3135: Test failed: Got unexpected screen size 800x600. ddraw1.c:867: Test failed: Got unexpected wparam 0 for message 0x1c, expected 0x1. ddraw1.c:3141: Test failed: Expected message 0x5, but didn't receive it. ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got (-32000,-32000)-(-31840,-31972). ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768. ddraw1.c:3161: Test failed: Expected message 0x46, but didn't receive it. [...] ddraw1.c:3609: Test failed: Expected (0,0)-(640,480), got (-8,-8)-(648,448). ddraw1.c:4338: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4350: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4362: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4384: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:8051: Test failed: Failed to set foreground window. ddraw1.c:8053: Test failed: Got unexpected hr 0. ddraw1.c:8055: Test failed: Got unexpected hr 0. ddraw1.c:8057: Test failed: Got unexpected hr 0. ddraw1.c:8059: Test failed: Got unexpected hr 0. ddraw1.c:8069: Test failed: Got unexpected hr 0. ddraw1.c:8071: Test failed: Got unexpected hr 0. ddraw1.c:8073: Test failed: Got unexpected hr 0. ddraw1.c:8077: Test failed: Failed to set foreground window. ddraw1.c:8079: Test failed: Got unexpected hr 0. ddraw1.c:8081: Test failed: Got unexpected hr 0. ddraw1.c:8087: Test failed: Got unexpected hr 0. ddraw1.c:8135: Test failed: Failed to set foreground window. ddraw1.c:8147: Test failed: Failed to set foreground window. ddraw1.c:13670: Test failed: WM_KILLFOCUS was not received. ddraw1.c:13706: Test failed: Got unexpected hr 0x887600e1. ddraw1.c:13709: Test failed: Got unexpected hr 0x887600ff. 0a60:ddraw1: unhandled exception c0000005 at 00007FF6FFAE2567 See https://test.winehq.org/data/patterns.html#ddraw:ddraw1 Where 0x46 == WM_WINDOWPOSCHANGING and the test window does not seem to be visible: expected: 0x14cf0000 == WS_VISIBLE | 0x04cf0000 This failure happens irregularly and only on w1064v1507 and w1046v2004 so far: * 2022-12-14 win1507_newtb-w1064v1507-64 * 2022-12-15 win1507_newtb-w1064v1507-64 * 2023-01-31 win1507_newtb-w1064v1507-64 * 2023-02-16 win1507_newtb-w1064v1507-64 * 2023-06-07 win1507_newtb-w1064v1507-64 * 2023-06-09 win1507_newtb-w1064v1507-32 * 2023-07-13 win1507_newtb-w1064v1507-64 * 2023-07-27 win2004_newtb-w10pro64v2004-64 -- 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 55388] New: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd
by WineHQ Bugzilla 09 Aug '23

09 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55388 Bug ID: 55388 Summary: d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd: visual.c:19496: Test failed: Failed to draw, hr 0x80004005. visual.c:19792: Test failed: Got unexpected color 0x0000ff00. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 53423] New: Baldur's gate 3 need allocation callbacks for winevulkan
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53423 Bug ID: 53423 Summary: Baldur's gate 3 need allocation callbacks for winevulkan Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: charles2000wang(a)gmail.com Distribution: --- Baldur's gate 3 crashes on startup when using the vulkan renderer. These are the error messages in terminal 0140:fixme:vulkan:wine_vkCreateWin32SurfaceKHR Support for allocation callbacks not implemented yet 0140:fixme:vulkan:__wine_create_vk_device_with_callback Support for allocation callbacks not implemented yet It seems that winevulkan does not have allocation callbacks. -- 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 51122] New: 5.0.3 vs 6.x - slow performance in graphics
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=51122 Bug ID: 51122 Summary: 5.0.3 vs 6.x - slow performance in graphics Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mondane.woodworker(a)gmail.com Distribution: --- When I use 6.x, even 'winecfg' starts like a slideshow. This doesn't happen with 5.0.3 . No application can be ran like this. Using: * Wine 6.0 - 6.7 * Ubuntu Unity 20.04.1 ( https://ubuntuunity.org/ ) * Laptop: Dell Precision 7550 * Graphics: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q] ** Using nvidia-driver-460 -- 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 55419] New: dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55419 Bug ID: 55419 Summary: dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an event in Wine: dxgi.c:7876: Test failed: Expected event fired. See https://test.winehq.org/data/patterns.html#dxgi:dxgi The first known instance goes back to 2023-01-26 and it has been happening a bit over twice per month since, mostly on the debiant VM but also on the GitLab CI environment and fg-deb64 (my desktop). -- 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 55418] New: quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv
by WineHQ Bugzilla 08 Aug '23

08 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55418 Bug ID: 55418 Summary: quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on w11pro64_nv: vmr9.c:3475: this is the last test seen before the exception 1828:vmr9: unhandled exception c0000005 at 000000000049805A See https://test.winehq.org/data/patterns.html#quartz:vmr9 This is crash happened only twice so far and both times on w11pro64_nv, the TestBot's Windows 11 Nvidia RTX 3050 VM: * 2023-08-04 w11pro64-nv-64 * 2023-03-03 w11pro64-nv-64 -- 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 55396] New: advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm
by WineHQ Bugzilla 07 Aug '23

07 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55396 Bug ID: 55396 Summary: advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry breaks test_registerOIDFunction() in crypt32:oid on w8adm: oid.c:297: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:303: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:305: Test failed: Could not delete bogus key oid.c:314: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:321: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:325: Test failed: Could not delete CryptDllEncodeObject key oid.c:336: Test failed: CryptUnregisterOIDFunction failed: 2 oid.c:340: Test failed: Could not delete CryptDllEncodeObject key oid.c:343: Test failed: Could not delete 'EncodingType 3' key oid.c:377: Test failed: Expected ERROR_FILE_EXISTS, got 00000000 oid.c:382: Test failed: Expected ERROR_FILE_EXISTS, got 00000000 oid.c:390: Test failed: Expected key to exist, RegOpenKeyA failed: 2 oid.c:412: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002 oid.c:416: Test failed: CryptUnregisterDefaultOIDFunction failed: 00000002 oid.c:430: Test failed: CryptUnregisterDefaultOIDFunction failed See https://test.winehq.org/data/patterns.html#crypt32:oid More precisely these failures only happen if running advapi32:registry before crypt32:oid. Furthermore the failures started on 2023-07-27 which is when the w8 VM's memory was increased to 4GB, and older WineTest builds still produce the failures. So the 2023-07-27 VM change is the cause of these failures but it's not clear why. -- 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 657] Many games and applications need 'mfc42.dll' ('winetricks -q mfc42' is a workaround)
by WineHQ Bugzilla 07 Aug '23

07 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=657 Bartosz <gang65(a)poczta.onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65(a)poczta.onet.pl -- 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 55412] New: Super Bubsy crashes before the intro
by WineHQ Bugzilla 06 Aug '23

06 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55412 Bug ID: 55412 Summary: Super Bubsy crashes before the intro 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: spzakulec(a)gmail.com Distribution: --- Created attachment 74972 --> https://bugs.winehq.org/attachment.cgi?id=74972 wine console output and backtrace from crash When I try to install & run Super Bubsy as specified in the AppDB page: https://appdb.winehq.org/objectManager.php?sClass=version&iId=19820 the game crashes right away. Per the AppDB instructions (reproduced below), I've tried to install the game and run it with the videomemorysize=512M winetricks verb. WINEPREFIX="$HOME/SuperBubsy" WINEARCH=win32 wine wineboot WINEPREFIX="$HOME/SuperBubsy" winecfg ---> set Windows 95, do not allow to decorate windows, emulate desktop WINEPREFIX="$HOME/SuperBubsy" winetricks videomemorysize=512 Install the game and to run it: WINEPREFIX="$HOME/SuperBubsy" wine $HOME/SuperBubsy/drive_c/SUPER\ BUBSY/Bubsy.exe I'm on KDE Neon 5.27, using Wine 8.13. -- 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 54825] New: Visual Studio C++ Build Tools fails to install with 'Could not find Windows Runtime type'
by WineHQ Bugzilla 06 Aug '23

06 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54825 Bug ID: 54825 Summary: Visual Studio C++ Build Tools fails to install with 'Could not find Windows Runtime type' Product: Wine-staging Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lupino8211(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74328 --> https://bugs.winehq.org/attachment.cgi?id=74328 full_install.log I'm trying to install MSVC toolchain in wine in docker, but didn't succeed. I'm installing tools in following order: - dotnet48 - winecfg /v win10 - Visual Studio C++ Build Tools Installation ends in the following error (from logs which can be found in wine user's Temp directory): [025c:000a][2023-04-13T20:48:57] Error 0x80131522: Rethrowing the exception from the engine: Could not find Windows Runtime type 'Windows.Networking.Connectivity.NetworkCostType'. but how I can inspect, these DLL's exist in the following paths: /root/.wine/drive_c/windows/system32/windows.networking.connectivity /root/.wine/drive_c/windows/syswow64/windows.networking.connectivity and should contain mentioned type. How to reproduce: Download vs_BulidTools.exe from https://download.visualstudio.microsoft.com/download/pr/d24d0627-f1e2-4a69-… Install it via: wine cmd /c start /wait vs_BuildTools.exe \--quiet --add "Microsoft.VisualStudio.Workload.VCTools;includeRecommended" --add "Microsoft.VisualStudio.Workload.MSBuildTools;includeRecommended" --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools;includeRecommended" --add "Microsoft.VisualStudio.Component.VC.Tools.x86.x64;includeRecommended" -- 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 25100] New: the program don't start...
by wine-bugs＠winehq.org 06 Aug '23

06 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=25100 Summary: the program don't start... Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: salvatore91salvatore(a)yahoo.it .... -- 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 3

[Bug 55406] New: mIRC hangs on receiving a new PM
by WineHQ Bugzilla 06 Aug '23

06 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55406 Bug ID: 55406 Summary: mIRC hangs on receiving a new PM Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kooldioxide(a)gmail.com Distribution: --- This problem started once I upgraded mIRC to version 7.74. When someone sends me a PM and this causes mIRC to open a new window, mIRC hangs entirely, and the process keeps using a lot of CPU according to htop. Only thing I can do at that point is kill the process. The problem doesn't occur if I already have a query window open with the person sending me a message. An easy way to reproduce this is to connect to an IRC server, then from the status window: /msg <my_own_nick> hello That will open a query window to yourself which triggers this behaviour as well. This problem occurs on two different Linux installations I tried, one with Wine 8.12 and one with Wine 8.0.2. -- 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 32900] New: The Bat 5.2.2 - keyboard keys stick
by wine-bugs＠winehq.org 05 Aug '23

05 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=32900 Bug #: 32900 Summary: The Bat 5.2.2 - keyboard keys stick Product: Wine Version: 1.1.22 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sprog(a)online.ru Classification: Unclassified It happens rarely and may be related to RU keyboard layout. You press Cntr-N a new message form is created but pressing letters on a keyboard won't work as expected. If fact it's like you're constantly holding right CTL key. You press right CTL again and the bug disappears.... The same happens happens with ALT key too. The probles was in Wine versions starting from 1.4.1 Unfortunately I can't give you the conditions how to reproduce the bug. This report is more like "think about what could go wrong". If you can advise how to trace this problem - I'll do it. The Bat all so has problems with ole32. From to time the Connection Center causes OLE32 error. The conditions are unkown. It happens once if 2-3 days. After that the connection center works but the status bar is showing OLE32 error... -- 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 7

[Bug 55393] New: The process which started "The Bat!" is still running after the app ist quieted
by WineHQ Bugzilla 05 Aug '23

05 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55393 Bug ID: 55393 Summary: The process which started "The Bat!" is still running after the app ist quieted 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: mywine(a)schiermeier-it.de Distribution: --- Created attachment 74957 --> https://bugs.winehq.org/attachment.cgi?id=74957 Part of "ps faux" command Setting: "The Bat!" is installed by its installer and "GnuPG" is also installed with its installer. "The Bat!" is starting normally and the encrypting is working. A mail was created, encrypted, or signed and sent. Now "The Bat!" is quieted by its menu entry. The GUI disappears. Now "(h)top" or "ps" shows still some processes running and can only be quieted with "kill": ---ps faux--- USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND (...) joerg 3281 3.4 0.0 19668 19144 ? Ss 00:59 0:08 /opt/wine-devel/bin/wineserver joerg 3285 0.0 0.0 2380696 16724 ? Ssl 00:59 0:00 C:\windows\system32\services.exe joerg 3288 0.1 0.0 2055360 15552 ? Ssl 00:59 0:00 C:\windows\system32\winedevice.exe joerg 3297 0.8 0.0 2297900 38264 ? Ssl 00:59 0:02 C:\windows\system32\winedevice.exe joerg 3306 0.1 0.0 2142560 29912 ? Ssl 00:59 0:00 C:\windows\system32\plugplay.exe joerg 3314 0.0 0.0 1919060 9596 ? Ssl 00:59 0:00 C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted joerg 3325 0.1 0.1 2169640 86012 ? Sl 00:59 0:00 C:\windows\system32\explorer.exe /desktop joerg 3330 0.0 0.0 2247080 14336 ? Ssl 00:59 0:00 C:\windows\system32\rpcss.exe joerg 3618 0.4 0.0 2704816 30700 ? Ss 01:00 0:00 z:\opt\winprog\GnuPG\bin\gpg-agent.exe --homedir c:\users\username\appdata\roaming\gnupg-tb --use-standard-socket --daemon ---///--- See also the attached log file. Internally the GnuPG is started from The Bat! via the command line. For another purpose (and wine bug) I wrote a little wrapper to log the commands which The Bat!s hands over to GnuPGs exe-file (gpg.exe). -- 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 49845] New: Sacred Gold: very bad performance (low fps) when zoomed out
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=49845 Bug ID: 49845 Summary: Sacred Gold: very bad performance (low fps) when zoomed out Product: Wine Version: 5.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: phaidros(a)gmx.at Distribution: --- Sacred 1 Gold provides 3 zoom levels: Very close, middle and zoomed out. I guess most people really only use the zoomed out setting, the other two show such a small portion of the world that i don't know how anybody could enjoy the experience. Unfortunately the zoomed out setting gives very bad performance, around 20fps on a Ryzen 2700X @ 3.7GHz. Using the middle zoom setting fps go up to about 30-35fps and the very close zoom setting gives 55-60fps. I don't really understand what's going on, I think this is a very old game and a 8-core 3.7GHz CPU should have no problem whatsoever to run it. The 20fps i'm getting make the game really unenjoyable to the extent where i would rather boot windows to play it (where i'm getting 60fps at all zoom levels). I tried with and without CSMT, fixing the process to a single CPU core etc. Unfortunately no luck. It is really strange that the game would run at almost 60fps when zoomed in and then take such a massive performance hit when zooming out. -- 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 53956] New: Sacred Underworld crashes after launching
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53956 Bug ID: 53956 Summary: Sacred Underworld crashes after launching Product: Wine Version: 7.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Alexandr42suv(a)mail.ru Distribution: --- Created attachment 73536 --> https://bugs.winehq.org/attachment.cgi?id=73536 automatically generated backtrace When I was trying to run Sacred Underworld 2.28, I got an error message and game crashes. Other games or windows programs works well CPU: Intel Core i3-4005u GPU: Intel HD Graphics 4400 -- 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 14

[Bug 54124] New: Sacred Underworld black screen hanging
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54124 Bug ID: 54124 Summary: Sacred Underworld black screen hanging Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: VladimirVSC(a)yandex.ru Distribution: --- Created attachment 73656 --> https://bugs.winehq.org/attachment.cgi?id=73656 Sacred Underworld crash report When starting the game, the black screen appears which hangs until you press Escape or anything else. Then "Application is not responding" message appears and the game crashes to desktop. The same for stable 7.0.1 and 8.0-rc1. -- 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 39236] New: shell32:shlfileop fails if privileges not high enough
by wine-bugs＠winehq.org 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=39236 Bug ID: 39236 Summary: shell32:shlfileop fails if privileges not high enough Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- If the user cannot write to the root of the c: drive the test fails with the following errors: shlfileop.c:2497: Test failed: The file does not exist shlfileop.c:2499: Test failed: File is not removed, ErrorCode: 1026 shlfileop.c:94: Test failed: Failure to open file shlfileop.c:2505: Test failed: The file does not exist shlfileop.c:2507: Test failed: File is not removed, ErrorCode: 1026 In particular one can notice this bug on the following WineTest box: fg-win2000-rusr: Windows 2000 with a Restricted user account The test should try to write its Unicode file in the temporary directory. The test regression was introduced by this commit: commit 1fc0cb75eebeb011a1f620fb96f32245d886916c Author: Nigel Liang <ncliang(a)gmail.com> Date: Fri Jun 8 14:25:24 2007 -0700 shell32: Conformance tests for unicode filenames and fix a bug for file deletion. -- 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 4

[Bug 55395] New: dinput:force_feedback - test_device_managed_effect() sometimes fails on w8
by WineHQ Bugzilla 03 Aug '23

03 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55395 Bug ID: 55395 Summary: dinput:force_feedback - test_device_managed_effect() sometimes fails on w8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:force_feedback - test_device_managed_effect() sometimes fails on w8: driver_bus.c:290: Test failed: id 1: force_feedback.c:4180 got spurious packet driver_bus.c:1098: Test failed: id 1: force_feedback.c:4180 expect[0]: got 0xb000f, expected 0 driver_bus.c:1099: Test failed: id 1: force_feedback.c:4180 expect[0]: got id 6 driver_bus.c:1100: Test failed: id 1: force_feedback.c:4180 expect[0]: got len 2 See https://test.winehq.org/data/patterns.html#dinput:force_feedback These failures are specific to the 32-bit Windows 8 TestBot VM, w8, and they happened 5 times over the past 8 months: * 2022-12-09 win81_newtb-w8 * 2023-01-31 win81_newtb-w8 * 2023-05-05 win81_newtb-w8 * 2023-05-26 win81_newtb-w8 * 2023-07-27 win81_newtb-w8 -- 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 55298] New: gdi32:font fails the MS Shell Dlg tests in the Arabic, Japanese and Chinese locales in Wine
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55298 Bug ID: 55298 Summary: gdi32:font fails the MS Shell Dlg tests in the Arabic, Japanese and Chinese locales in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:font fails the MS Shell Dlg tests in the Arabic, Japanese and Chinese locales in Wine: test_nonexistent_font() font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial font.c:4181: Test failed: MS Shell Dlg should be enumerated font.c:4183: Test failed: MS Shell Dlg should be enumerated font.c:4192: Test failed: expected MS Shell Dlg, got Arial font.c:4205: Test failed: expected MS Shell Dlg, got Arial test_EnumFonts_subst() font.c:5507: Test failed: MS Shell Dlg should be enumerated font.c:5509: Test failed: MS Shell Dlg should be enumerated as a TrueType font font.c:5529: Test failed: MS Shell Dlg should be enumerated font.c:5530: Test failed: MS Shell Dlg should be enumerated See https://test.winehq.org/data/patterns.html#gdi32:font This happens on both the TestBot's Debian11 and Testing VMs. -- 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 55339] New: d3d9:visual - add_dirty_rect_test() fails on w11pro64_nv
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55339 Bug ID: 55339 Summary: d3d9:visual - add_dirty_rect_test() fails on w11pro64_nv Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - add_dirty_rect_test() fails on w11pro64_nv: visual.c:19792: Test failed: Got unexpected color 0x00adbeef. See https://test.winehq.org/data/patterns.html#d3d9:visual This failure goes back to at least 2022-11-23, is systematic and specific to w11pro64_nv, the TestBot's only NVidia test configuration. -- 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 55392] New: d3d9:visual - test_color_clamping() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55392 Bug ID: 55392 Summary: d3d9:visual - test_color_clamping() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_color_clamping() fails on w11pro64-amd: visual.c:24213: Test failed: Got unexpected color 0x00000000, case 1. See https://test.winehq.org/data/patterns.html#d3d9:visual This failure is systematic and only happens on w11pro64-amd (AMD RX 6600). In particular it does not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor does it happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55391] New: d3d9:visual - test_uninitialized_varyings() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55391 Bug ID: 55391 Summary: d3d9:visual - test_uninitialized_varyings() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_uninitialized_varyings() fails on w11pro64-amd: visual.c:23014: Test failed: Got unexpected color 0x00000000, case 3. visual.c:23014: Test failed: Got unexpected color 0x00000000, case 6. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55390] New: d3d9:visual - test_updatetexture() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55390 Bug ID: 55390 Summary: d3d9:visual - test_updatetexture() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_updatetexture() fails on w11pro64-amd: visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 12. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 13. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 14. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 0, 15. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 12. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 13. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 14. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 1, 15. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 5. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 7. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 10. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 11. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 12. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 13. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 14. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 15. visual.c:22359: Test failed: Failed to update texture, hr 0x80004005, case 2, 18. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55389] New: d3d9:visual - test_per_stage_constant() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55389 Bug ID: 55389 Summary: d3d9:visual - test_per_stage_constant() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_per_stage_constant() fails on w11pro64-amd: visual.c:20134: Test failed: Got unexpected color 0x000000ff. visual.c:20152: Test failed: Got unexpected color 0x000000ff. visual.c:20170: Test failed: Got unexpected color 0x000000ff. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55387] New: d3d9:visual - test_fetch4() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55387 Bug ID: 55387 Summary: d3d9:visual - test_fetch4() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - test_fetch4() fails on w11pro64-amd: visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff131313 at (40, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff121212 at (200, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff111111 at (360, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff101010 at (520, 30). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff020202 at (40, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff2f2f2 at (200, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff1f1f1 at (360, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff010101 at (520, 150). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff040404 at (40, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff4f4f4 at (200, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xfff3f3f3 at (360, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff030303 at (520, 270). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff232323 at (40, 390). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff222222 at (200, 390). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff212121 at (360, 390). visual.c:16281: Test failed: Test texldd: Got unexpected colour 0xff202020 at (520, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (520, 30). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 150). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 150). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 150). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (520, 270). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (40, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (200, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (360, 390). visual.c:16281: Test failed: Test texldb: Got unexpected colour 0x00000000 at (520, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff131313 at (40, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff121212 at (200, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff111111 at (360, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff101010 at (520, 30). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff020202 at (40, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff2f2f2 at (200, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff1f1f1 at (360, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff010101 at (520, 150). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff040404 at (40, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff4f4f4 at (200, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xfff3f3f3 at (360, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff030303 at (520, 270). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff232323 at (40, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff222222 at (200, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff212121 at (360, 390). visual.c:16281: Test failed: Test texldl: Got unexpected colour 0xff202020 at (520, 390). See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55382] New: d3d9:device - test_draw_primitive() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55382 Bug ID: 55382 Summary: d3d9:device - test_draw_primitive() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:device test_draw_primitive() fails on w11pro64-amd: device.c:3194: Test failed: DrawIndexedPrimitive failed, hr 0x80004005. See https://test.winehq.org/data/patterns.html#d3d9:device Where 0x80004005 == E_FAIL This failure is systematic and only happens on w11pro64-amd (AMD RX 6600). In particular it does not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor does it happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55386] New: d3d9:visual - depth_clamp_test() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55386 Bug ID: 55386 Summary: d3d9:visual - depth_clamp_test() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:visual - depth_clamp_test() fails on w11pro64-amd: visual.c:14932: Test failed: color 0x0000ff00. visual.c:14934: Test failed: color 0x0000ff00. visual.c:14936: Test failed: color 0x0000ff00. visual.c:14938: Test failed: color 0x0000ff00. visual.c:14940: Test failed: color 0x0000ff00. See https://test.winehq.org/data/patterns.html#d3d9:visual These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55384] New: d3d9:device - test_update_volumetexture() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55384 Bug ID: 55384 Summary: d3d9:device - test_update_volumetexture() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:device - test_update_volumetexture() fails on w11pro64-amd: device.c:10425: Test failed: Failed to update texture, hr 0x80004005, case 6. device.c:10425: Test failed: Failed to update texture, hr 0x80004005, case 7. See https://test.winehq.org/data/patterns.html#d3d9:device Where 0x80004005 == E_FAIL These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 55385] New: d3d9:device - test_surface_format_null() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55385 Bug ID: 55385 Summary: d3d9:device - test_surface_format_null() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:device - test_surface_format_null() fails on w11pro64-amd: device.c:9328: Test failed: Expected non-zero pitch, got 0. device.c:9329: Test failed: Expected non-NULL pBits, got 0000000000000000. See https://test.winehq.org/data/patterns.html#d3d9:device These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they do not happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 43859] New: Snake Pass: In-game textures appear Black, White or Fuchsia and are extremely bright.
by wine-bugs＠winehq.org 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=43859 Bug ID: 43859 Summary: Snake Pass: In-game textures appear Black, White or Fuchsia and are extremely bright. Product: Wine Version: 2.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jason.bagavatsingham(a)gmail.com Distribution: --- Created attachment 59430 --> https://bugs.winehq.org/attachment.cgi?id=59430 Terminal Log Found: Upon reaching in-game, the worlds geometry is rendered correctly, but all assets are extremely bright and appear Black, White or Fuchsia. Some colours are visible, but overshadowed by the bloominess of the aforementioned colours. Steps to reproduce: # Launch Steam. # Launch Snake Pass. # Select New Game / Continue and select a level. Actual Results: In-game rendering is extremely bright and many of the textures appear completely White, Black or colours ranging around Fuchsia. Expected Results: Texture appears correctly on all assets while in-game. *Reproduction Rate:* 5/5. Notes: Menus / 2D assets appear correctly. See link below for video of the issues: https://www.youtube.com/watch?v=f5KtPyHnJyI Environment: Wine-Staging 2.18 -- 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 42424] New: Error occurs while installing Renesas_Flash_Programmer_Package_V30201_free.exe.
by wine-bugs＠winehq.org 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=42424 Bug ID: 42424 Summary: Error occurs while installing Renesas_Flash_Programmer_Package_V30201_free.exe. Product: Wine Version: 2.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kiwamu(a)debian.or.jp Distribution: --- Created attachment 57250 --> https://bugs.winehq.org/attachment.cgi?id=57250 Screen shot when the error occurs The issue is reproduced by following: 1. Download Renesas_Flash_Programmer_Package_V30201_free.exe from following: https://www.renesas.com/ja-jp/software/D4000308.html 2. Run the Renesas_Flash_Programmer_Package_V30201_free.exe with following: $ wine Renesas_Flash_Programmer_Package_V30201_free.exe 3. You should see attached screen shot named "shot.png". Could you support this issue? Best regards, -- Kiwamu Okabe -- 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 47588] New: AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging
by wine-bugs＠winehq.org 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=47588 Bug ID: 47588 Summary: AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mortenweb43(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 64993 --> https://bugs.winehq.org/attachment.cgi?id=64993 AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging AmiKitXE crashes on PlayOnLinux 4.3 with Wine 3.21-staging Please help make it work again :-) Error log is attached. 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.

2 3

[Bug 55380] New: d3d9:d3d9ex - test_swapchain_parameters() fails on w11pro64-amd
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55380 Bug ID: 55380 Summary: d3d9:d3d9ex - test_swapchain_parameters() fails on w11pro64-amd Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d9:d3d9ex - test_swapchain_parameters() fails on w11pro64-amd: d3d9ex.c:3763: Test failed: Expected hr 0, got 0x80004005, test 23. d3d9ex.c:3799: Test failed: Expected hr 0, got 0x80004005, test 23. d3d9ex.c:3763: Test failed: Expected hr 0, got 0x80004005, test 25. d3d9ex.c:3799: Test failed: Expected hr 0, got 0x80004005, test 25. See https://test.winehq.org/data/patterns.html#d3d9:d3d9ex Where 0x80004005 == E_FAIL These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In particular they don't happen on fgtb-w10pro64-rx550 the only other test machine to have an AMD GPU, nor do they happen on the other Windows 11 test machines (w11pro64 and w11pro64-nv). -- 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 41395] New: CreateFile returns a wrong LastError Code when you pass an invalid path
by wine-bugs＠winehq.org 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=41395 Bug ID: 41395 Summary: CreateFile returns a wrong LastError Code when you pass an invalid path Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: Christoph(a)ApiViewer.de Distribution: --- CreateFile returns a wrong LastError Code when you pass an invalid path. Testcase: CreateFileA("C:C:\\Windows", GENERIC_READ, FILE_SHARE_READ, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL); todo_wine ok( GetLastError() == ERROR_INVALID_NAME, "Wrong LastError %d, expected ERROR_INVALID_NAME\n", GetLastError() ); Which also means the code in cryptnet_main:1025 to line 1048 must be wrong. -- 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 2

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