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=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.
https://bugs.winehq.org/show_bug.cgi?id=53233
Bug ID: 53233
Summary: ddraw:ddraw1 - test_clear() has rare failures in Wine
on the debian11 VM
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 - test_clear() has rare failures in Wine on the debian11 VM:
ddraw1.c:12626: Test failed: Clear rectangle 3 (pos, neg) has color 0x00000000.
ddraw1.c:12628: Test failed: Clear rectangle 1 (pos, pos) has color 0x00000000.
ddraw1.c:12630: Test failed: Clear rectangle 4 (NULL) has color 0x00000000.
ddraw1.c:12632: Test failed: Clear rectangle 4 (neg, neg) has color 0x00000000.
https://test.winehq.org/data/patterns.html#ddraw:ddraw1
The first instance of these failures started some time after 2022-06-06 which
is when the debian11 VM was updated and moved to the gpu1 VM host.
--
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=53208
Bug ID: 53208
Summary: user32:msg - The SW_SHOWMINIMIZED test in
test_messages() succeeds in Wine with fvwm
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:msg - The SW_SHOWMINIMIZED test in test_messages() succeeds in Wine with
fvwm:
msg.c:5574: Test succeeded inside todo block:
ShowWindow(SW_SHOWMINIMIZED):overlapped: marked "todo_wine" but succeeds
https://test.winehq.org/data/patterns.html#user32:msg
This todo_wine seems to always succeed in the TestBot's VMs but almost always
fails on my box. The difference is probably that the former runs fvwm (with a
specially curated configuration) while the latter runs KDE.
--
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=53207
Bug ID: 53207
Summary: user32:msg - test_button_messages() fails randomly in
Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:msg - test_button_messages() fails randomly in Wine. There are two
failure modes:
* WM_CTLCOLORBTN (0x135) + WM_DRAWITEM (0x2b) -> 6 failures
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 4: the msg 0x0007 was
expected, but got msg 0x0005 instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 5: the msg 0x0135 was
expected, but got msg 0x030f instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 6: the msg 0x002b was
expected, but got msg 0x001c instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 7: the msg 0x0111 was
expected, but got msg 0x0086 instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 8: the msg 0x8000 was
expected, but got msg 0x0006 instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 9: the msg sequence is not
complete: expected 0000 - actual 0009
* WM_CTLCOLORSTATIC (0x138) -> 5 failures
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 4: the msg 0x0007 was
expected, but got msg 0x0005 instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 5: the msg 0x0138 was
expected, but got msg 0x030f instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 6: the msg 0x0111 was
expected, but got msg 0x001c instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 8: the msg 0x8000 was
expected, but got msg 0x0086 instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 9: the msg sequence is not
complete: expected 0000 - actual 0006
https://test.winehq.org/data/patterns.html#user32:msg
These failures don't seem to depend on the locale or bitness and were first
seen on 2022-06-06.
--
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=52965
Bug ID: 52965
Summary: kernel32:locale - test_GetLocaleInfoW() and
test_invariant() fail on Windows in Hindi
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:locale fails on Windows in Hindi when run without the UTF-8 codepage
(so with an English system locale):
In test_GetLocaleInfoW():
locale.c:394: Test failed: got wrong name
L"\0905\092e\0947\0930\093f\0915\093e"
locale.c:404: Test failed: got wrong name
L"\0905\0902\0917\094d\0930\0947\091c\093c\0940
(\0938\0902\092f\0941\0915\094d\0924 \0930\093e\091c\094d\092f)"
locale.c:5096: Test failed: got L"\0905\092e\0947\0930\093f\0915\093e"
In test_invariant():
locale.c:5728: Test failed: Expected ret == 39, got 33, error 87
locale.c:5729: Test failed: Expected Invariant Language (Invariant Country),
got '?????????? ???? (?????????? ???)'
locale.c:5733: Test failed: Expected ret == 18, got 15, error 87
locale.c:5734: Test failed: Expected Invariant Country, got '?????????? ???'
locale.c:5738: Test failed: Got '??? ??????????????'
https://test.winehq.org/data/patterns.html#kernel32:locale
This can be reproduced with the w10pro64-hi test configuration but these
failures do not happen when using UTF-8 (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=52507
Bug ID: 52507
Summary: user32:win has some spurious GetScrollInfo failures
Product: Wine
Version: 7.0-rc1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: rbernon(a)codeweavers.com
Distribution: ---
On some VMs and with some window styles, the GetScrollInfo SB_HORZ test
sometimes fails with "style 0x100000: expected !100".
It was happening consistently on Win10 on the submission test VMs, and tweaking
the window size in 34d1c100b044afa5eb6d6243e9fb40db085b78d2 fixed the issue
there, but it now fails on more VMs on the testbot pattern page.
--
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=53183
Bug ID: 53183
Summary: shell32:shelllink - test_load_save() randomly fails to
delete test.lnk in 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: ---
shell32:shelllink - test_load_save() randomly fails to delete test.lnk in Wine:
shelllink.c:818: Test failed: failed to delete link
'C:\users\winetest\Temp\\test.lnk' (32)
https://test.winehq.org/data/patterns.html#shell32:shelllink
This is probably the same issue as bug 28290, the only difference being that it
happens during the cleanup and thus does not cause a 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=53342
Bug ID: 53342
Summary: quartz:mpegaudio - The 64-bit test_streaming_events()
times out on fg-deb64
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
quartz:mpegaudio - The 64-bit test_streaming_events() times out on fg-deb64:
...
mpegaudio.c:1451: Test succeeded
https://test.winehq.org/data/patterns.html#quartz:mpegaudio
The timeout happens on this line:
hr = IMemAllocator_GetBuffer(allocator, &sample, NULL, NULL, 0);
A bisect shows that the timeouts started with the commit below:
commit 6c110bd398de28613b34555ff2738e74191bb6cd
Author: Rémi Bernon <rbernon(a)codeweavers.com>
Date: Mon Jun 13 11:43:51 2022 +0200
winegstreamer: Support zero-copy wg_transform_push_data in
quartz_transform.c.
Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.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=52877
Bug ID: 52877
Summary: user32:msg - test_dbcs_wm_char() fails in Wine in the
Japanese and Chinese locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
test_dbcs_wm_char() fails in Wine in the Japanese and Chinese locales.
For the Japanese locale:
msg.c:14919: using dbcs char 81,82 wchar 2260 bad wchar 30fb codepage 'ANSI/OEM
Japanese Shift-JIS'
msg.c:15071: Test failed: no messages: 0: the msg sequence is not complete:
expected 0000 - actual 0102
msg.c:15071: Failed sequence no messages:
msg.c:15071: 0: expected: nothing - actual: MsgCheckProc: 004B0136 0102 wp
0000ff1d lp 00000000 (flags 19)
msg.c:15073: Test failed: Unicode WM_CHAR: 0: the msg sequence is not complete:
expected 0102 - actual 0000
msg.c:15073: Failed sequence Unicode WM_CHAR:
msg.c:15073: 0: expected: msg 0102 - actual: nothing
msg.c:15075: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam
0x2260 got 0xff42
msg.c:15075: Failed sequence Unicode WM_CHAR:
msg.c:15075: 0: expected: msg 0102 - actual: MsgCheckProc: 004B0136 0102 wp
0000ff42 lp 00000000 (flags 19)
For the Chinese locale:
msg.c:14919: using dbcs char 81,80 wchar 4e90 bad wchar 003f codepage 'ANSI/OEM
Simplified Chinese GBK'
msg.c:15071: Test failed: no messages: 0: the msg sequence is not complete:
expected 0000 - actual 0102
msg.c:15071: Failed sequence no messages:
msg.c:15071: 0: expected: nothing - actual: MsgCheckProc: 004B0136 0102 wp
00004e96 lp 00000000 (flags 19)
msg.c:15073: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam
0x4e90 got 0x20ac
msg.c:15073: Failed sequence Unicode WM_CHAR:
msg.c:15073: 0: expected: msg 0102 - actual: MsgCheckProc: 004B0136 0102 wp
000020ac lp 00000000 (flags 19)
msg.c:15075: Test failed: Unicode WM_CHAR: 0: in msg 0x0102 expecting wParam
0x4e90 got 0x20ac
msg.c:15075: Failed sequence Unicode WM_CHAR:
msg.c:15075: 0: expected: msg 0102 - actual: MsgCheckProc: 004B0136 0102 wp
000020ac lp 00000000 (flags 19)
https://test.winehq.org/data/patterns.html#user32:msg
A bisect shows that the failures started with the following commit:
commit d42888f07c6e3e491c99bb5c8b62b568264e990c
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Mon Apr 4 16:58:21 2022 +0200
user32: Use NtUserMessageCall for SendMessageA implementation.
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Huw Davies <huw(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=51457
Bug ID: 51457
Summary: The 32-bit version:install fails in 64-bit
wineprefixes
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: version
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The 32-bit version:install fails in 64-bit wineprefixes:
https://test.winehq.org/data/patterns.html#version:install
install.c:250: Test failed: Wrong return value got 0 expected VFF_CURNEDEST set
install.c:255: Test failed: Wrong return value got 0 expected VFF_CURNEDEST set
install.c:260: Test failed: Wrong return value got 0 expected VFF_CURNEDEST set
All three failing tests query regedit.exe which is installed in two locations
in Wine:
windows/regedit.exe
windows/syswow64/regedit.exe
The failure happens because CreateFileA("C:\windows\system32\regedit.exe")
succeeds despite that file not actually being present (see file_existsA() in
dlls/kernelbase/version.c).
So either this is a WoW32 file remapping issue, or this is not the right way to
check for this 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=36681
Bug ID: 36681
Summary: ws2_32/tests/sock.c fails on gentoo without IPX
support
Product: Wine
Version: 1.7.19
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Created attachment 48725
--> https://bugs.winehq.org/attachment.cgi?id=48725
+winsock,+tid,+seh
../../../tools/runtest -q -P wine -T ../../.. -M ws2_32.dll -p
ws2_32_test.exe.so sock && touch sock.ok
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0
fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0xffffffff>
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0
fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x0000dead>
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0
fixme:winsock:convert_proto_w2u unhandled Windows socket protocol 57005
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 57005
err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this
requires special permissions.
sock.c:2224: Tests skipped: SOCK_RAW is not supported
sock.c:2270: Test failed: Expected 10047, received 10043
sock.c:2271: Tests skipped: IPX is not supported
+winsock attached
Linux aw25 3.13.3-gentoo-devlight-1 #1 SMP Thu Feb 20 00:10:55 Local time zone
must be set--see zic x86_64 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz
GenuineIntel GNU/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=53240
Bug ID: 53240
Summary: dinput:device8 - test_sys_mouse() has some rare
failures on the TestBot VMs
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:device8 - test_sys_mouse() has some rare failures on the TestBot VMs.
They can take two forms:
device8.c:1988: Test failed: 0x700: Acquire returned 0x80070005
device8.c:1997: Test failed: 0x700: WaitForSingleObject returned 0x102
device8.c:2002: Test failed: 0x700: got count 0
device8.c:2006: Test failed: 0x700: WaitForSingleObject returned 0x102
device8.c:2009: Test failed: 0x700: Unacquire returned 0x1
device8.c:2013: Test failed: 0x700: got count 0
device8.c:2016: Test failed: 0x700: Acquire returned 0x80070005
device8.c:2025: Test failed: 0x700: WaitForSingleObject returned 0x102
device8.c:2028: Test failed: 0x700: Unacquire returned 0x1
device8.c:2031: Test failed: 0x700: Acquire returned 0x80070005
device8.c:2035: Test failed: 0x700: got count 0
device8.c:2044: Test failed: 0x700: WaitForSingleObject returned 0x102
device8.c:2050: Test failed: 0x700: WaitForSingleObject returned 0x102
device8.c:2050: Test failed: 0x700: WaitForSingleObject returned 0x102
device8.c:2059: Test failed: 0x700: got count 0
or
device8.c:1988: Test failed: 0x800: Acquire returned 0x80070005
device8.c:1997: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:2001: Test failed: 0x800: GetDeviceData returned 0x8007000c
device8.c:2006: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:2009: Test failed: 0x800: Unacquire returned 0x1
device8.c:2016: Test failed: 0x800: Acquire returned 0x80070005
device8.c:2025: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:2028: Test failed: 0x800: Unacquire returned 0x1
device8.c:2031: Test failed: 0x800: Acquire returned 0x80070005
device8.c:2034: Test failed: 0x800: GetDeviceData returned 0x8007000c
device8.c:2044: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:2050: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:2050: Test failed: 0x800: WaitForSingleObject returned 0x102
device8.c:2055: Test failed: 0x800: GetDeviceData returned 0x8007000c
device8.c:2058: Test failed: 0x800: GetDeviceData returned 0x8007000c
https://test.winehq.org/data/patterns.html#dinput:device8
So far they have only happened on the Debian 11 VMs and the first known
instance was on 2022-06-14.
--
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=28290
Summary: shell32/shelllink.ok test flaky
Product: Wine
Version: 1.3.27
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
When running with WINEDEBUG=warn+heap (on my 32 bit i7 natty box
running in low power mode, fwiw), twice I've hit the error
../../../tools/runtest -q -P wine -M shell32.dll -T ../../.. -p
shell32_test.exe.so shelllink.c && touch shelllink.ok
shelllink.c:728: Test failed: save failed (0x80070020)
shelllink.c:728: Test failed: got 0x00000001
shelllink.c:728: Test failed: Didn't expect NULL
shelllink.c:474: Test failed: GetCurFile fails on shell32 < 5.0
shelllink.c:732: Test failed: GetDescription returned 'command on path' instead
of 'command on path without .exe'
This test keeps overwriting the same file with new data, iirc.
The previous thing it wrote was "command on path", so it looks
like the immediately previous testcase sometimes leaves a reference dangling?
I think 0x80070020 is "sharing violation".
--
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=50618
Bug ID: 50618
Summary: FoxPro for Windows 2.6a fails to start
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: JSladek(a)juno.com
Distribution: ---
Created attachment 69308
--> https://bugs.winehq.org/attachment.cgi?id=69308
Terminal output with both start conditions
Any attempt to start foxprow.exe with or without an appended program script
results in a program crash. Attached are copies of terminal output for both
types or foxprow start.
--
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.