wine-bugs October 2023

wine-bugs@winehq.org

1 participants
3027 discussions

[Bug 55791] New: Unhandled Exception error when running Blitz.exe with Windows 10 compatibility
by WineHQ Bugzilla 14 Oct '23

14 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55791 Bug ID: 55791 Summary: Unhandled Exception error when running Blitz.exe with Windows 10 compatibility Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kubilay12344(a)hotmail.nl Distribution: --- Created attachment 75274 --> https://bugs.winehq.org/attachment.cgi?id=75274 Contains the debug information I am encountering an "Unhandled exception" error when trying to run Blitz.exe on Wine with Windows 10 compatibility. The error message is as follows: wine: Unhandled exception 0x80000003 in thread 24 at address 01C03A35 (thread 0024), starting debugger... Steps to Reproduce: 1. Install Wine on Pop!_OS (version details below). 2. Set Wine to Windows 10 compatibility mode. 3. Run Blitz.exe. Expected Results: The application should run without any errors. Actual Results: The application fails to run and throws an "Unhandled exception" error. Additional Information: - Wine version: wine-6.0.3 (Ubuntu 6.0.3~repack-1) - Platform: i386 (WOW64) - Version: Windows 10 - Host system: Linux - Host version: 6.5.4-76060504-generic -- 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 55787] New: Use PipeWire/PulseAudio for synthing MIDI instead of FluidSynth
by WineHQ Bugzilla 14 Oct '23

14 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55787 Bug ID: 55787 Summary: Use PipeWire/PulseAudio for synthing MIDI instead of FluidSynth Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dmusic Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- I feel like using software synth can be waste of RAM and CPU cycles when hardware synth is available. PipeWire/PulseAudio have capabilities to pass MIDI to either hardware devices or software synth daemons, such as TiMidity++ or FluidSynth. There are 2 problems with it: 1. One cannot set a soundfont via it, usually a special binaries run as root like asfxload are needed, and sound font affects all the apps using the device. We need ways to do it via PipeWire for unprivileged processes. IMHO even ignoring it is not a big problem: the fonts installed from packages are of high-enough quality, and sound much better (as instruments, not as beeps) than the software synth used by Windows OSes. 2. There is no autorouting for MIDI in PipeWire, one has to choose the sink himself. It could be configurable in winecfg. Also it is highly desireable to have a pretty standalone shared lib automatically selecting the needed sink. -- 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 25988] New: Mr. Smoozles Goes Nutso: problems playing sound
by wine-bugs＠winehq.org 14 Oct '23

14 Oct '23

http://bugs.winehq.org/show_bug.cgi?id=25988 Summary: Mr. Smoozles Goes Nutso: problems playing sound Product: Wine Version: 1.3.12 Platform: x86 URL: http://www.juniper-games.com/smoozles/Nutsosetup.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=33126) --> (http://bugs.winehq.org/attachment.cgi?id=33126) terminal output (only built-in dlls) The game is a nice, freeware adventure puzzle game. Neither sound nor music is playing in the game with a clean Wine install. After installing the directmusic components via winetricks and starting Timidity as a separate process music is playing fine in the menu and in some of the scenes. However there are still problems playing sound effects during gameplay: it is most noticeable in the first scene where a simple sound effect is intended to play (sounds like a shooting sound). The game becomes almost unplayable because of a strange lagging issue: the game barely responds to keyboard events while the sound is playing. Once you manage to make it past the first scene, gameplay seems to be back to normal in the second scene. It seems that the lagging issue has something to do with the looping sound effect during the first scene. The first log is showing the output without native directmusic dlls. -- 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 13

[Bug 55785] New: WineD3D PolygonOffset scale factor detection failed on Intel HD grapgics
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55785 Bug ID: 55785 Summary: WineD3D PolygonOffset scale factor detection failed on Intel HD grapgics Product: Wine Version: 8.18 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com Trying any D3D application on Intel HD graphics 3000 0764:fixme:d3d_shader:print_glsl_info_log No errors. 0764:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #1: 0764:fixme:d3d_shader:print_glsl_info_log No errors. 0764:fixme:d3d:wined3d_caps_gl_ctx_test_filling_convention Unexpected filling co nvention test result. 0764:fixme:d3d:wined3d_caps_gl_ctx_test_filling_convention Unexpected filling co nvention test result. 0764:fixme:d3d:wined3d_adapter_find_fill_offset Did not find a way to get the fi lling convention we want. 0764:err:d3d:wined3d_adapter_find_polyoffset_scale PolygonOffset scale factor de tection failed, using fallback value 2^23. 0764:err:d3d:wined3d_adapter_find_polyoffset_scale PolygonOffset scale factor de tection failed, using fallback value 2^23. -- 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 55632] New: ntdll:file - test_file_link_information() fails on Windows 10 1709 and older
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55632 Bug ID: 55632 Summary: ntdll:file - test_file_link_information() fails on Windows 10 1709 and older Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:file - test_file_link_information() fails on Windows 10 1709 and older: file.c:2249: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2251: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2256: Test failed: file should exist file.c:2291: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2321: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2323: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2354: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2356: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2367: Test failed: Link did not change casing on existing target file: got L"foo3368.tmp" file.c:2399: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2434: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2472: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2522: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2559: Test failed: res expected STATUS_OBJECT_NAME_COLLISION or STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2599: Test failed: res expected STATUS_OBJECT_NAME_COLLISION or STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2637: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2676: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2716: Test failed: res expected STATUS_OBJECT_NAME_COLLISION or STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2756: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2798: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2833: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2867: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2901: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2903: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2908: Test failed: file should exist file.c:2942: Test failed: got status c0000003 file.c:2948: Test failed: got io status 0xdeadbeef file.c:2950: Test failed: got status c0000003 file.c:2976: Test failed: got status c0000003 file.c:2982: Test failed: got io status 0xdeadbeef file.c:2984: Test failed: got status c0000003 file.c:2992: Test failed: Link did not change casing on same file: got L"foo3396.tmp" See https://test.winehq.org/data/patterns.html#ntdll:file Where 0xc0000003 == STATUS_INVALID_INFO_CLASS These failures are systematic and started happening on 2023-09-19. A bisect shows that these started with the commit below: commit 67479f8c2fc03c2043b8414bc063e671e36fdbda Author: Joel Holdsworth <joel(a)airwebreathe.org.uk> AuthorDate: Fri Sep 15 17:49:52 2023 +0100 ntdll/tests: Test both FileRenameInformation and FileRenameInformationEx in test_file_rename_information. Signed-off-by: Joel Holdsworth <joel(a)airwebreathe.org.uk> -- 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 44276] New: Poor resolution change handling with Shadow of Memories demo
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=44276 Bug ID: 44276 Summary: Poor resolution change handling with Shadow of Memories demo Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Created attachment 60099 --> https://bugs.winehq.org/attachment.cgi?id=60099 Log from successful demo gameplay start When game starts (fresh boot) it shows only the upper-left quadrant of the logo screens. It then changes resolution and shows the intro video the size of a postage stamp (often loses focus and an alt-tab is needed to see it). It then shows only the upper-left quadrant of the main menu. It's possible to pan around and see all of it but the button graphics don't align with the buttons so they're hard to target with the pointer. At the main menu, if the game is started it often freezes at the "Prologue" screen. Alt-tabbing during these various stages can trigger some odd effects (at least with the Nvidia proprietary driver). The game will crash, the screen gets left at a low resolution, etc. Eventually the behavior changes - the game launches the opening screens correctly sized but with the Xfce desktop panel still visible. The game will then be startable (won't freeze at the "Prologue" screen). It still seems to freeze further along, normally after the tea house scene when control is returned to the player. The behavior is persistent until the system is rebooted. The CD version of the game acts the same except it never seems to get past "Prologue". Some of this may be related to bug #44275. Install notes (demo download link on same page): https://appdb.winehq.org/objectManager.php?sClass=version&iId=31628#notes System tested: Xubuntu 17.04 x86, Intel Pentium D 3.46GHz, GeForce 8600 GT with Nvidia 340.102 driver. wine-staging 2.21.0~zesty from dl.winehq.org -- 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 55708] New: cpython 3.12.0 fails to run on wine
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55708 Bug ID: 55708 Summary: cpython 3.12.0 fails to run on wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: propsys Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)bochs.info Distribution: --- cpython 3.12.0 (released today) fails to run in wine on Linux, due to a new module _wmi which depends on VariantToString. This is stubbed in wine's propsys.dll: "Unimplemented function propsys.dll.VariantToString called at address ..." It's unclear if anything else is broken, because the process halts here. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 55674] New: 64-bit wineserver/wine-preloader hangs on macOS 14.
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55674 Bug ID: 55674 Summary: 64-bit wineserver/wine-preloader hangs on macOS 14. Product: Wine Version: 8.16 Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com This is a regression introduced by a81c53504ae32715e6e91bd020fdebd5bef20d48. Before this commit, I can run Notepad++ with a WOW64 build on macOS 14. But now, I can't even start `winecfg` and create a wineprefix. I don't reproduce this issue with 64-bit Wine on Linux, so this is a Mac-specific issue. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 55658] New: psapi:psapi_main - test_EnumProcessModules*() fails on macOS
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55658 Bug ID: 55658 Summary: psapi:psapi_main - test_EnumProcessModules*() fails on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - test_EnumProcessModules*() fails on macOS: psapi_main.c:156: Test failed: got 0, error 5 psapi_main.c:158: Test failed: expected non-NULL module psapi_main.c:162: Test failed: got error 5 psapi_main.c:163: Test failed: got PÛ psapi_main.c:166: Test failed: got error 5 psapi_main.c:167: Test failed: got psapi_main.c:170: Test failed: got error 5 psapi_main.c:183: Test failed: got error 5 psapi_main.c:184: Test failed: third DLL in wow64 should be one of wow*.dll () psapi_main.c:239: Test failed: pcs-6432: 1: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 2: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 0: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 3: didn't succeed 5 psapi_main.c:507: Test failed: pcs-6432: expecting 32bit modules psapi_main.c:510: Test marked todo: pcs-6432: expecting 64bit modules psapi_main.c:345: Test failed: pcs-6432: 1: got error 5 psapi_main.c:346: Test failed: pcs-6432: 1: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 1: got error 5 psapi_main.c:349: Test failed: pcs-6432: 1: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 1: got error 5 psapi_main.c:353: Test failed: pcs-6432: 1: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 1: got entry point 0000000000000000 psapi_main.c:345: Test failed: pcs-6432: 0: got error 5 psapi_main.c:346: Test failed: pcs-6432: 0: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 0: got error 5 psapi_main.c:349: Test failed: pcs-6432: 0: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 0: got error 5 psapi_main.c:353: Test failed: pcs-6432: 0: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 0: got entry point 0000000000000000 psapi_main.c:345: Test failed: pcs-6432: 3: got error 5 psapi_main.c:346: Test failed: pcs-6432: 3: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 3: got error 5 psapi_main.c:349: Test failed: pcs-6432: 3: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 3: got error 5 psapi_main.c:353: Test failed: pcs-6432: 3: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 3: got entry point 0000000000000000 psapi_main.c:529: Test succeeded inside todo block: pcs-6432: Wrong count 0 in C:\windows\syswow64 See https://test.winehq.org/data/patterns.html#psapi:psapi_main This set of failures started on 2023-09-14 and only happens on macOS (see Remi's rbernon-macos-* cloud test machines). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 55241] New: The 64-bit winmm:capture & winmm:wave crash on Windows 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55241 Bug ID: 55241 Summary: The 64-bit winmm:capture & winmm:wave crash on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit winmm:capture & winmm:wave crash on Windows 8: capture.c:171: this is the last test seen before the exception 07d0:capture: unhandled exception c0000005 at 00007FFDC66DCF38 wave.c:686: this is the last test seen before the exception 0b14:wave: unhandled exception c0000005 at 00007FFDC66DCF38 See https://test.winehq.org/data/patterns.html#winmm:capture https://test.winehq.org/data/patterns.html#winmm:wave This started with the GitLab CI's switch to Debian 12 (bookworm) for the build system: * The winmm_test.exe binary produced by the TestBot's Debian 11-based build VM produces no failures when run on Windows while GitLab CI's binary for the same Wine version produces this set of failures. * And the TestBot runs the official WineTest builds on its Windows VMs which is why the failures appeared on 2023-07-10 which corresponds to this commit: commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Jul 10 17:18:49 2023 +0200 gitlab: Upgrade the Debian image to bookworm. Now the question is whether the new build environment revealed a preexisting bug in Wine, or if the new build environment itself is broken, or if the bug is elsewhere such as in the MinGW compiler. This is also likely the same issue as bug 55240. -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs October 2023