https://bugs.winehq.org/show_bug.cgi?id=54078
Bug ID: 54078
Summary: ntdll:pipe - test_blocking() sometimes fails in Wine
when the pipe is not signaled
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntdll:pipe - test_blocking() sometimes fails in Wine when the pipe is not
signaled:
pipe.c:1769: Test marked todo: client is not signaled
pipe.c:1751: Test failed: pipe is not signaled
pipe.c:1769: Test marked todo: client is not signaled
pipe.c:1770: Test failed: pipe is not signaled
See https://test.winehq.org/data/patterns.html#ntdll:pipe
Here is this failure's nightly WineTest run history:
* There was no failure in June and July.
* The first known failure happened on 2022-08-13, the next on 2022-08-18.
* The third failure happened on 2022-09-23.
* The fourth on 2022-11-04 which was followed by 9 more in November.
So it's likely something changed in early August-ish that introduced this
failure. But there has been a further change in November that makes it more
frequent (maybe the latter is because the TestBot now runs two VMs at a time so
the host is more busy, though that started a bit earlier, on 2022-10-25).
This failure also happens in the GitLab CI.
--
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=53974
Bug ID: 53974
Summary: d3drm:d3drm sometimes crashes after failing to create
the IDirect3DRMDevice* interface in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3drm:d3drm sometimes crashes after failing to create the IDirect3DRMDevice*
interface in Wine:
d3drm.c:4600: Test failed: Cannot create IDirect3DRMDevice interface, hr
0x8007000e.
d3drm.c:4602: Test failed: expected ref2 > ref1, got ref1 = 1 , ref2 = 1.
d3drm.c:4604: Test failed: Expected surface_ref2 > surface_ref1, got
surface_ref1 = 1, surface_ref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0040e52b).
[...useless backtrace...]
d3drm.c:4776: Test failed: Cannot create IDirect3DRMDevice2 interface, hr
0x8007000e.
d3drm.c:4778: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1.
d3drm.c:4782: Test failed: Expected surface_ref2 > surface_ref1, got
surface_ref1 = 1, surface_ref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x004106c1).
[...useless backtrace...]
d3drm.c:4407: Test failed: Cannot create IDirect3DRMDevice3 interface, hr
0x8007000e.
d3drm.c:4409: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1.
d3drm.c:4413: Test failed: expected cref2 > cref1, got cref1 = 1 , cref2 = 1.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x0041290a).
[...useless backtrace...]
See https://test.winehq.org/data/patterns.html#d3drm:d3drm
The two "expected..." failures are not always present. This has been seen on
debian11, debiant but also fgtb-debian11 and gitlab-debian. So it's not
specific to dual-screen configurations nor to QEmu's QXL driver. But it seems
to only happen on "virtual GPUs" (gitlab-debian uses Xorg's dummy driver).
--
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=53528
Bug ID: 53528
Summary: ntdll:info - test_query_kerndebug() fails on Windows 8
to 10 1709
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:info - test_query_kerndebug() fails on Windows 8 to 10 1709:
info.c:1097: Test failed: Expected STATUS_SUCCESS, got 80000002
info.c:1102: Test failed: Expected STATUS_SUCCESS, got 80000002
https://test.winehq.org/data/patterns.html#ntdll:info
The failures started on 2022-07-26.
--
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=53182
Bug ID: 53182
Summary: shell32:shelllink - A save(NULL, TRUE) fails randomly
in test_load_save() on Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
A save(NULL, TRUE) fails randomly in test_load_save() on Wine:
shelllink.c:775: Test failed: save(NULL, TRUE) failed (0x80070020)
https://test.winehq.org/data/patterns.html#shell32:shelllink
This is probably the same issue as bug 28290, the only difference being that it
does not happen at a point that leads to a NULL pointer access.
--
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=52948
Bug ID: 52948
Summary: gdi32:font - test_EnumFonts() fails on Arial Bold on
Windows in Russian
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:font - test_EnumFonts() fails on Arial Bold on Windows in Russian:
font.c:5409: Test failed: font Arial Bold is not enumerated
font.c:5412: Test failed: expected FW_BOLD got 400
font.c:5419: Test failed: font Arial Bold Italic is not enumerated
font.c:5421: Test failed: expected Arial got Arial Bold
font.c:5422: Test failed: expected FW_BOLD got 400
https://test.winehq.org/data/patterns.html#gdi32:font
Maybe this can happen in other locales, but among those that are tested this
only happens with the Russian one (w10pro64-ru).
--
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=51848
Bug ID: 51848
Summary: Performance Regression in Secondhand Lands
Product: Wine
Version: 6.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: escomk3(a)hotmail.com
Distribution: ---
After 4261369e5d8 [1], FPS will be near zero, and the game area will be black,
with the actual should-be content sometimes appearing and disappearing.
Standard output with default'ish debug channels doesn't show any difference
with a build prior to this commit.
1.
https://source.winehq.org/git/wine.git/commit/4261369e5d8f1d71e8d2074747515…
--
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=54649
Bug ID: 54649
Summary: windows.perception.stub:perception - Windows 10 1607
does not have ISpatialSurfaceObserverStatics2
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
windows.perception.stub:perception - Windows 10 1607 does not have
ISpatialSurfaceObserverStatics2:
perception.c:76: Test failed: got hr 0x80004002.
perception.c:76: this is the last test seen before the exception
088c:perception: unhandled exception c0000005 at 00401483
See
https://test.winehq.org/data/patterns.html#windows.perception.stub:percepti…
Where 0x80004002 == E_NOINTERFACE
This test was introduced in the commit below:
commit 006bc33c57c96bd733147c4088d36bfc14da907e
Author: Mohamad Al-Jaf <mohamadaljaf(a)gmail.com>
AuthorDate: Thu Feb 23 03:50:15 2023 -0500
windows.perception.stub: Add ISpatialSurfaceObserverStatics2 stub
interface.
--
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=54539
Bug ID: 54539
Summary: Starcraft Remastered Game Initialization Failed
Product: Wine
Version: 8.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: uberdude555(a)yahoo.com
Distribution: ---
Created attachment 74080
--> https://bugs.winehq.org/attachment.cgi?id=74080
stdout
I updated from wine 7.0-rc3 to 8.2, and when I try to start StarCraft now I see
an error dialog box with text "Game Initialization Failed: T".
I tried running the exe directly (rather than through the Battle.net client)
and saw the same error with only the four lines attached written to the
terminal.
The AppDB page shows at least three other users experiencing the same issue
from version 8.1 and possibly earlier:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=35171.
--
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=54509
Bug ID: 54509
Summary: psapi:psapi_main - The 64-bit
test_EnumProcessModules() gets unexpected third module
on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 64-bit test_EnumProcessModules() gets unexpected third
module on Windows 11:
psapi_main.c:185: Test failed: third DLL in wow64 should be one of wow*.dll
(kernel32.dll)
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
This test and failure was introduced by the commit below:
commit 00bf7293af13f3766c6c839f0125785ac9084de8
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Tue Feb 14 11:07:01 2023 +0100
psapi: Add more tests for EnumProcessModules().
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
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=54003
Bug ID: 54003
Summary: vbscript:run sometimes fails on Windows UTF-8 locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
vbscript:run sometimes fails on UTF-8 locales:
=== w10pro64_en_AE_u8 (64 bit report) ===
vbscript:
run.c:1206: Test failed: api.vbs: L"Err.number = 0"
run.c:1206: Test failed: api.vbs: L"Err.description = "
run.c:1206: Test failed: api.vbs: L"Err.number = 0"
See https://gitlab.winehq.org/wine/wine/-/merge_requests/1534
Strangely enough so far this has not happened in the nightly WineTest runs but
it did happen in another unrelated merge request (MR!1561).
According to Nikolay (probably s/testChrError/testCStrError/):
> This is happening on utf-8 locale, in testChrError().
> Needs to be fixed, but unrelated to this MR.
--
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.