wine-bugs August 2023

wine-bugs@winehq.org

1 participants
2879 discussions

[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

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