https://bugs.winehq.org/show_bug.cgi?id=53214
Bug ID: 53214
Summary: d3d11:d3d11 - test_negative_viewports() fails in the
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: ---
d3d11:d3d11 - test_negative_viewports() fails in the TestBot VMs:
d3d11.c:28330: Test succeeded inside todo block: Got 0xffffffff, expected
0xffffffff at (640, 480, 1), sub-resource 0.
d3d11.c:28339: Test succeeded inside todo block: Got 0xffffffff, expected
0xffffffff at (640, 480, 1), sub-resource 0.
d3d11.c:28330: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
d3d11.c:28339: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
d3d11.c:28330: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
d3d11.c:28339: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Happen on Debian Testing + QXL + multi-monitor
So they seems to be related to the VMs QXL GPU.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=53215
Bug ID: 53215
Summary: d3d11:d3d11 - test_fractional_viewports() fails in the
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: ---
d3d11:d3d11 - test_fractional_viewports() fails in the TestBot VMs:
d3d11.c:28276: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001},
expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001.
d3d11.c:28276: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001},
expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002.
d3d11.c:28276: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001},
expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001.
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Happen on Debian Testing + QXL + multi-monitor
So they seems to be related to the VMs QXL GPU.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=53204
Bug ID: 53204
Summary: shell32:autocomplete - test_custom_source() sometimes
gets DropDown failures on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:autocomplete - test_custom_source() sometimes gets DropDown failures on
Windows:
autocomplete.c:778: Test failed: AutoComplete DropDown should be visible
autocomplete.c:788: Test failed: AutoComplete DropDown should be hidden
https://test.winehq.org/data/patterns.html#shell32:autocomplete
The second failure is not always present.
They only happen on Windows 10.
--
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=53203
Bug ID: 53203
Summary: shell32:autocomplete - test_aclist_expand() sometimes
fails on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:autocomplete - test_aclist_expand() sometimes fails on Windows:
autocomplete.c:534: Test failed: Expected 3 expansions, got 2
autocomplete.c:535: Test failed: Expected L"test\\foo\\bar\\baz_bbq\\", got
L"test\\foo\\bar\\"
autocomplete.c:536: Test failed: Expected 3 resets, got 2
autocomplete.c:541: Test failed: Expected 4 expansions, got 3
autocomplete.c:543: Test failed: Expected 4 resets, got 3
autocomplete.c:547: Test failed: Expected 4 expansions, got 3
autocomplete.c:548: Test failed: Expected 5 resets, got 4
autocomplete.c:553: Test failed: Expected 5 expansions, got 4
autocomplete.c:555: Test failed: Expected 6 resets, got 5
autocomplete.c:560: Test failed: Expected 6 expansions, got 5
autocomplete.c:562: Test failed: Expected 7 resets, got 6
https://test.winehq.org/data/patterns.html#shell32:autocomplete
These failures have been seen on Windows 10 1809 and 21H1.
The w8adm VM also got pretty similar failures once:
autocomplete.c:541: Test failed: Expected 4 expansions, got 3
autocomplete.c:542: Test failed: Expected L"test\\", got
L"test\\foo\\bar\\baz_bbq\\"
autocomplete.c:543: Test failed: Expected 4 resets, got 3
autocomplete.c:547: Test failed: Expected 4 expansions, got 3
autocomplete.c:548: Test failed: Expected 5 resets, got 4
autocomplete.c:553: Test failed: Expected 5 expansions, got 4
autocomplete.c:555: Test failed: Expected 6 resets, got 5
autocomplete.c:560: Test failed: Expected 6 expansions, got 5
autocomplete.c:562: Test failed: Expected 7 resets, got 6
--
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=32083
Bug #: 32083
Summary: Diablo III: Missing logo on startup
Product: Wine
Version: 1.5.16
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sworddragon2(a)aol.com
Classification: Unclassified
On starting Diablo III the logo before the game starts is transparent. If I'm
going with the mouse over it the cursor will be hidden.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35213
Bug ID: 35213
Summary: Kane & Lynch: Dead Men demo needs native d3dx9_31
Product: Wine
Version: 1.7.9
Hardware: x86
URL: http://www.gamefront.com/files/9394790/Kane___Lynch__D
ead_Men_Demo
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
First d3dx9_36 should be installed. Demo crashes with
fixme:d3dx:D3DXCreateEffectEx (0x20f000, 0x1e71cb58, 45008, (nil), (nil),
(nil), 0x10900, 0x1685a8, 0x1a99cf4, 0x1a99cec): semi-stub
after the same issue as for bug 35137, but this time should be d3dx9_31.
--
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=51158
Bug ID: 51158
Summary: advapi32:lsa fails in French on Windows 2004
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
advapi32:lsa fails in French on Windows 2004 because the name of the 'Everyone'
group does not seem to be translated anymore:
lsa.c:407: Test failed: expected L"Tout le monde", got L"Everyone"
That's a bit surprising. Maybe the Windows translation was slightly out of
date?
* This should be checked on Windows 2009 but we don't have a test configuration
for it.
* The test also has a translation for German but we don't have a test
configuration for German. There should really be one so we can validate the
test.
Once the results for German and Windows 2009 are known the test can be updated.
--
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=48108
Bug ID: 48108
Summary: kernel32:comm - QEmu's serial baud rate emulation is
broken
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
kernel32:comm got a failure when running on Wine on the TestBot VM:
comm.c:932: Test failed: OutQueue should not be empty
This happens in test_waittxempty():
// Open the serial device
hcom = test_OpenComm(TRUE);
// Here it is already set to 150 bps because that's how a
// previous test left it
...
// Write 17 bytes in overlaped mode.
// At 150 bauds this should take at least 900 ms
res = WriteFile(hcom, tbuf, sizeof(tbuf), &bytes, &ovl_write);
// Leaving us plenty of time to get to
ClearCommError(hcom, &errors, &stat);
...
// And here we expect the serial device to still have data to send.
// But because QEmu sends the data at > 400 kbps this often fails
ok(stat.cbOutQue != 0, "OutQueue should not be empty\n");
That QEmu does not enforce the set baud rate can also be verified from the
command line:
# stty -F /dev/ttyS0
speed 9600 baud; line = 0;
-brkint -imaxbel
# dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000
10000+0 records in
10000+0 records out
10000 bytes (10 kB, 9.8 KiB) copied, 0.224432 s, 44.6 kB/s
# stty -F /dev/ttyS0 300
# stty -F /dev/ttyS0
speed 300 baud; line = 0;
-brkint -imaxbel
# dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000
10000+0 records in
10000+0 records out
10000 bytes (10 kB, 9.8 KiB) copied, 0.679127 s, 14.7 kB/s
Back to the kernel32:comm failure:
* It did not happen for a long time and started happening on the debian10 VM on
2019-10-03. That corresponds to the time I added the winetest user to the
dialout group, thus giving it access to /dev/ttyS0.
* The same issue happens in the Windows VMs, but the ok() call has a broken()
clause which hides the issue there.
So:
1. The bug needs to be reported to QEmu.
2. See why speeds below 9600 bps are not allowed.
3. We may want a better check for this issue: directly check that the baud rate
is respected. This would allow us to skip tests that depend on the baud rate
and ditch the broken() clause.
4. If the above does not work out the serial device should be removed from the
Wine QEmu VMs.
--
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=52804
Bug ID: 52804
Summary: Crash when save settings in KaiNote
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matiasmoviegg(a)gmail.com
Distribution: ---
Created attachment 72181
--> https://bugs.winehq.org/attachment.cgi?id=72181
backtrace
Problem with KaiNote
Link for stable https://github.com/bjakja/Kainote/releases
Link for Beta (log from this version)
https://drive.google.com/uc?id=1ECqsrLo5d1jPoz-FKvJrS0279YeTKrmS&export=dow…
Go to File->Settings
Click OK
Click on random place in program
Program Crash
Testing on virtual machine with Xubuntu 21.10 (adding
"LIBGL_ALWAYS_SOFTWARE=1") and Laptop (i5-2520m) with Linux Mint 20.3
--
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=53194
Bug ID: 53194
Summary: d3d9:device - test_cursor_pos() is sometimes missing a
MOUSEMOVE on Windows 10 1809+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d9:device - test_cursor_pos() is sometimes missing a MOUSEMOVE on Windows 10
1809+:
device.c:5296: Test failed: Didn't receive MOUSEMOVE 0 (50, 50).
https://test.winehq.org/data/patterns.html#d3d9:device
These missing WM_MOUSEMOVE issues seem to be known to some extent, but not
quite understood:
https://gitlab.winehq.org/wine/wine/-/blob/1a3217393e2e6226da0f4024d4d384de…
--
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.