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.
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.