https://bugs.winehq.org/show_bug.cgi?id=51780
Bug ID: 51780
Summary: The user32:msg output is too big in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:msg now outputs ~97kB of data. This is way too much and contributes in
pushing the WineTest reports above the 1.5MB limit.
No single patch is responsible but the size changed on the following dates:
Sep 08: user32:msg (+6kB)
Sep 09: user32:msg (+18kB)
Sep 17: user32:msg (+6kB)
Sep 20: user32:msg (+15kB)
Sep 21: user32:msg (+19kB)
The traces break down as follows:
0kB failures
77kB todos
16kB traces
1.5kB test framework (summary lines, etc.)
Time to fix Wine to reduce the number of todos!
--
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=53254
Bug ID: 53254
Summary: urlmon:url - test_URLDownloadToFile_abort() sometimes
fails on Windows 7+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:url - test_URLDownloadToFile_abort() sometimes fails on Windows 7+:
url.c:3750: Test failed: expected OnProgress_DOWNLOADINGDATA
https://test.winehq.org/data/patterns.html#urlmon:url
This happens on Windows 7 to Windows 10 21H2 and is rare enough to cause false
positives. Note that this failure never happens at the same time as the ones in
bug 53253.
--
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=53211
Bug ID: 53211
Summary: ddraw:ddraw1 has over 255 failures on the debian11
TestBot VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ddraw:ddraw1 has over 255 failures on the debian11 TestBot VMs:
ddraw1.c:6647: Test failed: Got unexpected color 0x000000ff, test 0.
...
ddraw1.c:6953: Test failed: Unlit quad without normals has color 0x00ffffff.
...
ddraw1.c:6955: Test failed: Lit quad without normals has color 0x00ffffff.
...
ddraw1.c:7377: Test failed: Expected colour 0x003c3c3c at location (160, 120),
got 0x00ff0000, case 0.
...
ddraw1.c:8425: Test failed: Got unexpected color 0x00000000.
...
ddraw1.c:9590: Test failed: Got unexpected color 0x0000ff00, format
D3DFMT_X8R8G8B8, c=0.
...
ddraw1.c:9846: Test failed: Test 0 shading has color0 00ffffff, expected
00ff0000.
...
ddraw1.c:11527: Test failed: Got unexpected color 0x000000ff.
...
ddraw1.c:11924: Test failed: Got unexpected color 0x00ffffff.
...
ddraw1.c:12549: Test failed: z_depth 16: Got depth 0x0000ffff (diff -57344),
expected 0x00001fff+/-46, at 80, 60.
...
ddraw1.c:420: Test failed: (0, 0) - (640, 480) viewport: Pixel (1, 121) has
color 00000000, expected 00ffffff.
...
ddraw1.c:13757: Test failed: Alphatest failed, color 0x00ff0000, expected
0x0000ff00, alpha > ref, func 5.
...
ddraw1.c:14638: Test failed: Got color 0x00ff0000, expected 0x00ffffff.
...
ddraw1.c:15080: Test failed: Got unexpected colour 000000ff, 2x2, case 0.
...
The test prints too much data (96495 bytes)
https://test.winehq.org/data/patterns.html#ddraw:ddraw1
These failures started when the debian11 VM was updated and moved to the gpu1
VM host. Given that the debiant (Debian Testing) VM does not have these
failures this is likely related to some underlying Debian 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=52910
Bug ID: 52910
Summary: mshtml:htmldoc fails on Windows with the UTF-8
codepage
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mshtml:htmldoc fails on Windows with the UTF-8 codepage:
htmldoc.c:1472: Test failed: bindinfo.dwOptions=20000
htmldoc.c:597: Test failed: bindinfo.dwOptions=20000
[...]
https://test.winehq.org/data/patterns.html#mshtml:htmldoc
0x20000 is BINDINFO_OPTIONS_ENABLE_UTF8 which means that "UTF-8 encoding should
be enabled". Easy fix?
--
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=52909
Bug ID: 52909
Summary: rpcrt4:ndr_marshall crashes on the latest Windows 21H1
and 21H2
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: rpc
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
rpcrt4:ndr_marshall crashes on the latest Windows 21H1 and 21H2.
ndr_marshall.c:165: this is the last test seen before the exception
0770:ndr_marshall: unhandled exception 000006f7 at 00007FFCF0874F69
However the crash is not detected as such so the patterns page reports it as a
failure:
https://test.winehq.org/data/patterns.html#rpcrt4:ndr_marshall
I don't know what this 0x000006f7 exception is.
When w10pro64 had the updates up to 2021-10-21 this test was not crashing. The
crashes started happening when w1064 and w10pro64 were updated on 2022-04-24.
So the crash is probably caused by one of the Windows updates in that interval.
If necessary I can dig into the Windows update history to try and find
something related.
--
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=51456
Bug ID: 51456
Summary: oleaut32:typelib: test_CreateTypeLib(SYS_WIN32) fails
in 64-bit Wine
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
oleaut32:typelib has many failures in 64-bit Wine, the first one of which is
because Wine returns the wrong size for a structure:
https://test.winehq.org/data/patterns.html#oleaut32:typelib
typelib.c:2169: Test failed: retrieved IUnknown gave wrong cbSizeVft: 24
In the SYS_WIN32 case cbSizeVft should be 3 * 4 = 12 but it is still set to 24
by MSFT_DoTypeInfo():
ptiRet->typeattr.cbSizeVft = tiBase.cbSizeVft;
It makes sense for cbSizeVft to be 24 on the 64-bit side, but somewhere there
should be code to adjust it to account for the SYS_WIN32 on 64-bit case. But I
don't know where that should happen.
--
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=48105
Bug ID: 48105
Summary: kernel32:console fails on Japanese and Chinese Windows
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Running the kernel32:console test on Windows 10 1809 in Japanese or Chinese
results in 6 failures:
console.c:867: Test failed: ReadConsoleOutputCharacterW failed
console.c:869: Test failed: string does not match the pattern
console.c:880: Test failed: ReadConsoleOutputCharacterW failed
console.c:882: Test failed: string does not match the pattern
console.c:889: Test failed: ReadConsoleOutputCharacterW failed
console.c:891: Test failed: string does not match the pattern
These failures appear to be systematic but the w1064v1809_ja and
w1064v1809_zh_CN VMs do not always succeed in submitting their WineTest results
to test.winehq.org so the failures only appear intermittently there.
See https://test.winehq.org/data/tests/kernel32:console.html
--
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=46649
Bug ID: 46649
Summary: Tom Clancy's Rainbow Six: Vegas 2 needs
D3DXDisassembleShader implementation
Product: Wine
Version: 4.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Crashes at launch with 'Message General protection fault! History: '
fixme:d3dx:D3DXDisassembleShader 0x7671b00 0 (null) 0x62ce18: stub
wine-4.1-207-g7907ccfdcb
--
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=53684
Bug ID: 53684
Summary: ntdll:info is broken on Windows 8 to 10 1709 in the
GitLab WineTest builds
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 is broken in the GitLab WineTest builds:
info.c:1097: Test failed: Expected STATUS_SUCCESS, got 80000002
info.c:1102: Test failed: Expected STATUS_SUCCESS, got 80000002
Where 0x80000002 = STATUS_DATATYPE_MISALIGNMENT.
https://test.winehq.org/data/patterns.html#ntdll:info
The failures started on 2022-07-26 which is when the WineTest builds switched
from the old build system to GitLab. A test with winetest-889fe64d9f2e.exe
(built on 2022-07-25) confirms that this test still succeeds when using
binaries from the old build system.
Strangely enough the failures only happen on Windows 8 to Windows 10 1709.
--
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=53678
Bug ID: 53678
Summary: vbscript can not compile CaseClausules that do not use
a colon
Product: Wine
Version: 7.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: jsm174(a)gmail.com
Distribution: ---
While working on leveraging the vbscript engine of Wine for a macos port of
Visual Pinball, I've been testing several user made scripts.
I've found a few scripts, where users did not use a colon after a case. This
seems to work in vbscript:
Set g_objWSH = Wscript.CreateObject("Wscript.Shell")
dim x
x = 2
Select Case x
Case 0: 'If Enabled Then
Case 2 Wscript.Echo "This works 2"
Case 3: Wscript.Echo "This works 3"
Case 4
Wscript.Echo "This works 4"
End Select
--
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.