https://bugs.winehq.org/show_bug.cgi?id=53282
Bug ID: 53282
Summary: d3d9:d3d9ex - test_wndproc() is sometimes missing a
WM_DISPLAYCHANGE message in Wine
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: ---
d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_DISPLAYCHANGE message in
Wine:
d3d9ex.c:3115: Test failed: Expected message 0x7e for window 0x1, but didn't
receive it, i=0.
(also happens with i=1)
https://test.winehq.org/data/patterns.html#d3d9:d3d9ex
This failure is rare enough 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=53280
Bug ID: 53280
Summary: ddraw:ddraw1 sometimes crashes on 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: ---
ddraw:ddraw1 sometimes crashes on the TestBot VMs:
The crash is either an EXCEPTION_WINE_ASSERTION:
Unhandled exception: assertion failed in 32-bit code (0xf7f1e559).
[...]
Test failed: crash (80000101)
or a plain NULL dereference:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x70ba8945).
https://test.winehq.org/data/patterns.html#ddraw:ddraw1
The crashes only happen with 32-bit code.
Also the crashes started when the debian11 VM was updated and moved to the gpu1
VM host (see also bug 53235).
--
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=53279
Bug ID: 53279
Summary: World Of Warcraft (BCC): crashes on start on FreeBSD.
Product: Wine
Version: 7.7
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Wolffbsd(a)outlook.dk
Created attachment 72646
--> https://bugs.winehq.org/attachment.cgi?id=72646
Shows wine logs when running TBC.
os:FreeBSD <hostname> 13.1-RELEASE FreeBSD 13.1-RELEASE
releng/13.1-n250148-fc952ac2212 GENERIC amd64
drivers: https://www.freshports.org/x11/nvidia-driver/ (latest)
Running -d3d11 argument, dxvk 1.10.1, and wine-devel-7.7 from latest repo on
freebsd (https://www.freshports.org/emulators/wine-devel).
Both World of Warcraft TBC and classic Era crash.
TBC on start, a few images in, gives an ACCESS VIOLATION error. no more
specific information on the error is given on battle.net or the blizzard
forums, but it seems most people having same error code is due to antivirus
interfering (on windows that is).
I tried running without dxvk on opengl, also on a fresh .wine prefix, on vkd3d
all with no success and same errors.
TBCLOG attachment has a log of wine running.
first bug report I ever make, please do tell if I am being unclear, or if I did
a mistake.
--
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=53278
Bug ID: 53278
Summary: schedsvc:rpcapi once failed to release the RPC handle
on Windows
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
schedsvc:rpcapi once failed to release the RPC handle on Windows:
rpcapi.c:514: Test failed: expected S_OK, got 0x80070091
https://test.winehq.org/data/patterns.html#schedsvc:rpcapi
Where 0x80070091 == HRESULT_FROM_WIN32(ERROR_PATH_BUSY).
There was no other failure in that 2022-06-24 w10pro64-ar run.
It looks like there was still some operation pending that caused the final
RpcBindingFree() to fail. So maybe some sort of a race condition?
In another run a pair of SchRpcDelete() calls much earlier in the test failed
with the same error (2022-06-06 w10pro64-fr):
rpcapi.c:234: Test failed: expected S_OK, got 0x80070091
rpcapi.c:236: Test failed: expected S_OK, got 0x80070091
rpcapi.c:242: Test failed: expected ERROR_FILE_NOT_FOUND, got 0
rpcapi.c:243: Test failed: expected 0, got 1
rpcapi.c:244: Test failed: expected 0, got 1
rpcapi.c:245: Test failed: expected NULL, got 0000000000735EF0
rpcapi.c:248: Test failed: expected S_OK, got 0x800700b7
rpcapi.c:255: Test failed: expected 0, got 1
rpcapi.c:256: Test failed: expected 0, got 1
rpcapi.c:257: Test failed: expected NULL, got 00000000007358F0
rpcapi.c:260: Test failed: expected S_OK, got 0x800700b7
Note: The HRESULT_FROM_WIN32(ERROR_ALREADY_EXISTS) == 0x800700b7 errors are
probably caused by the initial SchRpcDelete() failures.
--
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=53193
Bug ID: 53193
Summary: d3d9:device - test_window_position() fails randomly in
Wine
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: ---
d3d9:device - test_window_position() fails randomly in Wine.
For instance:
device.c:14648: Test failed: Adapter 0: Expect window rect (0,0)-(1024,768),
got (4,14)-(644,494).
or
device.c:14648: Test failed: Adapter 0: Expect window rect (0,0)-(1024,768),
got (4,23)-(644,503).
or
device.c:14648: Test failed: Adapter 1: Expect window rect (1024,0)-(2048,737),
got (4,14)-(644,494).
or
device.c:14714: Test failed: Adapter 1: Expect window rect (1024,0)-(2048,737),
got (0,0)-(1024,737).
https://test.winehq.org/data/patterns.html#d3d9:device
Sometimes one can get failures for both adapter 0 and 1.
It is also not limited to multi-monitor configurations. For instance
fgtb-debian11 which is a single monitor configuration still gets the adapter 0
failure from time to time.
--
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=51976
Bug ID: 51976
Summary: The Elder Scrolls Online crashes at startup since it
auto-updated to v7.2.5 on Nov 1 2021
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 70965
--> https://bugs.winehq.org/attachment.cgi?id=70965
default terminal output (wine 6.20)
Hello,
After upgrading the game The Elder Scrolls Online to v7.2.5 (Deadlands & Update
32) on Nov 1, I can no longer start the application.
I was using Wine 6.17 at the time (had no issue with it before the game update)
and upgraded to 6.19, then 6.20, and got the same result.
The launcher works fine, but as soon as I click the PLAY button, a wine debug
dialog pops-up about a crash in the game client (eso64.exe - this is a 64bit
app).
The patch notes of the game speaks of changes in Nvidia DLSS & DLAA and
Multithreaded Rendering, but a +relay log shows that the crash occurs right
after a call to BluetoothFindFirstRadio(), in the same thread. I don't recall
seeing that function before so that may be an unmentioned change to the
application, or it may have nothing to do with the crash; I don't know (yet).
https://forums.elderscrollsonline.com/en/discussion/590109/pc-mac-patch-not…
Regards.
--
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=53267
Bug ID: 53267
Summary: user32:win - test_mouse_input() fails on Windows 10
21H1+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:win - test_mouse_input() fails on Windows 10 21H1+:
win.c:4549: Test failed: hwnd 000401CA/000401CA message 0204
win.c:4554: Test failed: hwnd 000401CA/000401CA message 0205
win.c:4559: Test failed: hwnd 000401CA/000401CA message 0206
win.c:4564: Test failed: hwnd 000401CA/000401CA message 0205
win.c:4580: Test failed: hwnd 002D039C/002D039C message 0204
win.c:4584: Test failed: hwnd 002D039C/002D039C message 0205
win.c:4593: Test failed: hwnd 000401CA/000401CA message 0204
win.c:4596: Test failed: hwnd 000401CA/000401CA message 0205
win.c:4629: Test failed: hwnd 00F802E8/00F802E8 message 00a4
win.c:4635: Test failed: hwnd 00F802E8/00F802E8 message 00a5
win.c:4642: Test failed: hwnd 00F802E8/00F802E8 message 0206
win.c:4644: Test failed: wparam 2
win.c:4655: Test failed: hwnd 00F802E8/00F802E8 message 0205
https://test.winehq.org/data/patterns.html#user32:win
This is quite similar to the failures in the Korean locale (bug 51395).
--
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=53263
Bug ID: 53263
Summary: dxgi:dxgi - test_swapchain_parameters() sometimes
crashes on Windows 8
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
dxgi:dxgi - test_swapchain_parameters() sometimes crashes on Windows 8:
dxgi.c:4487: Test failed: Got unexpected hr 0x8007000e, test 41.
dxgi.c:4487: Test failed: Got unexpected hr 0x8007000e, test 42.
dxgi.c:4487: Test failed: Got unexpected hr 0x8007000e, test 43.
dxgi.c:4639: Test failed: Got unexpected hr 0x8007000e.
dxgi.c:4639: this is the last test seen before the exception
0878:dxgi: unhandled exception c0000005 at 000000000042017E
https://test.winehq.org/data/patterns.html#dxgi:dxgi
0x8007000e == E_OUTOFMEMORY
This is known to have happened once on 2022-06-24 on w864.
--
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=53261
Bug ID: 53261
Summary: kernel32:module - test_LoadLibraryEx_search_flags()
sometimes crashes on Windows
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:module - test_LoadLibraryEx_search_flags() crashes on Windows.
On Windows 8 the traces show:
module.c:679: this is the last test seen before the exception
05d4:module: unhandled exception c0000005 at 76FC72F4
where line 679 is (see 561a5b8f84db):
679 ok( !lstrcmpiA( path, buf ), "%u: wrong module %s expected %s\n", j, path,
buf );
https://test.winehq.org/data/patterns.html#kernel32:module
But the crash is more easily reproducible on Windows 10 1607 and adding traces
there point to the following line as the location of the crash:
673 mod = LoadLibraryExA( "winetestdll.dll", 0, LOAD_LIBRARY_SEARCH_USER_DIRS
);
This is incompatible with the Windows 8 traces :-( However this crash seems to
be caused by memory corruption so it's possible the symptoms are a bit
different depending on the Windows version.
Furthermore the crash still happens on Windows 10 1607 even if all the others
test_xxx() functions are commented out in 'main'. Note however that the crash
is somewhat random so multiple (10+) tries can be needed to confirm it.
Finally this crash has only been seen on:
* Windows 8: w8, w8adm
* Windows 10 1507: w1064v1507
* Windows 10 1607: w1064v1607 (mostly 32-bit in WineTest results but mostly
64-bit for standalone tests!)
* Windows 10 1709: cw-gtx560 and cw-rx460 but no VM
--
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=50227
Bug ID: 50227
Summary: Logos 8 indexer crashes
Product: Wine
Version: 5.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galanlama(a)gmail.com
Distribution: ---
Created attachment 68735
--> https://bugs.winehq.org/attachment.cgi?id=68735
Backtrace produced by the wine debugger.
After opening Logos, indexer crashes after a few seconds. Same result by
running indexer.exe directly.
--
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=53257
Bug ID: 53257
Summary: Emacs 28.1 is unusable
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: EmilySeville7cf(a)gmail.com
Distribution: ---
Created attachment 72636
--> https://bugs.winehq.org/attachment.cgi?id=72636
screenshot of console emacs
I install Emacs 28.1 from here
(http://mirror.tochlab.net/pub/gnu/emacs/windows/emacs-28/)
emacs-28.1-installer.exe and run it via "C:\Program
Files\Emacs\emacs-28.1\bin\runemacs.exe"
".
When I use GUI version of Emacs it's window is moved to the left upper corner
when I press any button. Workaround: maximize window size and use Emacs.
When I use console Emacs version (emacs -nw) from wine cmd I can do nothing at
all. Any Emacs shortcut breaks interface. For instance I've tried use "Ctrl+N"
and obtain result on the screenshot.
--
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=15505
Summary: STM_SETIMAGE does not handle bitmaps with alpha
correctly
Product: Wine
Version: 1.1.5
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
In XP, STM_SETIMAGE makes a copy of bitmaps with alpha, which allows
applications to delete the bitmaps they passed in. Many programmers expect this
as the default behavior, since they don't test on older Windows platforms.
Our STM_SETIMAGE implementation still follows the pre-XP behavior, which may
cause rendering problems for apps that use STM_SETIMAGE extensively.
I don't have a minimal test case just yet...
--
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=4123
temp82(a)luukku.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |temp82(a)luukku.com
--- Comment #14 from temp82(a)luukku.com ---
still valid wine 7.11.
--
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=53191
Bug ID: 53191
Summary: Dualsense controller with WINE is not on-par with
Steam Input
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gab.pulcio(a)gmail.com
Distribution: ---
Latest Steam beta update has the following enhancement in particular: improved
vibration on Dualsense controller with updated firmware, or something like
that.
Now, if I run a game with Steam, the Dualsense has the improved basic rumble
support, which as far as I know, it's implemented in the firmware but it's
improved.
Running games without Steam leaves me with the super aggressive vibration, it's
always on maximum, without any variation, a lot different that the one present
on Steam Input API or something like that.
Is there a way to work the problem? Something like: actually make everything
global and not local by relying on a bugged piece of software like Steam is?
--
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=53152
Bug ID: 53152
Summary: LarkSuite: Unhandled exception: page fault on read
access to 0x00000008 in 32-bit code
Product: Wine
Version: 7.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: simon(a)kingstonwireless.com
Distribution: ---
Created attachment 72585
--> https://bugs.winehq.org/attachment.cgi?id=72585
Backtrace
LarkSuite (Lark) is a Slack-like collaboration suite that incorporates email,
messaging, calendar, video calls, etc and is quite popular with Chinese
companies. The installer can be downloaded from
https://www.larksuite.com/download (Windows, macOS, iOS and Android versions
are available there).
The Lark installer appears to run fine but when the actual suite tries to load
up, a page fault error is given.
--
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=53255
Bug ID: 53255
Summary: d3d11:d3d11 sometimes crashes in test_generate_mips()
on Windows 7
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
d3d11:d3d11 sometimes crashes in test_generate_mips() on Windows 7:
d3d11.c:30128: Tests skipped: Skipping test with DXGI_FORMAT_R8G8B8A8_UINT on
WARP.
d3d11.c:30128: Tests skipped: Skipping test with DXGI_FORMAT_R8G8B8A8_UINT on
WARP.
0d28:d3d11: unhandled exception c0000005 at 7FF9615D
https://test.winehq.org/data/patterns.html#d3d11:d3d11
Notice that a normal run has 4 of these skip messages instead of 2 which
suggests the crash happens in test_generate_mips().
There are two known instances of this crash:
* 2022-05-03 on w7u-2qxl
* 2022-06-22 on w7u-pt-PT
This makes this a pretty rare failure which can 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=53253
Bug ID: 53253
Summary: urlmon:url sometimes fails to create index.html on
Windows
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 sometimes fails to create index.html on Windows:
url.c:4073: bind to an object of not registered MIME type...
url.c:3774: Test failed: CreateFile failed
url.c:4078: file test (no callback)...
...
url.c:4184: emulated test reporting result in read...
url.c:4187: file test...
url.c:4190: file test (to file)...
url.c:4193: file test (to object)...
url.c:1534: Test failed: unexpected call QueryInterface_IWindowForBindingUI
url.c:1416: Test failed: unexpected call QueryService_IWindowForBindingUI
url.c:1342: Test failed: unexpected call GetWindow_ICodeInstall
url.c:1846: Test failed: binding failed: 80040154, expected 00000000
url.c:3524: Test failed: expected Obj_OnProgress_CLASSIDAVAILABLE
url.c:3533: Test failed: expected OnObjectAvailable
https://test.winehq.org/data/patterns.html#urlmon:url
These failures ahppen on Windows 7 to Windows 10 21H1 and are rare enough 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=53246
Bug ID: 53246
Summary: user32:sysparams - test_metrics_for_dpi() fails on
Windows 10 1709+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams - test_metrics_for_dpi() fails on Windows 10 1709+:
sysparams.c:4175: testing GetSystemMetrics with your current desktop settings
sysparams.c:3002: Test failed: 28: wrong value 136 vs 258
sysparams.c:3002: Test failed: 34: wrong value 136 vs 258
...
sysparams.c:2430: testing SPI_{GET,SET}DESKWALLPAPER
sysparams.c:3002: Test failed: 28: wrong value 136 vs 258
sysparams.c:3002: Test failed: 34: wrong value 136 vs 258
https://test.winehq.org/data/patterns.html#user32:sysparams
Where:
* 28 == SPI_SETMENUDROPALIGNMENT
* 34 == SPI_SETICONTITLELOGFONT
test_metrics_for_dpi() is actually called from multiple places and
unfortunately the traces make it hard to know which calls actually fail.
The first pair of failures probably come from:
trace("testing GetSystemMetrics with your current desktop settings\n");
test_GetSystemMetrics( );
test_metrics_for_dpi( 192 );
The source of the second set of failures is less clear but presumably from the
other test_metrics_for_dpi( 192 ) call in test_dpi_aware(). Some
winetest_push_context() would be a good addition here.
--
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=53245
Bug ID: 53245
Summary: user32:sysparams: test_SPI_SETNONCLIENTMETRICS() fails
on Windows 10 1709+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams: test_SPI_SETNONCLIENTMETRICS() fails on Windows 10 1709+:
sysparams.c:1488: testing SPI_{GET,SET}NONCLIENTMETRICS
sysparams.c:2823: Test failed: GetSystemMetrics(SM_CXSMICON): expected 16
actual 4
sysparams.c:2824: Test failed: GetSystemMetrics(SM_CYSMICON): expected 16
actual 4
https://test.winehq.org/data/patterns.html#user32:sysparams
The failure actually happens in test_GetSystemMetrics() which is called from
test_SPI_SETNONCLIENTMETRICS(). However there are 3 call locations and the
traces make it impossible to know which one fails which is another test bug in
its own right.
--
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=53244
Bug ID: 53244
Summary: user32:sysparams does not expect SPI_SETHANDEDNESS on
Windows 10 2004+
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:sysparams does not expect SPI_SETHANDEDNESS on Windows 10 2004+.
Furthermore that message arrives at slightly different times in the tests
leading to different failure messages:
sysparams.c:1202: testing SPI_{GET,SET}DOUBLECLKWIDTH
sysparams.c:241: Test failed: too many changes counter=1 last change=29
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 29
sysparams.c:1236: testing SPI_{GET,SET}DOUBLECLKHEIGHT
sysparams.c:1271: testing SPI_{GET,SET}DOUBLECLICKTIME
sysparams.c:1326: testing SPI_{GET,SET}MOUSEBUTTONSWAP
sysparams.c:241: Test failed: too many changes counter=1 last change=33
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:347: Test failed: Wrong value in registry: Control Panel\Mouse
SwapMouseButtons '1' instead of '0'
sysparams.c:1341: Test failed: SM_SWAPBUTTON: got 1 instead of 0
sysparams.c:1345: Test failed: SwapMouseButton does not return previous state
(really 1)
sysparams.c:1358: testing SPI_GETFASTTASKSWITCH
sysparams.c:1376: testing SPI_{GET,SET}DRAGFULLWINDOWS
sysparams.c:241: Test failed: too many changes counter=1 last change=37
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 33 expected 37
or
sysparams.c:1236: testing SPI_{GET,SET}DOUBLECLKHEIGHT
sysparams.c:241: Test failed: too many changes counter=1 last change=30
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 30
sysparams.c:1271: testing SPI_{GET,SET}DOUBLECLICKTIME
sysparams.c:241: Test failed: too many changes counter=1 last change=32
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 32
sysparams.c:1326: testing SPI_{GET,SET}MOUSEBUTTONSWAP
sysparams.c:241: Test failed: too many changes counter=1 last change=33
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:347: Test failed: Wrong value in registry: Control Panel\Mouse
SwapMouseButtons '1' instead of '0'
sysparams.c:1341: Test failed: SM_SWAPBUTTON: got 1 instead of 0
sysparams.c:1345: Test failed: SwapMouseButton does not return previous state
(really 1)
sysparams.c:1358: testing SPI_GETFASTTASKSWITCH
sysparams.c:1376: testing SPI_{GET,SET}DRAGFULLWINDOWS
sysparams.c:241: Test failed: too many changes counter=1 last change=37
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 33 expected 37
or
sysparams.c:1236: testing SPI_{GET,SET}DOUBLECLKHEIGHT
sysparams.c:241: Test failed: too many changes counter=1 last change=8229
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:1271: testing SPI_{GET,SET}DOUBLECLICKTIME
sysparams.c:241: Test failed: too many changes counter=1 last change=32
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 8229 expected 32
sysparams.c:1326: testing SPI_{GET,SET}MOUSEBUTTONSWAP
sysparams.c:241: Test failed: too many changes counter=1 last change=33
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:347: Test failed: Wrong value in registry: Control Panel\Mouse
SwapMouseButtons '1' instead of '0'
sysparams.c:1341: Test failed: SM_SWAPBUTTON: got 1 instead of 0
sysparams.c:1345: Test failed: SwapMouseButton does not return previous state
(really 1)
sysparams.c:1358: testing SPI_GETFASTTASKSWITCH
sysparams.c:1376: testing SPI_{GET,SET}DRAGFULLWINDOWS
sysparams.c:241: Test failed: too many changes counter=1 last change=37
sysparams.c:279: Test failed: Missed a message: change_counter=2
sysparams.c:282: Test failed: Wrong action got 33 expected 37
https://test.winehq.org/data/patterns.html#user32:sysparams
Where:
* 30 == SPI_SETDOUBLECLKHEIGHT
* 32 == SPI_SETDOUBLECLICKTIME
* 33 == SPI_SETMOUSEBUTTONSWAP
* 37 == SPI_SETDRAGFULLWINDOWS
* 8229 == SPI_SETHANDEDNESS
Some of these variants are less common than others due to timing so when they
happen they are likely to cause false positives.
Clearly SPI_SETHANDEDNESS is a new setting that was introduced in Windows 10
2004 and which the test should take into account.
Maybe it should receive special treatment like SPI_SETWORKAREA & co?
(Though we don't currently test SPI_SETHANDEDNESS)
--
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=53178
Bug ID: 53178
Summary: Mass Effect 3 Tweaks Mod Manager 7.0.7 does not launch
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: alt.ti-a8gprwn(a)yopmail.com
Distribution: ---
Created attachment 72623
--> https://bugs.winehq.org/attachment.cgi?id=72623
Terminal output
The latest version doesn't launch, however, the older ones do. This could be
due to the .NET 6 upgrade in the manager, process exits with a stack overflow
error, could be a duplicate of #51888. Attaching logs.
--
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=53125
Bug ID: 53125
Summary: diabloimmortal: invalid program stack in 64-bit code
Product: Wine
Version: 7.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: i.r.1783(a)gmx.net
Distribution: ---
Created attachment 72580
--> https://bugs.winehq.org/attachment.cgi?id=72580
lspci+backtrace
steps 2 reproduce
1. download current thumbleweed xfce live iso
https://download.opensuse.org/ports/aarch64/tumbleweed/iso/openSUSE-Tumblew…
2. download battle.net client
game info: https://eu.shop.battle.net/en-us/product/diablo-immortal?p=854533Battle.net Desktop App:
https://www.blizzard.com/en-us/download/confirmation?product=bnetdesk
3. additional things before installing Battle.net Desktop App:
sudo zypper in kernel-firmware-intel libdrm_intel1 libdrm_intel1-32bit
libvulkan1 libvulkan1-32bit libvulkan_intel libvulkan_intel-32bit
sudo sysctl dev.i915.perf_stream_paranoid=0
export WINEARCH=win64
export WINEPREFIX="/home/ich/.wine64"
export WINEDEBUG=-all
wineboot -i
4. wine Battle.net-Setup.exe
5. cd '/home/ich/Programme/Immortal/Diablo Immortal/Engine/Binaries/Win64/'
wine ./DiabloImmortal.exe
6. crash, see Diablo_Immortal_backtrace.txt
--
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=53117
Bug ID: 53117
Summary: USER32: Drop-list of combobox not closed when the user
clicks outside
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: carlo.bramix(a)libero.it
Distribution: ---
Created attachment 72571
--> https://bugs.winehq.org/attachment.cgi?id=72571
Open the drop list of the combobox.
Step to reproduce:
1) open an application that allows you to show a combobox, for example WINE
notepad.
2) then select from menu "File->Open" to display the open file dialog and press
the button to open the drop down list of the combobox (see attached image 1).
3) now, click on the title bar of the open file dialog and try to move it: the
drop down list will be still visible and completely disconnected from its
control (see attached image 2).
Here, I used the WINE notepad as example but the bug can be reproduced by all
applications with a combobox.
--
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=52919
Bug ID: 52919
Summary: Resident Evil 5 DVD shows
E_INVALIDARG:XLiveInitialize(&xii)
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BOBBLOG(a)protonmail.com
Distribution: ---
Created attachment 72299
--> https://bugs.winehq.org/attachment.cgi?id=72299
RE5-D3D
Resident Evil 5 DVD shows E_INVALIDARG:XLiveInitialize(&xii) when i launch the
game.
This was tested with wine-7.7 in a clean wine prefix. I'll attach +d3d log.
--
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=53192
Bug ID: 53192
Summary: FlexiPDF 3.0.3 crashes when moving window:
dlls/ntdll/unix/thread.c:1737:
ntdll_set_exception_jmp_buf: Assurance »!jmp ||
!ntdll_get_thread_data()->jmp_buf« not fulfilled
Product: Wine
Version: 7.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: postix(a)posteo.eu
Distribution: ---
Created attachment 72629
--> https://bugs.winehq.org/attachment.cgi?id=72629
Terminal output
### Issue
FlexiPDF 3.0.3 crashes when trying to move its window by dragging the titlebar.
### Download link
`https://www.softmaker.net/down/flexipdf2022.exe`
### System
Operating System: Fedora Linux 36
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Graphics Processor: AMD RENOIR
--
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=50103
François Gouget <fgouget(a)codeweavers.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |ABANDONED
CC| |fgouget(a)codeweavers.com
Status|NEEDINFO |RESOLVED
--- Comment #2 from François Gouget <fgouget(a)codeweavers.com> ---
No answer to a year-old request for information.
--
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=43347
Bug ID: 43347
Summary: valgrind shows an unintialized read in
dlls/iphlpapi/tests/iphlpapi.c
Product: Wine
Version: 2.12
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: iphlpapi
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
../../../tools/runtest -q -P wine -T ../../.. -M iphlpapi.dll -p
iphlpapi_test.exe.so iphlpapi && touch iphlpapi.ok
==10952== Syscall param ioctl(SIOCGIFINDEX) points to uninitialised byte(s)
==10952== at 0x4338F79: ioctl (syscall-template.S:84)
==10952== by 0x435916D: if_nametoindex (if_index.c:47)
==10952== by 0x4B25E43: getInterfaceIndexByName (ifenum.c:143)
==10952== by 0x4B2EC7E: IPHLP_if_nametoindex (iphlpapi_main.c:3233)
==10952== by 0x488198E: test_interface_identifier_conversion
(iphlpapi.c:1958)
==10952== by 0x48831AB: func_iphlpapi (iphlpapi.c:2230)
==10952== by 0x4884014: run_test (test.h:603)
==10952== by 0x4884465: main (test.h:687)
==10952== Address 0x4b0f8c0 is on thread 1's stack
==10952== in frame #1, created by if_nametoindex (if_index.c:35)
==10952== Uninitialised value was created by a stack allocation
==10952== at 0x4359141: if_nametoindex (if_index.c:41)
==10952==
--
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=53241
Bug ID: 53241
Summary: wtsapi32:wtsapi - test_WTSEnumerateProcessesW()
crashes if a process exits during the test?
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: wtsapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
wtsapi32:wtsapi - test_WTSEnumerateProcessesW() crashes if a process exits
during the test?
Here is the failure:
wtsapi.c:78: Test failed: failed to find pid 0x20e4
wtsapi.c:82: this is the last test seen before the exception
0618:wtsapi: unhandled exception c0000005 at 0000000000401848
https://test.winehq.org/data/patterns.html#wtsapi32:wtsapi
The crash happens when check_wts_process_info() dereferences the NULL pointer
returned by find_nt_process_info().
So presumably the test must check that some API does return information about
at least some processes but it seems allowances should be made for processes
exiting during the test.
--
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=53200
Bug ID: 53200
Summary: WET (a dotnet45 framework for web printing terminal):
black block covered the content. i can edit with
libreoffice draw. the content is there, but all
covered with black block.
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P1
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dejoebad(a)yahoo.com
Distribution: ---
WET (a dotnet45 framework for web printing terminal): black block covered the
content. i can edit with libreoffice draw. the content is there, but all
covered with black block.
https://www.instagram.com/p/Ce33e8vJ-n0
this is the output from windows and wine
https://www.instagram.com/p/CfBo3hVPd2d
this is what actually behind the black blocks. i'd print the file to pdf and
edit with libreoffice draw.
--
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=44337
Bug ID: 44337
Summary: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers)
in test_occlusion_query()
Product: Wine
Version: 3.0-rc5
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
with the following lines:
device.c:5915: Test failed: Got unexpected hr 0x1.
device.c:5919: Test failed: Got unexpected hr 0x1.
device.c:5920: Test failed: Got unexpected query result 0xffffffffffffffff.
It would be nice to fix this as this is currently the only D3D test failure on
the cw2 test machine.
--
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=48820
Bug ID: 48820
Summary: user32:win "unexpected 0x7fff message" Japanese
Windows 10 failures
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: major
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The TestBot's w1064v1809-zh_CN configuration runs the tests on Windows 10 1809
in a Chinese locale. This test configuration gets unique failures in
user32:win:
win.c:3852: Test failed: hwnd 007404D2 message 7fff
win.c:3858: Test failed: message 7fff available
win.c:3931: Test failed: hwnd 007404D2/0054050A message 7fff
win.c:3934: Test failed: hwnd 007404D2/0054050A message 7fff
Note how these messages are very similar to the IME messages in bug 48819.
However 0x7fff is a totally unknown message: all I can say about it is that
it's WM_APP-1. So maybe it's another IME system. Maybe not?
See: https://test.winehq.org/data/tests/user32:win.html
However note that quite often WineTest fails to submit its results to
test.winehq.org, typically because it times out. So you can more easily find
the latest failure by looking for the "32 bit WineTest: base VMs" jobs on the
TestBot.
Finally, three of these messages include the window handles which means they
are "always new". Because of this the TestBot will mistakenly attribute the
failure to any user32 patch submitted to wine-devel, which should cause them to
be rejected. So I bumped the priority on this bug.
--
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=53228
Bug ID: 53228
Summary: dxgi:dxgi - test_swapchain_window_styles() sometimes
fails on Windows 10
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
dxgi:dxgi - test_swapchain_window_styles() sometimes fails on Windows 10:
dxgi.c:6125: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100.
dxgi.c:6141: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100.
dxgi.c:6169: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100.
dxgi.c:6196: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100.
dxgi.c:6212: Test failed: Test 4: Got unexpected exstyle 0x108, expected 0x100.
https://test.winehq.org/data/patterns.html#dxgi:dxgi
This failure has been seen on Windows 10 1507 to 21H2.
Furthermore, because of the test's multi-threading it has an elevated risk of
causing false positives (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=53209
Bug ID: 53209
Summary: GTA San Andreas. Audio bug
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jon9097(a)gmail.com
Distribution: ---
When you rotate the camera around the character, the sound almost completely
goes from one speaker to the other and back again. I did not find anything
strange in the logs.
This problem has been in wine for as long as I can remember, no such thing on
windows. I wish that it was solved and the sound was distributed normally.
--
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=53173
Bug ID: 53173
Summary: user32:input - test_Input_mouse() randomly fails to
get the expected mouse button or hit-test messages
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:input - test_Input_mouse() randomly fails to get the expected mouse
button or hit-test messages:
input.c:3398: Test failed: expected WM_LBUTTONDOWN message
input.c:3399: Test failed: expected WM_LBUTTONUP message
input.c:3426: Test failed: expected WM_NCHITTEST message
input.c:3427: Test failed: expected WM_RBUTTONDOWN message
input.c:3428: Test failed: expected WM_RBUTTONUP message
input.c:3457: Test failed: expected WM_LBUTTONDOWN message
input.c:3458: Test failed: expected WM_LBUTTONUP message
input.c:3511: Test failed: expected loop with WM_NCHITTEST messages
input.c:3564: Test failed: expected WM_LBUTTONDOWN message
input.c:3565: Test failed: expected WM_LBUTTONUP message
https://test.winehq.org/data/patterns.html#user32:input
The failure list is always the same except for the first two which are not
always present.
This happened on w7u-2qxl, w86 and most Windows 10 1607+ test configurations up
to 21H2. So it's not a quirk of a specific Windows version.
--
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=53212
Bug ID: 53212
Summary: d3d11:d3d11 - test_clear_image_unordered_access_view()
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_clear_image_unordered_access_view() fails in the TestBot
VMs:
d3d11.c:16719: Test failed: Dim 0, Test 15: At layer 0, (0,0,0), expected
0x00c01001, got 0x00000000.
d3d11.c:16719: Test failed: Dim 1, Test 15: At layer 0, (0,0,0), expected
0x00c01001, got 0x00000000.
d3d11.c:16719: Test failed: Dim 2, Test 15: At layer 0, (0,0,0), expected
0x00c01001, got 0x00000000.
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures don't happen on my box which has an Intel graphics card instead
of QEmu's QXL graphics card.
Note also that these failures still happen on my debian11 VM which has a single
monitor instead of the TestBot VMs' multi-monitor setup.
So this seems to be related to the VMs QXL GPU.
Despite being systematic these failures someimes cause false positives because
of the test's multi-threading: sometimes these failures come before the
test_texture() failures (Test 60:), and most of the time they come after. The
order change causes the TestBot's diffing algorithm to consider them to be new
failures if they come in an order it has not seen before.
--
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=53148
Bug ID: 53148
Summary: mfplay:mfplay - test_media_item() has a rare crash on
Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mfplat
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
mfplay:mfplay - test_media_item() has a rare crash on Windows 8:
mfplay.c:295: Test failed: Unexpected hr 0xc00d3e85.
mfplay.c:295: this is the last test seen before the exception
0afc:mfplay: unhandled exception c0000005 at 0040121C
https://test.winehq.org/data/patterns.html#mfplay:mfplay
This looks like it is specific to the TestBot VMs: there is no record of this
failure happening on the cw-gtx560 or cw-rx460 machines. The failure rate is
about 6.8%.
--
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=53223
Bug ID: 53223
Summary: shell32:shlfileop - test_sh_path_prepare() fails in
the Japanese and Chinese locales 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:shlfileop - test_sh_path_prepare() fails in the Japanese and Chinese
locales in Wine:
shlfileop.c:2463: Test failed: Could not find unique multibyte representation
for directory name using default codepage.
https://test.winehq.org/data/patterns.html#shell32:shlfileop
Note that the conversion fails on Windows too which probably makes sense for
these locales. So the win_skip() should maybe be a regular skip() instead.
--
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=35765
Bug ID: 35765
Summary: gdi32:font / richedit:editor / msvcrt:locale /
msvcrt:string fails on newtb-w7u
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Keywords: source, testcase
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fracting(a)gmail.com
CC: fgouget(a)codeweavers.com
http://test.winehq.org/data/770213e16c6918728f69ea33545fafabd59dbc8e/win7_n…
It seems these tests are all related to locales, and they fail much more on
this machine than other machine.
SystemDefaultLCID 411
UserDefaultLCID 409
ThreadLocale 411
UserDefaultUILanguage 411
ThreadUILanguage 411
It doesn't happen frequently that we have a vm with different UserDefaultLCID
and SystemDefaultLCID. I'm not very sure if we want to support such a case, it
maybe useful in real world for some body. (I personally don't care too much
lol)
François, is there any chance to try:
1. set all LCIDs to 0x409 (Simplified Chinese)
2. set all LCIDs to 0x411 (Japanese)
Then reboot the vm, then resubmit the tests, to see if there is any
improvement?
Thanks for your great work! Everyone wants your patch/work :)
--
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=53221
Bug ID: 53221
Summary: user32:winstation - test_enumdesktops() sometimes
fails to open the desktop on Windows 7 & 8
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:winstation - test_enumdesktops() sometimes fails to open the desktop on
Windows 7 & 8:
winstation.c:411: desktop_callbackA called with argument WinSta0
winstation.c:411: desktop_callbackA called with argument winsta_test
winstation.c:420: open_desktop_callbackA called with argument new_desk
winstation.c:426: Test failed: Could not open desktop new_desk!
winstation.c:420: open_desktop_callbackA called with argument
rawinput_test_desktop
winstation.c:420: open_desktop_callbackA called with argument Default
winstation.c:420: open_desktop_callbackA called with argument Winlogon
winstation.c:452: Test failed: LastError is set to 00000002
winstation.c:411: desktop_callbackA called with argument rawinput_test_desktop
https://test.winehq.org/data/patterns.html#user32:winstation
These failures have been seen on w7u-adm, w7u-el, w8 and w8adm but the failure
rate is pretty low (<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=53219
Bug ID: 53219
Summary: winmm:mci - test_asyncWAVE() sometimes fails due to a
timing issue
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
winmm:mci - test_asyncWAVE() sometimes fails due to a timing issue:
mci.c:980: Test failed: 706ms is not in the expected 350-600ms range
https://test.winehq.org/data/patterns.html#winmm:mci
This only happened once on the TestBot but happens a bit more frequently on
fgtb-w10pro64 where the host is typically more busy.
--
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=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.