https://bugs.winehq.org/show_bug.cgi?id=54348
Bug ID: 54348
Summary: rpcrt4:server - run_client() sometimes times out
waiting for the child process on Debian
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: rpc
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: fgouget(a)codeweavers.com, huw(a)codeweavers.com,
z.figura12(a)gmail.com
Distribution: ---
rpcrt4:server - run_client() sometimes times out waiting for the child process
on Debian:
rpcrt4:server start dlls/rpcrt4/tests/server.c
server.c:2172: Using RpcServerRegisterIfEx
server.c:1228: Test failed: Timed out waiting for the child process
server.c:1015: Test marked todo: object_uuid is (null)
server.c:1016: Test marked todo: endpoint is (null)
server.c:1017: Test marked todo: network_options is (null)
0a04:server: 154 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0
skipped.
08a8:server: 11 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0
skipped.
server.c:1015: Test marked todo: object_uuid is (null)
server.c:1016: Test marked todo: endpoint is (null)
server.c:1017: Test marked todo: network_options is (null)
0858:server: 148 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0
skipped.
server.c:1015: Test marked todo: object_uuid is (null)
server.c:1016: Test marked todo: endpoint is (null)
server.c:1017: Test marked todo: network_options is (null)
0564:server: 156 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0
skipped.
rpcrt4:server:0224 done (258) in 120s 1063B
--
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=50780
Bug ID: 50780
Summary: ALT+TAB freezes game Stronghold (Crusader)
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: geist1(a)sms.at
Distribution: ---
Game "Stronghold Crusader HD" as well "Stronghold Crusader" , "Stronghold I" -
Stronghold Extreme will freeze after ALT+TAB to Desktop and back switching with
ALT+TAB to the game.
If you tab out on the title screen of Stronghold and tab back in, the screen is
correctly restored but game freezes.
If you TAB out and back in during the game (not on the main screen) , the game
window is not restored correctly, only a black window is visible with no sound.
It worked correctly until 4.9.
All Version starting from 4.10 up current one (6.3) will fail.
Game run in fulscreen at 1280X720.
Desktop resolution is 1920X1080.
--
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=54412
Bug ID: 54412
Summary: Setup failed when run ExamBible.exe with wine
Product: Wine
Version: 7.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: luoriyuhui21(a)163.com
Distribution: ---
Created attachment 73971
--> https://bugs.winehq.org/attachment.cgi?id=73971
the error log file
when using wine to load ExamBible.exe, this program cannot setup. The error
is as ,
0020:0024:err:module:import_dll Library oleaut32
oleaut32.dll (which is needed by
L"Z:\\home\\keming\\JC_EJJZS_GGKM2.3\\ExamBible.exe") not found
0020:0024:err:module:import_dll loadpath (null) (which is needed by
L"Z:\\home\\keming\\JC_EJJZS_GGKM2.3\\ExamBible.exe") not found
0020:0024:err:module:LdrInitializeThunk Importing dlls for
L"Z:\\home\\keming\\JC_EJJZS_GGKM2.3\\ExamBible.exe" failed, status c0000135
keming@keming-VirtualBox:~/JC_EJJZS_GGKM2.3$
0038:00fc:err:module:LdrInitializeThunk end.
--
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=54411
Bug ID: 54411
Summary: ntoskrnl.exe:ntoskrnl - test_pnp_devices() sometimes
gets an unexpected success in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntoskrnl.exe:ntoskrnl - test_pnp_devices() sometimes gets an unexpected success
in Wine:
ntoskrnl.c:1715: Test succeeded inside todo block: got error 997
See https://test.winehq.org/data/patterns.html#ntoskrnl.exe:ntoskrnl
Where 997 == ERROR_IO_PENDING
The test happens about once per month but has been known to impact merge
requests (e.g. MR2039).
This looks like a race condition. Mark the test as flaky in Wine?
--
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=54283
Bug ID: 54283
Summary: dinput:force_feedback - test_windows_gaming_input()
sometimes crashes on Windows and Wine
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_windows_gaming_input() sometimes crashes on
Windows :
force_feedback.c:6324: Test failed: TryResetAsync returned 0x86854001
force_feedback.c:6324: this is the last test seen before the exception
06a0:force_feedback: unhandled exception c0000005 at 000000000041B540
And Wine:
force_feedback.c:6479: Test marked todo: Stop returned 0x8000ffff
force_feedback.c:4864: iface 006C886C, async 019D8AF8, status 1
force_feedback.c:4779: iface 006C886C, async 019D8AF8, status 1
force_feedback.c:4864: iface 006C886C, async 019D8AF8, status 1
force_feedback.c:4779: iface 006C886C, async 019C09E0, status 1
force_feedback.c:4864: iface 006C886C, async 019C09E0, status 1
force_feedback.c:4779: iface 006C886C, async 019C09E0, status 1
Unhandled exception: page fault on read access to 0x00000008 in 32-bit code
(0x6fc81461).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:6fc81461 ESP:0389fdc0 EBP:0389fe08 EFLAGS:00010206( R- -- I - -P- )
EAX:00000000 EBX:0389fde0 ECX:006c886c EDX:00000000
ESI:019d8af8 EDI:019d9b28
Stack dump:
0x0389fdc0: 006c886c 019d8af8 00000001 00000001
0x0389fdd0: 00184f80 00000001 019d9b48 006c886c
0x0389fde0: 00000013 00000000 00000000 7bc5c97f
0x0389fdf0: 00184fc4 00000000 0389fe20 00185024
0x0389fe00: 00184f80 019d9b28 0389feb8 7bc602c6
0x0389fe10: 00000000 00000000 0389fe40 7bc602c6
Backtrace:
=>0 0x6fc81461
__x_ABI_CWindows_CGaming_CInput_CCustom_CIWineAsyncOperationCompletedHandler_Release+0xb(This=<internal
error>)
[Z:\home\winetest\tools\testbot\var\wine-win32\dlls\windows.gaming.input\provider.h:386]
in windows.gaming.input (0x0389fe08)
1 0x6fc81461 async_info_callback+0xc1(instance=<couldn't compute location>,
iface=<couldn't compute location>, work=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\windows.gaming.input\async.c:321]
in windows.gaming.input (0x0389fe08)
2 0x7bc602c6 tp_object_execute+0x2b6(object=<register ESI not accessible in
this frame>, wait_thread=0)
[Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\threadpool.c:2242] in ntdll
(0x0389feb8)
3 0x7bc60770 threadpool_worker_proc+0x110(param=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\threadpool.c:2356] in ntdll
(0x0389ff28)
4 0x7b62a290 in kernel32 (+0x2a290) (0x0389ff48)
5 0x7bc5cfa7 in ntdll (+0x5cfa7) (0x0389ff5c)
6 0x7bc5d7d0 RtlCreateUserThread(entry=7BC60660, arg=00185018)
[Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:306] in ntdll
(0x0389ffec)
0x6fc81461 async_info_callback+0xc1
[Z:\home\winetest\tools\testbot\var\wine\dlls\windows.gaming.input\async.c:321]
in windows.gaming.input: call *0x8(%eax)
321 LeaveCriticalSection( &impl->cs );
See https://test.winehq.org/data/patterns.html#dinput:force_feedback
This failure was first seen on 2023-01-06 and can happen on Windows 10 (e.g.
w1064-tsign-64) as well as Wine.
--
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=53479
Bug ID: 53479
Summary: dxgi:dxgi - Failed twice due to occlusion while
testing an invisible window vs a fullscreen swapchain
on Windows
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
dxgi:dxgi - Failed twice in test_swapchain_present() due to occlusion while
testing an invisible window vs a fullscreen swapchain on Windows:
dxgi.c:4792: Test failed: Test 0: Got unexpected hr 0x87a0001.
dxgi.c:4796: Test failed: Test 0: Got unexpected fullscreen status.
https://test.winehq.org/data/patterns.html#dxgi:dxgi
Where 0x87a0001 == DXGI_STATUS_OCCLUDED
This only happened on w1064v1507, on 2022-05-24 (32-bit) and 2022-07-27
(64-bit).
Maybe there's a window popping up that's causing the occlusion (from a previous
test crashing or a Windows notification)? Or maybe there is a message ordering
issue such that the windows states are not always as expected.
The only other case of occlusion issue happened on cw-rx460 when running
Windows 10 21H2. In that case the issue was systematic and happened earlier in
test_swapchain_present(), in the minimized window test and the set of failures
was different:
dxgi.c:4714: Test failed: Test 0: Got unexpected hr 0x87a0001.
dxgi.c:4735: Test failed: Test 0: Got unexpected hr 0x8876086a.
dxgi.c:4744: Test failed: Test 0: Got unexpected fullscreen status.
dxgi.c:4745: Test failed: Test 0: Got unexpected output.
dxgi.c:4753: Test failed: Test 0: Got unexpected fullscreen status.
dxgi.c:4765: Test failed: Test 0: Got unexpected fullscreen status.
--
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=53229
Bug ID: 53229
Summary: dxgi:dxgi - test_swapchain_window_messages() sometimes
gets an unexpected WM_DWMNCRENDERINGCHANGED message on
Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dxgi:dxgi - test_swapchain_window_messages() sometimes gets an unexpected
WM_DWMNCRENDERINGCHANGED message on Windows:
dxgi.c:5822: Test failed: Got unexpected message 0x31f, hwnd 00000000010E01E4,
wparam 0x1, lparam 0.
https://test.winehq.org/data/patterns.html#dxgi:dxgi
Where 0x31f == WM_DWMNCRENDERINGCHANGED.
This failure only happens on Windows 8 to Windows 10 1909.
The window handle also interferes with the TestBot's old failures detection.
Even without it, it would have an elevated risk of causing false positives due
to the test's multi-threading (see bug 53212).
--
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=54406
Bug ID: 54406
Summary: user32:msg - test_unicode_wm_char() sometimes gets an
unexpected WM_DWMNCRENDERINGCHANGED message on Windows
10+
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:msg - test_unicode_wm_char() sometimes gets an unexpected
WM_DWMNCRENDERINGCHANGED message on Windows 10+:
msg.c:16001: Test failed: unexpected message 31f
msg.c:16002: Test failed: bad wparam 1
msg.c:16008: Test failed: unicode WM_CHAR: 0: the msg sequence is not complete:
expected 0102 - actual 0000
msg.c:16008: Failed sequence unicode WM_CHAR:
msg.c:16008: 0: expected: msg 0102 - actual: nothing
See https://test.winehq.org/data/patterns.html#user32:msg
Where:
031f == WM_DWMNCRENDERINGCHANGED
The first instance happened on 2022-11-08 and there has only been about one
instance per month since.
This looks like some previous test did something that caused the non-client
rendering policy to change but did not wait for this message to be sent and
processed by all windows before continuing. So then which test gets impacted is
up to timing.
dxgi:dxgi has also been getting this message for a long time (see bug 53229).
--
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=54403
Bug ID: 54403
Summary: Robotill: A windows based point of sale application
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: bower.johan1(a)gmail.com
Distribution: ---
Created attachment 73969
--> https://bugs.winehq.org/attachment.cgi?id=73969
The atrtached is the bug report when the application terminate
Robotill. A windows based application. I want to use the application on a linux
based machine and trying to use bottles/wine to run the application.
--
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=54404
Bug ID: 54404
Summary: d3d8:device & d3d9:device - test_cursor_pos()
sometimes fails to set the cursor position on Windows
<= 8 without elevated privileges
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
d3d8:device & d3d9:device - test_cursor_pos() sometimes fails to set the cursor
position on Windows <= 8 without elevated privileges:
device.c:1247: Test failed: Failed to set cursor position.
See https://test.winehq.org/data/patterns.html#d3d8:devicehttps://test.winehq.org/data/patterns.html#d3d9:device
This started happening on 2022-12-08 and is tied to the lack of elevated
privileges on Windows 7 and 8. Yet the failure is not systematic.
--
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.