https://bugs.winehq.org/show_bug.cgi?id=53488
Bug ID: 53488
Summary: The dxgi:dxgi output is too big on debiant
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: ---
The dxgi:dxgi output is too big in Wine.
It used to be about 24 KB but the commit below pushed it to 34 KB, over the 32
KB limit.
Then on 2022-07-22 another commit improved the situation on debian11 but not on
debiant where the size has not changed since the commit below.
commit 184ff3bfbb4be3e3fbcfaaba3ec7095d2d885882
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Sat Jun 11 19:36:20 2022 +0300
dxgi: Create DXGI resource object, optionally supporting surface
interfaces.
Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com>
dlls/d3d11/d3d11_private.h | 4 +-
dlls/d3d11/tests/d3d11.c | 7 -
dlls/d3d11/texture.c | 130 +++++++-------
dlls/dxgi/Makefile.in | 2 +-
dlls/dxgi/device.c | 24 +--
dlls/dxgi/dxgi_private.h | 11 +-
dlls/dxgi/resource.c | 423 +++++++++++++++++++++++++++++++++++++++++++++
dlls/dxgi/surface.c | 296 -------------------------------
dlls/dxgi/tests/dxgi.c | 34 ++--
include/wine/winedxgi.idl | 7 +-
10 files changed, 526 insertions(+), 412 deletions(-)
create mode 100644 dlls/dxgi/resource.c
delete mode 100644 dlls/dxgi/surface.c
--
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=54553
Bug ID: 54553
Summary: mmdevapi:propstore - The 32-bit
test_setvalue_on_wow64() fails on Windows 10 2004+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mmdevapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mmdevapi:propstore - The 32-bit test_setvalue_on_wow64() fails on Windows 10
2004+:
propstore.c:186: Test failed: Wrong error when opening mmdevices Render key: 0
See propstore.c:186: Test failed: Wrong error when opening mmdevices Render
key: 0
As far as I can tell what this means is that the assumption that "should NOT
find the key in 32-bit view" is incorrect on Windows 10 2004+.
So maybe the old behavior should be considered to be broken() nowadays?
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=53172
Bug ID: 53172
Summary: advapi32:registry - test_enum_value() has a pair of
rare failures in UTF-8 system locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8
system locales:
registry.c:558: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of
'foobar' or x's, data_count=21
registry.c:576: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of
'foobar' or x's, data_count=21
https://test.winehq.org/data/patterns.html#advapi32:registry
The line 558 and 576 failures happen about with the same frequency (~13% each)
but independently from each other so that most times there is at most one in
the report.
And they only happen in the TestBot's two UTF-8 test configurations:
w10pro64-en-AE-u8 and w10pro64-hi-u8.
--
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=54657
Bug ID: 54657
Summary: kernel32:loader - test_import_resolution() gets bad
tls data on Windows 7
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 - test_import_resolution() gets bad tls data on Windows 7:
loader.c:2324: Test failed: wrong tls data 'hello world' at 0000000000320590
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.
https://bugs.winehq.org/show_bug.cgi?id=54531
Bug ID: 54531
Summary: jsproxy:jsproxy crashes on Windows 11
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
jsproxy:jsproxy crashes on Windows 11:
jsproxy.c:52: Test failed: got 3735928559
jsproxy.c:56: Test failed: got 3735928559
jsproxy.c:59: Test failed: got 3735928559
jsproxy.c:60: this is the last test seen before the exception
054c:jsproxy: unhandled exception c0000005 at 004013FA
See https://test.winehq.org/data/patterns.html#jsproxy:jsproxy
Where 3735928559 == 0xdeadbeef
So InternetGetProxyInfo() fails but does not set LastError. Furthermore the
proxy pointer is not initialized either so the test crashes when trying to free
it.
--
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=54504
Bug ID: 54504
Summary: psapi:psapi_main - The 32-bit
test_EnumProcessModules() gets a partial copy error 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 32-bit test_EnumProcessModules() gets a partial copy
error on Windows 11:
psapi_main.c:133: Test failed: got 0, error 299
psapi_main.c:134: Test failed: expected non-NULL module
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
Where 299 == ERROR_PARTIAL_COPY
This failure is specific to the 32-bit tests running on Windows 11, that is the
64-bit test has other (possibly related) failures, and Windows 10 and lower
don't have failures.
Also this failure has been present ever since the Windows 11 VM was added.
--
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=54019
Bug ID: 54019
Summary: The 64-bit ntdll:wow64 fails on Windows 11
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
The 64-bit ntdll:wow64 fails on Windows 11. There are two failure modes:
wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 /
00000013640C5000
wow64.c:273: Test failed: wrong len 0
wow64.c:290: Test failed: wrong len 0
wow64.c:312: Test failed: wrong len 0
wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 75cec0-75d884
wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210
wow64.c:321: Test failed: wrong CommandLine ptr 0 / 75cec0-75d884
wow64.c:321: Test failed: wrong CommandLinelen 0 / 66
wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 75cec0-75d884
wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210
wow64.c:323: Test failed: wrong Desktop ptr 0 / 75cec0-75d884
wow64.c:323: Test failed: wrong Desktoplen 0 / 30
wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 75cec0-75d884
wow64.c:326: Test failed: wrong size 0 / 3222
wow64.c:338: Test failed: wrong len 0
wow64.c:339: Test failed: BeingDebugged is 0
or with 2 extra failures and different values:
wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 /
000000A7ECDDA000
wow64.c:273: Test failed: wrong len 0
wow64.c:290: Test failed: wrong len 0
wow64.c:291: Test failed: BeingDebugged is 117
wow64.c:309: Test failed: wrong ptr32 0000000000000000 / 00000298B3F80000
wow64.c:312: Test failed: wrong len 0
wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 0-9c4
wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210
wow64.c:321: Test failed: wrong CommandLine ptr 0 / 0-9c4
wow64.c:321: Test failed: wrong CommandLinelen 0 / 66
wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 0-9c4
wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210
wow64.c:323: Test failed: wrong Desktop ptr 0 / 0-9c4
wow64.c:323: Test failed: wrong Desktoplen 0 / 30
wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 0-9c4
wow64.c:326: Test failed: wrong size 0 / 3112
wow64.c:338: Test failed: wrong len 0
wow64.c:339: Test failed: BeingDebugged is 117
See https://test.winehq.org/data/patterns.html#ntdll:wow64
The values are pretty stable from one run to the next but do change from time
to time (causing false positives). Note also that the 32-bit version fails on
Windows 11 too.
--
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=52895
Bug ID: 52895
Summary: advapi32:service - EnumServicesStatusA() does not
support UTF-8 on Windows?
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:service fails on Windows with a UTF-8 codepage:
service.c:1283: Test failed: Expected success, got error 8
service.c:1285: Test failed: Expected some returned services
service.c:1312: Test failed: Expected the needed buffer size for this one
service
service.c:1313: Test failed: Expected fewer services to be returned
service.c:1314: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1326: Test failed: Expected the needed buffer size for this one
service
service.c:1327: Test failed: Expected fewer services to be returned
service.c:1328: Test failed: Expected a resume handle
service.c:1329: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1340: Test failed: Expected success, got error 8
service.c:1342: Test failed: Expected 559038737 services to be returned
service.c:1610: Test failed: Expected success, got error 8
service.c:1627: Test failed: Expected the needed buffer size
service.c:1628: Test failed: Expected fewer services to be returned
service.c:1629: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1641: Test failed: Expected the needed buffer size
service.c:1642: Test failed: Expected fewer services to be returned
service.c:1643: Test failed: Expected a resume handle
service.c:1644: Test failed: Expected ERROR_MORE_DATA, got 1783
service.c:1655: Test failed: Expected success, got error 8
service.c:1657: Test failed: Expected 559038737 services to be returned
service.c:1702: Test failed: Expected success 8
https://test.winehq.org/data/patterns.html#advapi32:service
The first failure is an ERROR_NOT_ENOUGH_MEMORY in this call:
services = HeapAlloc(GetProcessHeap(), 0, needed);
bufsize = needed;
needed = 0xdeadbeef;
returned = 0xdeadbeef;
SetLastError(0xdeadbeef);
ret = EnumServicesStatusA(scm_handle, SERVICE_WIN32, SERVICE_STATE_ALL,
services, bufsize, &needed, &returned, NULL);
Where needed was calculated from a previous call (30890 in my case). So the
buffer should be big enough but EnumServicesStatusA() fails anyway. I tried
increasing the buffer size to the max 256KB but EnumServicesStatusA() still
complains about insufficient memory which does not make sense.
Later, when given a resume handle, the tests return RPC_X_BAD_STUB_DATA (1783)
instead of ERROR_MORE_DATA (234).
So this looks like the underlying RPC code that accesses the service control
manager is buggy and does not support UTF-8. So win_skip() the whole thing on
the first failure? Move the resume test with the RPC_X_BAD_STUB_DATA first and
skip if that fails?
--
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=53461
Bug ID: 53461
Summary: advapi32:service - test_EventLog() fails on Windows 10
2004 and 2009
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:service - test_EventLog() fails on Windows 10 2004 and 2009:
service.c:2751: Test failed: got 0x1 --> SERVICE_STOPPED
service.c:2753: Test failed: got 0
service.c:2757: Test failed: got 0x42b --> ERROR_PROCESS_ABORTED
service.c:2761: Test failed: got 0
https://test.winehq.org/data/patterns.html#advapi32:service
The failures appear to be happening because the EventLog service is stopped
following some sort of error (crash?).
These failures are systematic when running WineTest.exe but don't happen when
running advapi32:service on its own. So it seems likely that some other test is
causing EventLog to crash.
--
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=53460
Bug ID: 53460
Summary: advapi32:service regularly fails on Windows when
services stop / start
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
advapi32:service regularly fails on Windows when services stop / start.
Because this may happen at any time the failures can take many forms:
service.c:1729: Test failed: Expected a process id for this running service
(sppsvc)
service.c:1746: Test failed: Active services mismatch 4294967295
service.c:1747: Test failed: Inactive services mismatch 1
or
service.c:1729: Test failed: Expected a process id for this running service
(SgrmBroker)
...
or
service.c:1746: Test failed: Active services mismatch 1
service.c:1747: Test failed: Inactive services mismatch 4294967295
or
service.c:1342: Test failed: Expected 114 services to be returned
service.c:1612: Test failed: Expected the same number of service from this
function
or
service.c:1729: Test failed: Expected a process id for this running service
(edgeupdate)
or
service.c:1729: Test failed: Expected a process id for this running service
(MapsBroker)
or
service.c:1729: Test failed: Expected a process id for this running service
(W32Time)
or
service.c:1729: Test failed: Expected a process id for this running service
(BITS)
or
service.c:1729: Test failed: Expected a process id for this running service
(DoSvc)
https://test.winehq.org/data/patterns.html#advapi32:service
The service names give a hint as to what happened:
* An Edge update got triggered: edgeupdate, probably BITS too.
* A time synchronization happened: W32Time.
* Some application caused the on-demand "Downloaded Maps Broker" service to
start: MapsBroker.
* Something caused Windows Update Delivery Optimization to start (despite it
being disabled in the settings): DoSvc.
* The 'System Guard Runtime Monitor Broker Service' got started for some
reason: SgrmBroker.
* The 'Microsoft Software Protection Platform Service' which is involved in the
license checking got started: sppsvc.
So I don't think it would be reasonable to disable all these services. We would
still likely have a steady trickle of other services causing trouble, and we'd
have the problem again when a new Windows version introduces another service.
Instead advapi32:service should be more resilient. That may mean accepting
small variations in the number of running services, or checking that a service
is still running before complaining that it does not have a pid.
--
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=54694
Bug ID: 54694
Summary: Marvel's Spider-Man Remastered requires Windows 10
version 1909, build 18363 (or newer)
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
As the title says.
8.3-258-g81976e5c3f4
--
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=53562
Bug ID: 53562
Summary: SWAT 4: mouse wrapping issues
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matheus.venturini(a)acad.ufsm.br
Distribution: ---
When beginning a mission in SWAT 4, the mouse will (most often) not allow you
to fully rotate your vision in 360 degrees. This can be "fixed" by simply
right-clicking, which will cause it to start acting normal.
I've had times where this did not occur when starting a mission so I can't say
it's a "can always reproduce" issue, and sometimes, very sporadically, the
mouse starts acting faulty again during gameplay for seemingly no reason.
Doing a search, I found an entry for the same issue in Codeweavers' forum:
https://www.codeweavers.com/compatibility/crossover/forum/swat-4?msg=108881
The fix suggested in that page, to set "MouseWarpOverride" to "force_edge" in
the registry, was not necessary since doing a right-click will make it go back
to normal.
Apparently some other games are also affected (GTA Vice City and Bioshock
according to the discussion in https://forum.winehq.org/viewtopic.php?t=29663).
I will try to reproduce the issue and attach the log file.
--
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=54419
Bug ID: 54419
Summary: RICHED20: Word Break Procedure of Rich TextBox should
consider punctuation
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: katayama.hirofumi.mz(a)gmail.com
Distribution: ---
Created attachment 73977
--> https://bugs.winehq.org/attachment.cgi?id=73977
the patch to the word break procedure of rich textbox
The default word break procedure of rich textbox didn't consider punctuation.
This patch will add punctuation check to the default word break procedure.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=33008
Bug #: 33008
Summary: UDP listening on specific IP address does not work
properly
Product: Wine
Version: 1.5.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: decimusmaximus(a)seznam.cz
Classification: Unclassified
Wine updated from 1.5.6 to 1.5.24.
My app uses UDP listening on specific address (not 0.0.0.0). It is running on
machine with NAT, there are two interfaces with IP A.A.A.A (public) and IP
B.B.B.B (private) My app is set to listen only on one IP address, IP A.A.A.A
It works properly on Wine 1.5.6. Traffic from subnet B.B.B.B is NATed to
A.A.A.A interface and application running in wine receives it correctly.
After update to 1.5.24 it does not work anymore.
Application does not receive data from private subnet B.B.B.B, however it works
properly for traffic incoming on A.A.A.A interface.
Please see attached schema.
results of "netstat --listening"
with Wine 1.5.6 it is listening on A.A.A.A address correctly.
with Wine 1.5.24 it is listening on 0.0.0.0 (obviously incorrect, socket
binding is set to A.A.A.A address in application and although it is saying
0.0.0.0 app does not receive any data from B.B.B.B network)
This application has to be listening only on one interface and do not mix
public and private addresses. In this case it is not accessible for clients in
private network, so it is critical bug.
Main strange thing is, that it is listening on all addresses 0.0.0.0 although
socket binding in application is set to address A.A.A.A
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=54671
Bug ID: 54671
Summary: netcap.exe crashes on unimplemented function
npptools.dll.CreateBlob
Product: Wine
Version: 8.3
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 74187
--> https://bugs.winehq.org/attachment.cgi?id=74187
Console output
netcap.exe is the "Microsoft Network Monitor capture utility". It was included
in the Windows XP Service Pack 2 Support Tools.
Steps to reproduce:
1. Create a 32-bit Wine bottle and set the Windows version to XP.
2. Run `wine WindowsXP-KB838079-SupportTools-ENU.exe`.
3. Run `wine 'C:\Program Files\Support Tools\netcap.exe'`.
The program will not start.
$ sha256sum WindowsXP-KB838079-SupportTools-ENU.exe
7927e87af616d2fb8d4ead0db0103eb845a4e6651b20a5bffea9eebc3035c24d
--
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.