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=53327
Bug ID: 53327
Summary: Ragnarok Online bad performance
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: paulo1039(a)gmail.com
Distribution: ---
Created attachment 72711
--> https://bugs.winehq.org/attachment.cgi?id=72711
log running game client (shining.exe)
Hello, i'm playing some Ragnarok online private servers
(https://www.shining-moon.com) but the performance is really bad even on wine
7.12 i noticed the CPU usage is really high and the game is very choppy to
unplayable levels specially when skills effects, damage numbers and
monsters/players appear on screen.
this is happening with other private servers too.
sadly i can't test official servers since iRO and bRO has Easy-AntiCheat.
This was tested with Ryzen 5 5600G on fedora 36 and another computer with
nvidia gtx 1650 and arch linux.
--
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=53199
Bug ID: 53199
Summary: dinput:force_feedback - test_windows_gaming_input()
sometimes has unexpected reference counts in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
dinput:force_feedback - test_windows_gaming_input() sometimes has unexpected
reference counts in Wine. There are three known instance but they don't all
correspond to the same check:
2022-05-17
force_feedback.c:6097: Test failed: Release returned 1
6096 ref = IAsyncOperation_ForceFeedbackLoadEffectResult_Release(
result_async );
6097 ok( ref == 0, "Release returned %lu\n", ref );
2022-06-06 and 2022-06-17
force_feedback.c:6057: Test failed: Release returned 1
6056 ref = IForceFeedbackEffect_Release( effect );
6057 ok( ref == 0, "Release returned %lu\n", ref );
https://test.winehq.org/data/patterns.html#dinput:force_feedback
This failure can happen on its own (so it's not a side-effect of another
failure) and is pretty rare (~0.8%) so it's bound to cause false positives.
--
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=52875
Bug ID: 52875
Summary: riched20:editor fails in Wine in Hindi
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
riched20:editor fails in Wine in Hindi:
editor.c:6064: Test failed: EM_STREAMIN: Test UTF8Split returned 6
https://test.winehq.org/data/patterns.html#riched20:editor
It also has failures in Wine in other locales and on other Linux configurations
but this one is new. A bisect shows that it started after the following commit:
commit e81327358a26b160740b3421a4c7f300b4d2f06f
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Apr 13 15:13:16 2022 +0200
kernelbase: Move codepage initialization to ntdll.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
This commit is also involved in the following failures:
* Bug 52873 - oleaut32:typelib fails in Wine in Hindi
* Bug 52870 - shlwapi:url - The UrlGetPartA() tests fails in Wine in Hind
* Bug 52872 - vbscript:run fails in Wine in Hindi
--
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=52980
Bug ID: 52980
Summary: conhost.exe:tty - test_tty_input() fails in most
locales on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
conhost.exe:tty - test_tty_input() fails in most locales on Windows.
Specifically it fails in German, French, Portuguese (Brazil and Portugal), and
Spanish (the mixed locale, mx-MX, uses a Spanish keyboard layout).
For instance in Portuguese (Brazil):
tty.c:1521: Test failed: 2f: wVirtualKeyCode = 12, expected 11
tty.c:1521: Test failed: 2f: wVirtualScanCode = 38 expected 1d
tty.c:1521: Test failed: 2f: dwControlKeyState = 109
tty.c:1521: Test failed: 2f: dwControlKeyState = 9
[...]
tty.c:1521: Test failed: 3f: dwControlKeyState = 100
tty.c:1544: Test failed: 2f: wVirtualKeyCode = dd, expected db
tty.c:1544: Test failed: 2f: wVirtualScanCode = 1b expected 1a
tty.c:1544: Test failed: 2f: wVirtualKeyCode = dd, expected db
tty.c:1544: Test failed: 2f: wVirtualScanCode = 1b expected 1a
https://test.winehq.org/data/patterns.html#conhost.exe:tty
The test also fails on cw-gtx560 and cw-rx460, maybe because their keyboard
layout is not completely standard due to the KVM. Besides the usual failures on
lines 1521 and 1544, those get a few related earlier failures:
tty.c:1505: Test failed: 61: wVirtualScanCode = 4f expected 1e
tty.c:1505: Test failed: 61: wVirtualScanCode = 4f expected 1e
tty.c:1508: Test failed: 64: wVirtualScanCode = 4b expected 20
tty.c:1508: Test failed: 64: wVirtualScanCode = 4b expected 20
--
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.