https://bugs.winehq.org/show_bug.cgi?id=37355
Bug ID: 37355
Summary: Tages Protection v5.x needs ntoskrnl
'MmMapLockedPagesSpecifyCache' implementation
Product: Wine
Version: 1.7.27
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
reported here: https://github.com/compholio/wine-compholio/issues/80
Michael Müller from FDS team:
--- quote ---
Sadly this is not enough to make the Tages copy protection happy. The issue you
are now running into is:
fixme:ntoskrnl:MmMapLockedPagesSpecifyCache (0x111988, 0, 1, (nil), 0, 32):
stub
The MmMapLockedPagesSpecifyCache command is used to map memory of a process
into the kernel, so that a kernel driver can write / read it. This is necessary
since the kernel does not share the same address space as the process. The
problem is that this command is a stub and always returns 0 as mapped address.
The Tages protection does not check for NULL pointers and tries to write to the
address resulting in:
wine: Unhandled page fault on write access to 0x00000000 at address 0x57fe27
(thread 0018), starting debugger...
The problem is that there is no way to properly implement this on Linux since
there is no way to simply map the memory of a different process if you are not
inside the kernel. Since wine is no kernel module it can only use memory of
different processes, when they explicitly create it as shared memory block.
Sadly you can not declare a memory block as shared after it was allocated, so
this does not help implementing this command.
Anyway in the case of the Tages protection we have some luck since it seems
like the process is paused (I think it was waiting for the response of the
DeviceIoControl function) while the memory is changed by the windows kernel
driver. This allows us to emulate the mapping of the memory by using
ReadProcessMemory and WriteProcessMemory. I wrote some hack to implement this,
but this only prevented the crash and made the application to exit silently. I
either made a mistake in my hack or there is still something else which
prevents it from working.
--- quote ---
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=55431
Bug ID: 55431
Summary: wine-staging to have same Component as wine
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
CC: austinenglish(a)gmail.com
Distribution: ---
Could wine-staging bugs have the same Component list as wine?
--
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=47996
Bug ID: 47996
Summary: Battlefield 2 - d3d:debug_d3dformat Unrecognized
0x4642564e - Unhandled exception
Product: Wine
Version: 4.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: consolelogger(a)rhyta.com
Distribution: ---
Created attachment 65519
--> https://bugs.winehq.org/attachment.cgi?id=65519
console log with WINEDEBUG=+loaddll
Ubuntu 19.10 - wine-mono-4.9.3.msi
Battlefield 2 crashes during startup.
Console log is attached.
I am happy to provide more details and do tests when asked to.
--
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=55416
Bug ID: 55416
Summary: psapi:psapi_main - check_QueryWorkingSetEx() sometimes
fails on Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - check_QueryWorkingSetEx() sometimes fails on Windows 10:
psapi_main.c:1165: Test failed: exe expected Valid=1 but got 0
psapi_main.c:1169: Test failed: exe expected Win32Protection=2 but got 0
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
This first happened on 2023-07-11 and there has been three instances so far:
* 2023-07-11 win22H2_fgtb-w10pro64-32
* 2023-07-19 win21H2_gitlab-win10-21h2-32
* 2023-08-04 win22H2_newtb-w1064-32
--
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=55426
Bug ID: 55426
Summary: user32:msg - test_swp_paint_region_on_show() sometimes
fails on w7u
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:msg - test_swp_paint_region_on_show() sometimes fails on w7u:
msg.c:9471: Test failed: GetRgnBox (on parent) returned 1
msg.c:9475: Test failed: parent update region: got (0,0)-(0,0), expected
(10,10)-(100,100)
msg.c:9508: Test failed: GetRgnBox (on parent) returned 1
msg.c:9512: Test failed: parent update region: got (0,0)-(0,0), expected
(20,20)-(120,120)
See https://test.winehq.org/data/patterns.html#user32:msg
This first happened on 2023-07-13 and has happened about once a week since,
always on w7u. In particular it does not happen on w7pro64 but then that VM
only runs 64-bit tests so maybe this is just 32-bit-specific.
* 2023-07-13 win7_newtb-w7u-pt-PT_1
* 2023-07-14 win7_newtb-w7u-de
* 2023-07-19 win7_newtb-w7u-es
* 2023-08-01 win7_newtb-w7u-2qxl
See also bug 55425 which is similar but happens in
test_swp_paint_region_on_extend_zerosize() and started one month earlier.
--
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=55425
Bug ID: 55425
Summary: user32:msg -
test_swp_paint_region_on_extend_zerosize() sometimes
fails on w7u
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:msg - test_swp_paint_region_on_extend_zerosize() sometimes fails on w7u:
msg.c:9569: Test failed: parent update region: got (10,10)-(100,58), expected
(10,10)-(100,100)
See https://test.winehq.org/data/patterns.html#user32:msg
This first happened on 2023-06-13 and has happened about twice a week since,
always on w7u. In particular it does not happen on w7pro64 but then that VM
only runs 64-bit tests so maybe this is just 32-bit-specific.
* 2023-06-13 win7_newtb-w7u-adm
* 2023-06-22 win7_newtb-w7u-2qxl
* 2023-06-23 win7_newtb-w7u
* 2023-06-26 win7_newtb-w7u-2qxl
* 2023-07-13 win7_newtb-w7u-2qxl_1
* 2023-07-19 win7_newtb-w7u-el
* 2023-08-01 win7_newtb-w7u-adm
* 2023-08-08 win7_newtb-w7u-adm
--
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=55381
Bug ID: 55381
Summary: installing synaptics fingerprint reader driver fails
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 74955
--> https://bugs.winehq.org/attachment.cgi?id=74955
log file trying to install synaptics fingerprint reader driver
Attached is the log file when trying to install the synaptics fingerprint
reader driver
https://download.lenovo.com/pccbbs/mobiles/nz3gf09w.exe
It seems to fail with this error:
012c:err:ntdll:NtQueryInformationToken Unhandled token information class 26
When selecting to "extract only" (and not install), this error is not shown.
The files are extracted in both cases, when selecting extract only, as well as
"install".
--
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=54095
Bug ID: 54095
Summary: quartz:filtermapper sometimes crashes on exit in Wine
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:filtermapper sometimes crashes on exit in Wine:
quartz:filtermapper start dlls/quartz/tests/filtermapper.c
0c18:filtermapper: 251 tests executed (0 marked as todo, 0 as flaky, 0
failures), 0 skipped.
quartz:filtermapper:0c18 done (-1073741819) in 0s 94B
See https://test.winehq.org/data/patterns.html#quartz:filtermapper
Where -1073741819 == 0xc0000005
The crash is pretty rare: one per month on average but there are some two
months stretches with no crash.
What's interesting is that the invalid memory access happens after the main
process has printed the 'test summary' line, which means the crash happened on
exit. So it must be caused by previous memory corruption.
Also MR!1703 got a timeout on exit which is probably the same underlying issue:
quartz:filtermapper start dlls/quartz/tests/filtermapper.c
0af0:filtermapper: 253 tests executed (0 marked as todo, 0 as flaky, 0
failures), 0 skipped.
quartz:filtermapper:0af0 done (258) in 120s 94B
--
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=54845
Bug ID: 54845
Summary: Fusion 360: key_import_pair unsupported key type
L"CAPIPRIVATEBLOB"
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: benjackson990(a)gmail.com
Distribution: ---
The recent update has changed the login process to allow for a Single Sign On,
but in the process seemingly used a encryption not supported in any version of
Wine that I'm aware of.
Can anyone please advise how I should go about resolving the following issue
```
0178:fixme:bcrypt:key_import_pair unsupported key type L"CAPIPRIVATEBLOB"
0178:fixme:bcrypt:get_key_property unsupported algorithm 9
```
--
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=53712
Bug ID: 53712
Summary: ole32:moniker is broken on Windows 7 in the GitLab
WineTest builds
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ole32:moniker is broken on Windows 7 in the GitLab WineTest builds:
moniker.c:2280: ACP is 1252
0a18:4þ": 5504 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0
skipped.
ole32:moniker:0a18 done (-1073740791) in 0s 115B
Test failed: crash (c0000409)
https://test.winehq.org/data/patterns.html#ole32:moniker
Where 0xc0000409 == STATUS_STACK_BUFFER_OVERRUN.
The failures started on 2022-07-26 which is when the WineTest builds switched
from the old build system to GitLab. A test with winetest-889fe64d9f2e.exe
(built on 2022-07-25) confirms that this test still succeeds when using
binaries from the old build system.
--
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=54545
Bug ID: 54545
Summary: ieframe:webbrowser test_WebBrowser() gets unexpected
OnFocus_FALSE calls on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ieframe
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ieframe:webbrowser - test_WebBrowser() gets unexpected OnFocus_FALSE calls on
Windows 7.
For instance:
webbrowser.c:1202: Test failed: unexpected call OnFocus_FALSE
and sometimes a second failure happens later:
webbrowser.c:3434: Test failed: expected OnFocus_FALSE
See https://test.winehq.org/data/patterns.html#ieframe:webbrowser
The unexpected calls don't happen during a specific test_WebBrowser() call.
Up to 2022-11-04 this failure was only happening on w1064v1709 when that
stopped. Then on 2023-01-25 is started happening about 3 times per month on the
w7u* TestBot 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=55430
Bug ID: 55430
Summary: ddraw:ddraw1, ddraw:ddraw2 & ddraw:ddraw7 -
test_coop_level_mode_set() is sometimes missing
WM_DISPLAYCHANGE on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:ddraw1, ddraw:ddraw2 & ddraw:ddraw7 - test_coop_level_mode_set() is
sometimes missing WM_DISPLAYCHANGE on Windows:
ddraw1.c:3141: Test failed: Expected message 0x7e, but didn't receive it.
ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got (0,0)-(1024,768).
ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768.
See https://test.winehq.org/data/patterns.html#ddraw:ddraw1https://test.winehq.org/data/patterns.html#ddraw:ddraw4https://test.winehq.org/data/patterns.html#ddraw:ddraw7
Where 0x7e == WM_DISPLAYCHANGE
This first happened on 2023-04-11 [1] and has happened a bit over once per
month since on both Windows 8 and 10. Most of the time it's the first failure
in the WineTest run.
* 2023-04-11 win81_newtb-w8 (ddraw:ddraw4)
* 2023-04-13 win81_newtb-w8adm (ddraw:ddraw1)
* 2023-04-25 win81_newtb-w8 (ddraw:ddraw7)
* 2023-05-25 win21H1_newtb-w10pro64-he-64 (ddraw:ddraw7)
* 2023-05-25 win81_newtb-w8adm (ddraw:ddraw4, preceded by clip rect failures in
ddraw 1, 2, 4)
* 2023-08-01 win21H1_newtb-w10pro64-ar-64 (ddraw:ddraw4)
* 2023-08-03 win81_newtb-w8adm (ddraw:ddraw1)
[1] There are older instances but I think those were the consequence of
previous 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=55429
Bug ID: 55429
Summary: psapi:psapi_main - test_GetPerformanceInfo() sometimes
fails on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - test_GetPerformanceInfo() sometimes fails on Windows:
psapi_main.c:716: Test failed: expected approximately 1131 but got 1125
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
There are three known instances so far:
* 2023-06-16 win1607_newtb-w1064v1607-32
* 2023-06-28 win21H1_newtb-w10pro64-pt-BR-64
* 2023-08-08 win2004_newtb-w10pro64v2004-64
The test counts the total number of threads on the machine in two different
ways and expects to find the same or a close enough result. In this case some
process with 6 threads must have stopped while the test was running, thus
causing the failure.
The test also counts handles and processes, both of which could probably also
fail in the same way.
I think this is another good candidate for the tryok() patch from MR!3418.
--
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=44051
Bug ID: 44051
Summary: Rendering compressed .avi outputs error on program or
crashes it
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvidc32
Assignee: wine-bugs(a)winehq.org
Reporter: lanfrda1(a)gmail.com
Distribution: Ubuntu
Created attachment 59727
--> https://bugs.winehq.org/attachment.cgi?id=59727
msvidc32 compressed avi render bug log.
If you use any codec, it will make an error on the program (E.G. Flash 8), or
the program will crash (E.G. SidWiz 2).
--
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=12428
Summary: win16 test suite: profile test fails
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://win16test.googlecode.com
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=11967)
--> (http://bugs.winehq.org/attachment.cgi?id=11967)
Backtrace in git
+++ This bug was initially created as a clone of Bug #9850 +++
The code can be downloaded
from http://win16test.googlecode.com with svn,
and is quite easy to run; see
http://win16test.googlecode.com/svn/trunk/src/README
for instructions.
The profile test crashes in current git. Attached is the backtrace in current
git.
--
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=55427
Bug ID: 55427
Summary: ddraw:ddraw7 - test_lighting() sometimes fails on
Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:ddraw7 - test_lighting() sometimes fails on Windows:
ddraw7.c:4728: Test failed: Lit quad without normals has color 0x00ffff00,
expected 0x00000000.
ddraw7.c:4741: Test failed: Lit quad with normals has color 0x00ffff00,
expected 0x00000000.
ddraw7.c:4786: Test failed: Lit quad with light has color 0x00ffffff.
ddraw7.c:4786: Test failed: Lit quad with singular world matrix has color
0x00ffffff.
ddraw7.c:4786: Test failed: Lit quad with transformation matrix has color
0x00ffffff.
ddraw7.c:4786: Test failed: Lit quad with non-affine matrix has color
0x00ffff00.
See https://test.winehq.org/data/patterns.html#ddraw:ddraw7
The number of test failures changes from one run to the next, as well as the
unexpected color, although it's always a mix of ff and 00. This issue has been
there since at least 2023-01-20 and has happened regularly, about 1.5 times per
month, on Windows 8 to Windows 10 22H2.
--
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=55374
Bug ID: 55374
Summary: user32:msg - test_swp_paint_region_on_show() sometimes
gets a NULLREGION on Windows 7
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:msg - test_swp_paint_region_on_show() sometimes gets a NULLREGION on
Windows 7:
msg.c:9471: Test failed: GetRgnBox (on parent) returned 1
msg.c:9475: Test failed: parent update region: got (0,0)-(0,0), expected
(10,10)-(100,100)
msg.c:9508: Test failed: GetRgnBox (on parent) returned 1
msg.c:9512: Test failed: parent update region: got (0,0)-(0,0), expected
(20,20)-(120,120)
See https://test.winehq.org/data/patterns.html#user32:msg
The oldest known failure happened on 2023-06-22 and it has happened a bit over
once per week since, always on a w7u test configuration:
* 2023-06-22 win7_newtb-w7u-2qxl
* 2023-06-23 win7_newtb-w7u
* 2023-06-26 win7_newtb-w7u-2qxl
* 2023-07-13 win7_newtb-w7u-2qxl_1
* 2023-07-14 win7_newtb-w7u-de
* 2023-07-14 win7_newtb-w7u-de
* 2023-07-19 win7_newtb-w7u-es
* 2023-07-19 win7_newtb-w7u-es
--
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=12427
Summary: win16 test suite: printdlg test fails
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://win16test.googlecode.com
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=11966)
--> (http://bugs.winehq.org/attachment.cgi?id=11966)
Backtrace in git
+++ This bug was initially created as a clone of Bug #9850 +++
The code can be downloaded
from http://win16test.googlecode.com with svn,
and is quite easy to run; see
http://win16test.googlecode.com/svn/trunk/src/README
for instructions.
The printdlg test crashes in current git. Attached is the backtrace in current
git.
--
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=55423
Bug ID: 55423
Summary: dinput:device8 - test_mouse_keyboard() sometimes gets
access denied on Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dinput:device8 - test_mouse_keyboard() sometimes gets access denied on Windows
10:
device8.c:695: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005
device8.c:698: Test failed: IDirectInputDevice8_Acquire failed: 0x80070005
device8.c:703: Test failed: GetRegisteredRawInputDevices returned 1,
raw_devices_count: 3
device8.c:705: Test failed: Unexpected raw device flags: 0
device8.c:707: Test failed: Unexpected raw device flags: 0
See https://test.winehq.org/data/patterns.html#dinput:device8
Where 0x80070005 == E_ACCESSDENIED
This failure mode has been jumping around:
* From 2023-01-06 to 2023-03-20 this was happening exclusively on w7u, with one
exception, w10pro64-ru-64 on 2023-01-13 (all with "raw_devices_count: 3").
* Then from 2023-03-21 to 2023-05-16 it happened exclusively on various
debian11-win32 locales, but with "raw_devices_count: 1".
* And since 2023-05-30 it has been happening exclusively on w1064v1507 and
w10pro64v2004 (both in 32 and 64-bit) with 12 instances so far, all with
"raw_devices_count: 3".
See also bug 54558 about other access denied errors in dinput:device8.
--
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=55413
Bug ID: 55413
Summary: ddraw:ddraw1 sometimes fails and crashes on w1064v1507
and w1046v2004
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ddraw:ddraw1 sometimes fails on w1064v1507 and w1046v2004:
ddraw1.c:2495: Test failed: Expected message 0x46, but didn't receive it.
ddraw1.c:2618: Test failed: Failed to set foreground window.
ddraw1.c:2626: Test failed: Failed to set foreground window.
ddraw1.c:2652: Test failed: Expected window style 0x14cf0000, got 0x4cf0000.
ddraw1.c:2655: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2662: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2671: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2680: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2683: Test failed: Failed to set foreground window.
ddraw1.c:2690: Test failed: Expected window style 0x14cf0000, got 0x4cf0000.
ddraw1.c:2693: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2706: Test failed: Failed to set foreground window.
ddraw1.c:2731: Test failed: Failed to set foreground window.
ddraw1.c:2746: Test failed: Failed to set foreground window.
ddraw1.c:2755: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2775: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:2778: Test failed: Failed to set foreground window.
ddraw1.c:2781: Test failed: Expected window style 0x34cf0000, got 0x14cf0000.
ddraw1.c:2784: Test failed: Expected window extended style 0x108, got 0x100.
ddraw1.c:3129: Test failed: Failed to set foreground window.
ddraw1.c:3130: Test failed: Expected message 0x6, but didn't receive it.
ddraw1.c:3135: Test failed: Got unexpected screen size 800x600.
ddraw1.c:867: Test failed: Got unexpected wparam 0 for message 0x1c, expected
0x1.
ddraw1.c:3141: Test failed: Expected message 0x5, but didn't receive it.
ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got
(-32000,-32000)-(-31840,-31972).
ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768.
ddraw1.c:3161: Test failed: Expected message 0x46, but didn't receive it.
[...]
ddraw1.c:3609: Test failed: Expected (0,0)-(640,480), got (-8,-8)-(648,448).
ddraw1.c:4338: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:4350: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:4362: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:4384: Test failed: Expected WM_ACTIVATEAPP, but did not receive it.
ddraw1.c:8051: Test failed: Failed to set foreground window.
ddraw1.c:8053: Test failed: Got unexpected hr 0.
ddraw1.c:8055: Test failed: Got unexpected hr 0.
ddraw1.c:8057: Test failed: Got unexpected hr 0.
ddraw1.c:8059: Test failed: Got unexpected hr 0.
ddraw1.c:8069: Test failed: Got unexpected hr 0.
ddraw1.c:8071: Test failed: Got unexpected hr 0.
ddraw1.c:8073: Test failed: Got unexpected hr 0.
ddraw1.c:8077: Test failed: Failed to set foreground window.
ddraw1.c:8079: Test failed: Got unexpected hr 0.
ddraw1.c:8081: Test failed: Got unexpected hr 0.
ddraw1.c:8087: Test failed: Got unexpected hr 0.
ddraw1.c:8135: Test failed: Failed to set foreground window.
ddraw1.c:8147: Test failed: Failed to set foreground window.
ddraw1.c:13670: Test failed: WM_KILLFOCUS was not received.
ddraw1.c:13706: Test failed: Got unexpected hr 0x887600e1.
ddraw1.c:13709: Test failed: Got unexpected hr 0x887600ff.
0a60:ddraw1: unhandled exception c0000005 at 00007FF6FFAE2567
See https://test.winehq.org/data/patterns.html#ddraw:ddraw1
Where 0x46 == WM_WINDOWPOSCHANGING
and the test window does not seem to be visible:
expected: 0x14cf0000 == WS_VISIBLE | 0x04cf0000
This failure happens irregularly and only on w1064v1507 and w1046v2004 so far:
* 2022-12-14 win1507_newtb-w1064v1507-64
* 2022-12-15 win1507_newtb-w1064v1507-64
* 2023-01-31 win1507_newtb-w1064v1507-64
* 2023-02-16 win1507_newtb-w1064v1507-64
* 2023-06-07 win1507_newtb-w1064v1507-64
* 2023-06-09 win1507_newtb-w1064v1507-32
* 2023-07-13 win1507_newtb-w1064v1507-64
* 2023-07-27 win2004_newtb-w10pro64v2004-64
--
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=55388
Bug ID: 55388
Summary: d3d9:visual - add_dirty_rect_test() fails on
w11pro64-amd
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d9:visual - add_dirty_rect_test() fails on w11pro64-amd:
visual.c:19496: Test failed: Failed to draw, hr 0x80004005.
visual.c:19792: Test failed: Got unexpected color 0x0000ff00.
See https://test.winehq.org/data/patterns.html#d3d9:visual
These failures are systematic and only happen on w11pro64-amd (AMD RX 6600). In
particular they do not happen on fgtb-w10pro64-rx550 the only other test
machine to have an AMD GPU, nor do they happen on the other Windows 11 test
machines (w11pro64 and w11pro64-nv).
--
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=53423
Bug ID: 53423
Summary: Baldur's gate 3 need allocation callbacks for
winevulkan
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: charles2000wang(a)gmail.com
Distribution: ---
Baldur's gate 3 crashes on startup when using the vulkan renderer. These are
the error messages in terminal
0140:fixme:vulkan:wine_vkCreateWin32SurfaceKHR Support for allocation callbacks
not implemented yet
0140:fixme:vulkan:__wine_create_vk_device_with_callback Support for allocation
callbacks not implemented yet
It seems that winevulkan does not have allocation callbacks.
--
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=51122
Bug ID: 51122
Summary: 5.0.3 vs 6.x - slow performance in graphics
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mondane.woodworker(a)gmail.com
Distribution: ---
When I use 6.x, even 'winecfg' starts like a slideshow. This doesn't happen
with 5.0.3 . No application can be ran like this.
Using:
* Wine 6.0 - 6.7
* Ubuntu Unity 20.04.1 ( https://ubuntuunity.org/ )
* Laptop: Dell Precision 7550
* Graphics: NVIDIA TU117GLM [Quadro T2000 Mobile / Max-Q]
** Using nvidia-driver-460
--
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=55419
Bug ID: 55419
Summary: dxgi:dxgi - test_video_memory_budget_notification() is
sometimes missing an event in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
dxgi:dxgi - test_video_memory_budget_notification() is sometimes missing an
event in Wine:
dxgi.c:7876: Test failed: Expected event fired.
See https://test.winehq.org/data/patterns.html#dxgi:dxgi
The first known instance goes back to 2023-01-26 and it has been happening a
bit over twice per month since, mostly on the debiant VM but also on the GitLab
CI environment and fg-deb64 (my desktop).
--
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=55418
Bug ID: 55418
Summary: quartz:vmr9 - test_surface_allocator_notify_refcount()
sometimes crashes on w11pro64_nv
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
quartz:vmr9 - test_surface_allocator_notify_refcount() sometimes crashes on
w11pro64_nv:
vmr9.c:3475: this is the last test seen before the exception
1828:vmr9: unhandled exception c0000005 at 000000000049805A
See https://test.winehq.org/data/patterns.html#quartz:vmr9
This is crash happened only twice so far and both times on w11pro64_nv, the
TestBot's Windows 11 Nvidia RTX 3050 VM:
* 2023-08-04 w11pro64-nv-64
* 2023-03-03 w11pro64-nv-64
--
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.