wine-bugs August 2023

wine-bugs@winehq.org

1 participants
2948 discussions

[Bug 55414] New: Ultimate Spider-Man: Widescreen Fix shifts HUD too much to the right
by WineHQ Bugzilla 15 Oct '23

15 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55414 Bug ID: 55414 Summary: Ultimate Spider-Man: Widescreen Fix shifts HUD too much to the right 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: tinozzo123(a)tutanota.com Distribution: --- Created attachment 74975 --> https://bugs.winehq.org/attachment.cgi?id=74975 Logs taken from fresh prefix, with `WINEDEBUG=warn+all` The game Ultimate Spider-Man works well in Wine (I played it from start to finish). I also played with the Widescreen Fix, which works except for one thing. The mod offers the option (enabled by default) to fix the HUD (without it, the HUD would be stretched). That is the problematic part under Wine, because with it the HUD is shifted too much to the right, rendering the mod unusable. It works no problem with it disabled (which is how I played). So, to reproduce: - Install Ultimate Spider-Man - Install the mod: https://github.com/ThirteenAG/WidescreenFixesPack/releases/tag/usm - Set `WINEDLLOVERRIDES` for `dsound` - Make sure that in the mod settings, `FixHUD` is set to `1` (it's the default) - Launch the game, you should see the problem right in the main menu. Source code of the mod: https://github.com/ThirteenAG/WidescreenFixesPack/tree/master/source/Ultima… Images of the issue (made an issue on GitHub in case the issue wasn't on from Wine's side): https://github.com/ThirteenAG/WidescreenFixesPack/issues/1309 -- 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 55287] New: msvcrt:file - The 32-bit test_pipes() fails in the new WoW mode
by WineHQ Bugzilla 15 Oct '23

15 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55287 Bug ID: 55287 Summary: msvcrt:file - The 32-bit test_pipes() fails in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- msvcrt:file - The 32-bit test_pipes() fails in the new WoW mode: file.c:2343: Test failed: i 0, expected to write 'Hello world' wrote -1 file.c:2343: Test failed: i 1, expected to write 'Hello world' wrote -1 file.c:2343: Test failed: i 2, expected to write 'Hello world' wrote -1 file.c:2350: Test failed: unable to close 4: 9 01cc:file: 5 tests executed (0 marked as todo, 0 as flaky, 4 failures), 0 skipped. file.c:2383: Test failed: i 0, got 0 file.c:2386: Test failed: expected to read 'Hello world', got '' file.c:2383: Test failed: i 1, got 0 file.c:2386: Test failed: expected to read 'Hello world', got '' file.c:2383: Test failed: i 2, got 0 file.c:2386: Test failed: expected to read 'Hello world', got '' file.c:2343: Test failed: i 0, expected to write 'Hello world' wrote -1 file.c:2343: Test failed: i 1, expected to write 'Hello world' wrote -1 file.c:2343: Test failed: i 2, expected to write 'Hello world' wrote -1 file.c:2350: Test failed: unable to close 4: 9 076c:file: 5 tests executed (0 marked as todo, 0 as flaky, 4 failures), 0 skipped. file.c:2419: Test failed: fread() returned 0: ferror=0 file.c:2422: Test failed: got '' expected 'Hello worldHello worldHello world' See https://test.winehq.org/data/patterns.html#msvcrt: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 4

[Bug 55402] New: CMD '!var!' not working in 'if' statement
by WineHQ Bugzilla 15 Oct '23

15 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55402 Bug ID: 55402 Summary: CMD '!var!' not working in 'if' statement Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: mr.dmitry.sokolov(a)gmail.com Distribution: --- The command not working set var=qwe if "!var!"=="" ... ACTUAL The script (attached) produces wrong output EXPECTED See the output in .exp file (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 7

[Bug 46107] New: Altium Designer 18 page faults when launched
by wine-bugs＠winehq.org 15 Oct '23

15 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=46107 Bug ID: 46107 Summary: Altium Designer 18 page faults when launched Product: Wine Version: 3.19 Hardware: x86 URL: https://s3.amazonaws.com/altium-release-manager/Altium _Designer_18/OfflineSetup_Altium_Designer_Public_18_1_ 9.zip 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 62738 --> https://bugs.winehq.org/attachment.cgi?id=62738 Backtrace of Altium Designer 18.1.9 on wine-staging 3.19 on xubuntu 16.04 x86-64 Altium Designer 18 is a major rewrite of the EDA/PCB CAD suite and is 64-bit with some legacy 32-bit components (previous versions were 32-bit only). It appears to still be a mix of NET Framework and Delphi components. It has both online and offline installers (URL link is to offline installer, 2.1GB). It requires a registration code to use the app but this is prompted after launch. The offline installer works without problems but includes NET Framework 2.6.1 which doesn't install properly (as per NET Framework Setup Verification Tool) so winetricks is needed: winetricks -q corefonts dotnet461 Upon execution the app (X2.EXE) page faults after the splash screen. Occurs with both dev and staging. Wine packages: wine-devel | 3.19.0~xenial | https://dl.winehq.org/wine-builds/ubuntu xenial/main amd64 Packages wine-staging | 3.19.0~xenial | https://dl.winehq.org/wine-builds/ubuntu xenial/main amd64 Packages winetricks list: Using winetricks 20180815-next - sha256sum: cff80fa6dbd02b43972d13fc82e4af9bddd968623c0b18620679816968a07f80 with wine-3.19 (Staging) and WINEARCH=win64 andale arial comicsans courier georgia impact times trebuchet verdana webdings corefonts w_workaround_wine_bug-34803 remove_mono w_workaround_wine_bug-34803 remove_mono w_workaround_wine_bug-34803 remove_mono w_workaround_wine_bug-42701 w_workaround_wine_bug-34803 remove_mono winxp dotnet40 dotnet45 w_workaround_wine_bug-38959 dotnet46 dotnet461 Third-party components (identified by file name and hex dumps): TeighaX SQLite DirectX 9 zlib Professional Software Development FastMM FFmpeg LAME 7-Zip LZ4 DevExpress Chromium Embedded Framework -- 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 61

[Bug 39876] New: Humanity Asset crashes on start with built-in d3dx
by wine-bugs＠winehq.org 15 Oct '23

15 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=39876 Bug ID: 39876 Summary: Humanity Asset crashes on start with built-in d3dx Product: Wine Version: 1.9.0 Hardware: x86 URL: http://www.moddb.com/games/humanity-asset/downloads/hu manity-asset-demo# OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 53243 --> https://bugs.winehq.org/attachment.cgi?id=53243 +d3dx log The demo comes bundled with native d3dx9_38.dll, if you set it to 'built-in' in winecfg, then the game crashes while loading to the main menu. HumanityAssetDemo.2.rar sha1: 619538846bc8c8a6d8d319378708582ef41be1c4 -- 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 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 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 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

[Bug 54744] New: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54744 Bug ID: 54744 Summary: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows: taskbarlist.c:61: Test failed: Got hr 0x80004001. taskbarlist.c:66: Test failed: Got hr 0x80004001. See https://test.winehq.org/data/patterns.html#explorerframe:taskbarlist Where 0x80004001 == E_NOTIMPL On average this happens about once every other month on recent Windows 10 versions: * 2022-08-31 on w1064-tsign-64 (21h2) * 2022-11-14 on w1064-tsign-32 (21h2) * 2023-01-10 on fgtb-w10pro64-rx550-64 (22h2) * 2023-02-06 on w10pro64-rx550-64 (22h2) * 2023-03-27 on w10pro64-ar-64 (21h1) -- 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 54069] New: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54069 Bug ID: 54069 Summary: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+ 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_texture_wrong_caps() sometimes fails on Windows 8+. ddraw7.c:18954: Test failed: Got unexpected color 0x00000040. and ddraw7.c:18972: Test failed: Got unexpected color 0x00ff00ff. See https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Notes: * There is no evidence of this happening on Windows 11. * This seems to only happen with Microsoft's "Microsoft Basic Display Adapter" driver: the "-1qxl" and "-2qxl" (dual-monitor) configuration use the "Red Hat QXL controller" driver and are are not affected. Neither are the AMD / NVIDIA PCI passthrough configurations. * The 0x00000040 result mostly happens on Windows 8 to Windows 10 1607 but it also happened a couple of times on Windows 10 21H2. Meanwhile the 0x00ff00ff result seems to only happen on Windows 10 2004+. * ddraw:ddraw1, ddraw:ddraw2 and ddraw:ddraw4 have a similar test function but don't have this failure. -- 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 43017] New: Unreal Tournament 2004/UT2004.exe crashes due to " intel_do_flush_locked failed: Cannot allocate memory"
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43017 Bug ID: 43017 Summary: Unreal Tournament 2004/UT2004.exe crashes due to "intel_do_flush_locked failed: Cannot allocate memory" Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Unreal Tournament 2004/UT2004.exe crashes due to `intel_do_flush_locked failed: Cannot allocate memory` the debug output of PlayOnLinux reads ``` [05/12/17 23:55:35] - Running wine-2.7 UT2004.exe (Working directory : /home/richter/.PlayOnLinux/wineprefix/UnrealT2004/drive_c/Program Files/Unreal Tournament 2004/System) err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142 fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32e540,0x32e53c): stub fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:create_server class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject no class object {96749377-3391-11d2-9ee3-00c04f797396} could be created for context 0x7 fixme:win:EnumDisplayDevicesW ((null),0,0x32bc98,0x00000000), stub! fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:imm:ImmReleaseContext (0x1007c, 0x2165e0): stub fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x6404c88, 0x32ccc4 err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1042267284)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1082643741)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129305379)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1017464658)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106373278)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1061644189)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103102115)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102202262)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127878391)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1133393126)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064431753)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056334452)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103590910)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1128011843)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1012511863)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129177136)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064579615)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107545964)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127492263)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1131588260)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1009667614)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064940315)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102388947)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107645235)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127352012)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106599611)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065065837)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056114040)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1104285584)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127422744)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1029644321)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1126051816)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065075311)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". intel_do_flush_locked failed: Cannot allocate memory ``` -- 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 55273] New: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55273 Bug ID: 55273 Summary: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709 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:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709: wow64.c:783: Test failed: 0:0: wrong offset 4 wow64.c:783: Test failed: 0:1: wrong offset 6 wow64.c:783: Test failed: 0:2: wrong offset 4 wow64.c:783: Test failed: 0:3: wrong offset 6 wow64.c:783: Test failed: 0:4: wrong offset 4 wow64.c:783: Test failed: 0:5: wrong offset 6 wow64.c:783: Test failed: 0:6: wrong offset 4 wow64.c:783: Test failed: 0:7: wrong offset 6 wow64.c:783: Test failed: 1:0: wrong offset 16 wow64.c:783: Test failed: 1:1: wrong offset 14 wow64.c:783: Test failed: 1:2: wrong offset 12 wow64.c:783: Test failed: 1:3: wrong offset 10 wow64.c:783: Test failed: 1:4: wrong offset 8 wow64.c:783: Test failed: 1:5: wrong offset 6 wow64.c:783: Test failed: 1:6: wrong offset 4 wow64.c:783: Test failed: 1:7: wrong offset 18 wow64.c:783: Test failed: 2:0: wrong offset 8 wow64.c:783: Test failed: 2:1: wrong offset 6 wow64.c:783: Test failed: 2:2: wrong offset 4 wow64.c:783: Test failed: 2:3: wrong offset 10 wow64.c:783: Test failed: 2:4: wrong offset 8 wow64.c:783: Test failed: 2:5: wrong offset 6 wow64.c:783: Test failed: 2:6: wrong offset 4 wow64.c:783: Test failed: 2:7: wrong offset 10 wow64.c:783: Test failed: 3:0: wrong offset 16 wow64.c:783: Test failed: 3:1: wrong offset 14 wow64.c:783: Test failed: 3:2: wrong offset 12 wow64.c:783: Test failed: 3:3: wrong offset 10 wow64.c:783: Test failed: 3:4: wrong offset 8 wow64.c:783: Test failed: 3:5: wrong offset 6 wow64.c:783: Test failed: 3:6: wrong offset 4 wow64.c:783: Test failed: 3:7: wrong offset 18 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The failures started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 so in this case it is just a coincidence. See also bug 55272 for ntdll:exception crashes that started at the same time on the same set of 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 4

[Bug 55211] New: Print file not truncated when printing to file in FrameMaker 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55211 Bug ID: 55211 Summary: Print file not truncated when printing to file in FrameMaker 8 Product: Wine Version: 8.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- A existing print file ist not truncated when printing to the same file again. So when printing a smaller document to the print file which was generated for a larger file, the resultung file contains garbage at its end. This happens in Framemaker 8 and may happen in other apps too. To reproduce - Install Framemaker from the given URL - Print the attached Document Large.fm to a file (select print to file in the printer dialog). Check the size of the generated file. - Print the attached Document Small.fm to the same file generated in the previous step. Check again the size of the file - its the same. Depending on the used Postscript interpreter reading the file fails because of the garbage at the files end. This is simple to see when using different documents as descibed above. When printing existing documents again after (even small) changes the resulting print file may be garbage without notice. -- 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 43185] New: "Battle Bugs" game in unresponsive once game starts
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43185 Bug ID: 43185 Summary: "Battle Bugs" game in unresponsive once game starts Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matt(a)nightrealms.com Distribution: --- Created attachment 58457 --> https://bugs.winehq.org/attachment.cgi?id=58457 Wine output from before starting the game When playing the free game "Battle Bugs" (https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game start screen loads just fine, and pressing an indicated key starts the game just fine, but once the game starts nothing is moving and the game doesn't respond to any keys. Got the same results with both versions of the executable, and both WINEARCH unspecified or set to win32 -- 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 55236] New: scrrun:dictionary - test_hash_value() gets bad hashes on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55236 Bug ID: 55236 Summary: scrrun:dictionary - test_hash_value() gets bad hashes on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com scrrun:dictionary - test_hash_value() gets bad hashes on Windows: dictionary.c:676: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:686: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:695: Test failed: got hash 0x2db, expected 0x2da dictionary.c:721: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:732: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:742: Test failed: got hash 0x2db, expected 0x2da See https://test.winehq.org/data/patterns.html#scrrun:dictionary Note that the hash values change with every run causing false positives. -- 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 54791] New: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54791 Bug ID: 54791 Summary: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7. This can either be a single event but it can also happen multiple times for multiple events: nstc.c:2265: Test failed: Got event 4, count 1 or nstc.c:1906: Test failed: Got event 7, count 0 nstc.c:1908: Test failed: Got event 4, count 0 nstc.c:1912: Test failed: Got event 4, count 1 nstc.c:1912: Test failed: Got event 7, count 1 nstc.c:1912: Test failed: Got event 12, count 8 See https://test.winehq.org/data/patterns.html#explorerframe:nstc This first happened on 2022-12-07 and has been happening roughly once every three week since. So it's probably caused by a commit in the fall of 2022. -- 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 54441] New: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54441 Bug ID: 54441 Summary: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10: speech.c:1775: Test failed: recog_state was 0. See https://test.winehq.org/data/patterns.html#windows.media.speech:speech This failure started on 2023-01-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.

1 9

[Bug 54156] New: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54156 Bug ID: 54156 Summary: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:edit - test_paste() sometimes gets an empty string on Windows edit.c:3238: Test failed: got 0 See https://test.winehq.org/data/patterns.html#comctl32:edit This happens on Windows 10 1809 to 21H2 a bit less than 3 times per month. Where 0 is the length of the string in the field we pasted to. So that field is empty instead of having received the string we pasted. We can also get this failure in user32:edit (2022-11-15 w10pro64v1809): edit.c:3211: Test failed: got 0 See https://test.winehq.org/data/patterns.html#user32:edit But the case above is for the single-line to single-line case and there is also the same issue happening in the multi-line to multi-line case (2022-10-25 w11pro64-amd): edit.c:3240: Test failed: got 0 So it's a pretty general, if rare (only 4 known instances in 6 months), problem. Note that while one could expect this to be caused by yet another OpenClipboard() failure, like in bug 53276, there is no failure message indicating this to be the case. -- 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 53276] New: user32:edit - test_paste() sometimes fails to access the clipboard on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=53276 Bug ID: 53276 Summary: user32:edit - test_paste() sometimes fails to access the clipboard on Windows 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:edit - test_paste() sometimes fails to access the clipboard on Windows: edit.c:3222: Test failed: expected 1, got 0 le=5 edit.c:3224: Test failed: expected 1, got 0 edit.c:3226: Test failed: expected 00000000008500A8, got 0000000000000000 edit.c:3228: Test failed: expected 1, got 0 edit.c:3234: Test failed: got 21 edit.c:3240: Test failed: got 21 https://test.winehq.org/data/patterns.html#user32:edit Where 5 is ERROR_ACCESS_DENIED and indicates that the clipboard has already been opened in another thread, process, etc. This happens a lot on machines with an AMD GPU due to known interference from the Radeon driver (see bug 47888). But it also happens sometimes on machines with an Nvidia GPU (cw-gtx560) and even on pure QEmu VMs such as w1064-1qxl (or fgtb-w10pro64). So there is either some other source of interference, maybe from some Windows component, or an issue (a race condition?) in the test itself. It would be nice to identify the source of interference, if any, to see if it can be neutralized. But maybe the only solution is to work around the issue as in user32:clipboard (see commit 316eec8f6658). -- 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 55272] New: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55272 Bug ID: 55272 Summary: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709 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 The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709: exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 ntdll:exception:0dd8 done (-1073741819) in 0s 6581B See https://test.winehq.org/data/patterns.html#ntdll:exception Where -1073741819 == 0xC0000005 == STATUS_ACCESS_VIOLATION The crashes started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 in this case it is just a coincidence. Note that before that ntdll:exception was exiting silently on Windows 8 & 10 <= 1809, see bug 55111. These two issues may be one and the same, just producing different results due to changes in the binary layout. -- 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 55108] New: xaudio2_8:xaudio2 fails on Windows 10+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55108 Bug ID: 55108 Summary: xaudio2_8:xaudio2 fails on Windows 10+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com xaudio2_8:xaudio2 fails on Windows 10+: xaudio2.c:1218: Test failed: Got hr 0x80004002. See https://test.winehq.org/data/patterns.html#xaudio2_8:xaudio2 Note that this is the same failure as what happened on Windows 8 in the late stages described in bug 55016. A bisect shows that this failure started with the commit below: commit e8b0e7c1fcf090ba80c543f68b0bdae185316327 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Fri Jun 16 15:13:14 2023 -0500 xaudio2/tests: Fix the IID_IXAudio28 declaration. This was accidentally copied from the 2.9 version instead in 14c44d0b0. -- 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 54699] New: Motorola Ready For Assistant does not start, RoOriginateLanguageException in Windows.Networking
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54699 Bug ID: 54699 Summary: Motorola Ready For Assistant does not start, RoOriginateLanguageException in Windows.Networking Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lischak(a)gmail.com Distribution: --- Created attachment 74209 --> https://bugs.winehq.org/attachment.cgi?id=74209 install+run of v04.0.0.010.000 on Wine 8.4 Motorola Ready For Assistant is a software for interfacing with Motorola smartphones from desktop, allowing either phone screen mirror or a full-sized Android-powered desktop similar to Samsung DeX. The installer appears to finish successfully, but the application will not start. This is a continuation of Bug 54495 in which two previous issues were fixed (thanks!). The installation file is freely downloadable: https://web.archive.org/web/20230214220515/https://download.lenovo.com/leno… cd ~/Downloads WINEPREFIX=~/.wine_readyfor wine ReadyFor_setup_04.0.0.010.000.exe cd ~/.wine_readyfor/drive_c/Program\ Files/Lenovo/Ready\ For\ Assistant WINEPREFIX=~/.wine_readyfor wine ReadyFor.exe Attaching log from installation and from a follow-up run. Env: Fedora 37, using the appropriate official WineHQ repo. Note: The software is apparently only available via MS Store nowadays, but the Store install just downloads a normal Win32 .exe from Motorola/Lenovo's servers in the background. -- 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 52641] New: dsdmo has missing implementation causing game crash on loaded
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=52641 Bug ID: 52641 Summary: dsdmo has missing implementation causing game crash on loaded Product: Wine 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 Distribution: --- log has shown a missing implementation on dsdmo dll this cause game crash when loading Affect game: Feeding Frenzy 2 Log: 0290:warn:dsdmo:effect_inner_QueryInterface {6d6cbb60-a223-44aa-842f-a2f06750be6d} not implemented; returning E_NOINTERFACE. -- 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 41645] New: recursive invokation of __clone+0x6d() in libc.so.6 ( 0x00000000) in start_thread+0xe4() in libpthread.so.0 (0x0608f428)
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=41645 Bug ID: 41645 Summary: recursive invokation of __clone+0x6d() in libc.so.6 (0x00000000) in start_thread+0xe4() in libpthread.so.0 (0x0608f428) Product: Wine Version: 1.9.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Created attachment 56020 --> https://bugs.winehq.org/attachment.cgi?id=56020 Backtrace created by wine crash handler There seems to be a recursive invokation inside `__clone+0x6d()` in `start_thread+0xe4() in libpthread.so.0 (0x0608f428)`, see attached backtrace. -- 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 19

[Bug 55245] New: ntdll:om - The 32-bit test_all_kernel_objects() gets an access violation on the w8 VM
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55245 Bug ID: 55245 Summary: ntdll:om - The 32-bit test_all_kernel_objects() gets an access violation on the w8 VM 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:om - The 32-bit test_all_kernel_objects() gets an access violation on Windows 8: om.c:553: Test failed: 751: NtCreateSymbolicLinkObject failed c0000005 om.c:565: Test failed: 751: NtCreateSymbolicLinkObject failed c0000005 om.c:553: Test failed: 752: NtCreateSymbolicLinkObject failed c0000005 om.c:565: Test failed: 752: NtCreateSymbolicLinkObject failed c0000005 See https://test.winehq.org/data/patterns.html#ntdll:om Where c0000005 == STATUS_ACCESS_VIOLATION This started on 2023-07-10 which corresponds to the GitLab CI switch to Debian 12 for builds which means it is caused by the commit below: 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. However unlike other failures related to that switch, this one only happens on the 32-bit Windows 8 VM, aka w8. So running the same 32-bit binary on the 64-bit Windows 8 VM, aka w864, produces no failure. -- 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 August 2023