wine-bugs August 2023

wine-bugs@winehq.org

1 participants
2931 discussions

[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

[Bug 55379] New: kernel32:loader sometimes gets a bad thread count on Windows 10 in phase 0/1
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55379 Bug ID: 55379 Summary: kernel32:loader sometimes gets a bad thread count on Windows 10 in phase 0/1 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:loader sometimes gets a bad thread count on Windows 10 in phase 0/1. So far there are only two instances, both in the 64-bit tests: * 2023-07-31 w1064-adm 64-bit tests loader.c:2875: phase 1: writing 00007FF633B64570 at 0x202 loader.c:2514: dll: 0000000010000000, DLL_PROCESS_ATTACH, 0000000000000000 loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000 loader.c:2399: 1eb0: mutex_thread_proc: starting loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000 loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000 loader.c:2954: Test failed: attached thread count should be 2 * 2023-06-07 fgtb-w10pro64 64-bit tests loader.c:2875: phase 0: writing 000000000048FED0 at 0x202 loader.c:2514: dll: 0000000010000000, DLL_PROCESS_ATTACH, 0000000000000000 loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000 loader.c:2399: 1414: mutex_thread_proc: starting loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000 loader.c:2784: dll: 0000000010000000, DLL_THREAD_ATTACH, 0000000000000000 loader.c:2954: Test failed: attached thread count should be 2 See https://test.winehq.org/data/patterns.html#kernel32:loader -- 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 55378] New: Can't get resolutions list for scanner
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55378 Bug ID: 55378 Summary: Can't get resolutions list for scanner Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ilya.docin(a)contentai.ru Distribution: --- Created attachment 74954 --> https://bugs.winehq.org/attachment.cgi?id=74954 Twister Analysis of HP LaserJet MFP M426fdn OS: Ubuntu 20.04.1 Component: sane.ds I use Twister utility to analyze some scanners on Wine. Many scanners return resolutions in a form of array. E.g., HP LaserJet MFP M426fdn. Twister indicates that getting resolutions for such scanners is unsupported. Screenshot 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 0

[Bug 55375] New: Can't set color mode for scanner
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55375 Bug ID: 55375 Summary: Can't set color mode for scanner Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: ilya.docin(a)contentai.ru CC: dimesio(a)earthlink.net Distribution: --- Created attachment 74952 --> https://bugs.winehq.org/attachment.cgi?id=74952 Twister analyze for HP LaserJet Pro M428-M429f OS: Ubuntu 20.04.1 Wine version: wine-8.0.2 Component: sane.ds I use Twister utility to analyze some scanners on Wine. When it tries to set color mode to any scanner, both report and Wine log says, that value is not set. I attached screenshot with report. -- 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 55376] New: [USER32/NTUSER] Keyboard app accents doesn't change the keys correctly.
by WineHQ Bugzilla 02 Aug '23

02 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55376 Bug ID: 55376 Summary: [USER32/NTUSER] Keyboard app accents doesn't change the keys correctly. Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: julenuri(a)hotmail.com Distribution: --- Wine version: 8.13 Environment: Debian 11 Software tested: Accents 1.0 from this web: https://www.dcmembers.com/skrommel/download/accents/# Steps to reproduce: The functionality is simple. After 3 or more keyboard inputs in the letters A, E, I, O, U or Y, you will have accent mark. 1. start the software accents 2. start wine notepad or whatever notepad you want. 3. input 3 "a" There is a failure somewhere into key hooking process: WH_KEYBOARD_LL, WM_USER+(number), DWL_MSGRESULT, PM_NOREMOVE, VK_LSHIFT [have a bad value (-32768)], GetAsyncKeyState, CharLowerA, SetWindowsHookExA, CallNextHookEx, VkKeyScanExA, MapVirtualKeyA. I'm not sure where because I'm not developer and I have zero time to check where is exactly the failure. Expected behavior: It should write å. Issue: But in fact, it only deletes the input. Video of the issue: https://youtu.be/B56TUdg3zQ8 Video of example of no issue: https://www.dcmembers.com/skrommel/wp-content/uploads/sites/2/2017/10/Accen… We detected the same behaviour in ReactOS too long time ago, but I guess no-one tested in Wine before: https://jira.reactos.org/browse/CORE-5627 -- 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

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