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.
https://bugs.winehq.org/show_bug.cgi?id=55674
Bug ID: 55674
Summary: 64-bit wineserver/wine-preloader hangs on macOS 14.
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: jactry92(a)gmail.com
This is a regression introduced by a81c53504ae32715e6e91bd020fdebd5bef20d48.
Before this commit, I can run Notepad++ with a WOW64 build on macOS 14. But
now, I can't even start `winecfg` and create a wineprefix.
I don't reproduce this issue with 64-bit Wine on Linux, so this is a
Mac-specific issue.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55670
Bug ID: 55670
Summary: Word 2007 and Wordpad are no longer able to print
multiple copies of a page
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dmitry(a)baikal.ru
CC: piotr(a)codeweavers.com
Distribution: ---
This problem has been noticed with Word 2007 however it's also possible to
reproduce with wordpad ('wine write' is a nice wrapper to run wordpad).
Steps to reproduce:
1. wine write
2. Ctrl+P (File -> Print), it's fine to print empty document
3. Select "Print to file", set "Number of copies" to 2, select Pages 1 - 1 for
clarity
4. Press OK, save "output.prn".
When the bug is not present output.prn contains the comment
%%cupsJobTicket: copies=2
otherwise this comment is missing from the generated Postscript file.
According to my testing last version of Wine that was able to correctly print
multiple copies is wine-7.22, wine-8.0-rc1 is already broken.
It's not really possible to correctly find the offending commit because
breakage has side effects like a failure to create "output.prn". If a missing
output.prn could be considered as 'bad' during bisection then the regression is
caused by
$ git bisect bad
017e9557db73a4b51b5cb2eacbf638288b5e6719 is the first bad commit
commit 017e9557db73a4b51b5cb2eacbf638288b5e6719
Author: Piotr Caban <piotr(a)codeweavers.com>
Date: Fri Dec 2 21:23:50 2022 +0100
localspl: Use print processor in ScheduleJob.
Wine with this commit reverted writes correct "output.prn" with
%%cupsJobTicket: copies=2, however using Wine with that commit leads to a
missing "output.prn".
P.S.
wine-8.0 is not able to print to a file (missing "output.prn")
wine-8.0.2 is able to create "output.prn" however %%cupsJobTicket: copies=2 is
missing
As a result with wine-stable it's impossible to print multiple copies of a
page.
I'd personally consider this bug as major, especially when stable Wine release
is affected, however I'll leave to Piotr to decide.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=55658
Bug ID: 55658
Summary: psapi:psapi_main - test_EnumProcessModules*() fails on
macOS
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - test_EnumProcessModules*() fails on macOS:
psapi_main.c:156: Test failed: got 0, error 5
psapi_main.c:158: Test failed: expected non-NULL module
psapi_main.c:162: Test failed: got error 5
psapi_main.c:163: Test failed: got PÛ
psapi_main.c:166: Test failed: got error 5
psapi_main.c:167: Test failed: got
psapi_main.c:170: Test failed: got error 5
psapi_main.c:183: Test failed: got error 5
psapi_main.c:184: Test failed: third DLL in wow64 should be one of wow*.dll ()
psapi_main.c:239: Test failed: pcs-6432: 1: didn't succeed 5
psapi_main.c:239: Test failed: pcs-6432: 2: didn't succeed 5
psapi_main.c:239: Test failed: pcs-6432: 0: didn't succeed 5
psapi_main.c:239: Test failed: pcs-6432: 3: didn't succeed 5
psapi_main.c:507: Test failed: pcs-6432: expecting 32bit modules
psapi_main.c:510: Test marked todo: pcs-6432: expecting 64bit modules
psapi_main.c:345: Test failed: pcs-6432: 1: got error 5
psapi_main.c:346: Test failed: pcs-6432: 1: expecting msinfo32.exe but got
psapi_main.c:348: Test failed: pcs-6432: 1: got error 5
psapi_main.c:349: Test failed: pcs-6432: 1: expecting
C:\windows\syswow64\msinfo32.exe but got
psapi_main.c:352: Test failed: pcs-6432: 1: got error 5
psapi_main.c:353: Test failed: pcs-6432: 1: expected 00000000DEADBEEF, got
0000000178010008
psapi_main.c:355: Test failed: pcs-6432: 1: got entry point 0000000000000000
psapi_main.c:345: Test failed: pcs-6432: 0: got error 5
psapi_main.c:346: Test failed: pcs-6432: 0: expecting msinfo32.exe but got
psapi_main.c:348: Test failed: pcs-6432: 0: got error 5
psapi_main.c:349: Test failed: pcs-6432: 0: expecting
C:\windows\syswow64\msinfo32.exe but got
psapi_main.c:352: Test failed: pcs-6432: 0: got error 5
psapi_main.c:353: Test failed: pcs-6432: 0: expected 00000000DEADBEEF, got
0000000178010008
psapi_main.c:355: Test failed: pcs-6432: 0: got entry point 0000000000000000
psapi_main.c:345: Test failed: pcs-6432: 3: got error 5
psapi_main.c:346: Test failed: pcs-6432: 3: expecting msinfo32.exe but got
psapi_main.c:348: Test failed: pcs-6432: 3: got error 5
psapi_main.c:349: Test failed: pcs-6432: 3: expecting
C:\windows\syswow64\msinfo32.exe but got
psapi_main.c:352: Test failed: pcs-6432: 3: got error 5
psapi_main.c:353: Test failed: pcs-6432: 3: expected 00000000DEADBEEF, got
0000000178010008
psapi_main.c:355: Test failed: pcs-6432: 3: got entry point 0000000000000000
psapi_main.c:529: Test succeeded inside todo block: pcs-6432: Wrong count 0 in
C:\windows\syswow64
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
This set of failures started on 2023-09-14 and only happens on macOS (see
Remi's rbernon-macos-* cloud test machines).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
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:capturehttps://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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=55648
Bug ID: 55648
Summary: ntdll:wow64 - test_peb_teb() crashes on macOS
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:wow64 - test_peb_teb() crashes on macOS:
wow64.c:712: Test failed: RtlWow64GetSharedInfoProcess failed c0000022
wow64.c:716: Test failed: wrong page size cccccccc
wow64.c:718: Test failed: wrong flags cccccccc
wow64.c:720: Test failed: wrong machine cccc / 8664
wow64.c:722: Test failed: wrong machine cccc
wow64.c:748: Test failed: DuplicateHandle failed 6
wow64.c:751: Test failed: NtMapViewOfSection failed c0000008
wow64.c:752: Test failed: unexpected size 0
wow64.c:764: Test failed: got 0 handle
wow64.c:765: Test failed: got NULL data
wow64.c:772: Test failed: NtMapViewOfSection failed c0000008
wow64.c:774: Test failed: invalid handle
Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit
code (0x000001400cc20e).
See https://test.winehq.org/data/patterns.html#ntdll:wow64
The crashes started happening on 2023-09-14 (a day with no ntdll commit) and
only happen on macOS (see Remi's rbernon-macos-* cloud test machines).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55631
Bug ID: 55631
Summary: ntdll:file - test_file_rename_information fails on
Windows 10 1607 and older
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:file - test_file_rename_information fails on Windows 10 1607 and older:
file.c:1550: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef
file.c:1552: Test failed: res expected STATUS_SUCCESS, got c0000003
file.c:1555: Test failed: file should not exist
file.c:1558: Test failed: file should exist
file.c:1565: Test failed: FileName expected
L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F4E.tmp", got
L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F4D.tmp"
file.c:1594: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got
c0000003
file.c:1624: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef
file.c:1626: Test failed: res expected STATUS_SUCCESS, got c0000003
file.c:1629: Test failed: file should not exist
file.c:1661: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got
c0000003
file.c:1696: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003
file.c:1731: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef
file.c:1733: Test failed: res expected STATUS_SUCCESS, got c0000003
file.c:1736: Test failed: file should not exist
file.c:1739: Test failed: file should exist
file.c:1746: Test failed: FileName expected
L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F68.tmp", got
L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F57.tmp"
file.c:1783: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003
file.c:1827: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got
c0000003
file.c:1865: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got
c0000003
file.c:1899: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef
file.c:1901: Test failed: res expected STATUS_SUCCESS, got c0000003
file.c:1904: Test failed: file should not exist
file.c:1940: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003
file.c:1979: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got
c0000003
file.c:2017: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003
file.c:2058: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003
file.c:2093: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got
c0000003
file.c:2127: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003
file.c:2161: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef
file.c:2163: Test failed: res expected STATUS_SUCCESS, got c0000003
file.c:2166: Test failed: file should not exist
file.c:2169: Test failed: file should exist
file.c:2176: Test failed: FileName expected
L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F8D.tmp", got
L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F8C.tmp"
file.c:2203: Test failed: got io status 0xdeadbeef
file.c:2205: Test failed: got status c0000003
See https://test.winehq.org/data/patterns.html#ntdll:file
Where 0xc0000003 == STATUS_INVALID_INFO_CLASS
These failures are systematic and started happening on 2023-09-19. A bisect
shows that they started with the commit below:
commit 67479f8c2fc03c2043b8414bc063e671e36fdbda
Author: Joel Holdsworth <joel(a)airwebreathe.org.uk>
Date: Fri Sep 15 17:49:52 2023 +0100
ntdll/tests: Test both FileRenameInformation and FileRenameInformationEx in
test_file_rename_information.
Signed-off-by: Joel Holdsworth <joel(a)airwebreathe.org.uk>
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.