wine-bugs August 2023

wine-bugs@winehq.org

1 participants
2457 discussions

[Bug 54933] New: Wine slow on certain fuse filesystems, with fix
by WineHQ Bugzilla 12 Aug '23

12 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54933 Bug ID: 54933 Summary: Wine slow on certain fuse filesystems, with fix Product: Wine Version: 8.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: hwertz10(a)gmail.com Distribution: --- Created attachment 74452 --> https://bugs.winehq.org/attachment.cgi?id=74452 CIOPFS speed patch I found a description of users experiencing slowdowns (even using explorer.exe) on an MTP filesystem, and I experienced similar slowdowns on an s3ql filesystem. In short, even using explorer on certain filesystems is slow, and opening programs that open up more than a handful of files is very slow off these filesystems.: https://forum.winehq.org/viewtopic.php?t=36400 I found the root cause courtesy of strace -- in dlls/ntdll/unix/file.c in get_dir_case_sensitivity_stat (which is called very frequently, I think on any file open or creation, among others), there is a fstatat system call, then a check on that result to see if the filesystem is a FUSE filesystem, then if it is it looks for a .ciopfs directory (because presumably CIOPFS -- Case Insensitive On Purpose Filesystem -- places a .ciopfs in every directory specifically so wine can do this test.) It turns out the fstatat call gets used and free inode count, used and free disk space, etc. along with filesystem type, and on my large s3ql filesystem at least this takes *8/10ths* of a second, versus the .ciopfs lookup being in dentry cache -- I don't recall if it used 0.0001 or 0.00001 seconds, but either way extremely fast compared to the other call. Reversing the order of these calls (check for .ciopfs first, then if it's there run fstatat and check result to see if it's a FUSE filesystem) should not cause a performance regression on any filesystem (since it's usually going to be out of the dentry cache) while avoiding this slowdown on a filesystems with slow filesystem stats. Just a note, I see the equivalent "is filesystem case sensitive?" check for MacOS actually only runs any tests once then caches the results; using a similar "case sensitivity" cache for Linux would also be effective (since it would only run this piece of code once per wine run then.) Finally, I wonder if CIOPFS is actually used? I see the last update on it is from 2011, it may have turned out that Wine's case insensitivity support is fast enough that CIOPFS did not prove useful. If it's not actually being used by anyone, removing the CIOPFS tests from file.c could be a reasonable thing to do. Please find attached a small patch to implement this change for Linux -- it simply reverses the order of 3 lines of code, so it runs the (fast) .ciopfs directory existence test first, then only runs the (on some filesystems much slower) fstatat call and "is it FUSE filesystem?" test if the.ciopfs directory actually exists. Thanks, and keep up the good work!!! --Henry -- 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.

1 1

[Bug 30550] New: Invisibles sprites in Rayman Origins
by wine-bugs＠winehq.org 12 Aug '23

12 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=30550 Bug #: 30550 Summary: Invisibles sprites in Rayman Origins Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: olivier.luraine(a)gmail.com Classification: Unclassified Created attachment 39961 --> http://bugs.winehq.org/attachment.cgi?id=39961 Screenshot that shows the bug. They are missing sprites on rayman origins. For exemple ropes and other things that rayman catch are invisible. I'm using an up to date archlinux with nvidia 295.40. The game run smoothly. -- 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.

2 44

[Bug 37355] New: Tages Protection v5.x needs ntoskrnl 'MmMapLockedPagesSpecifyCache' implementation
by wine-bugs＠winehq.org 11 Aug '23

11 Aug '23

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.

2 56

[Bug 55431] New: wine-staging to have same Component as wine
by WineHQ Bugzilla 11 Aug '23

11 Aug '23

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.

1 3

[Bug 47996] New: Battlefield 2 - d3d:debug_d3dformat Unrecognized 0x4642564e - Unhandled exception
by WineHQ Bugzilla 11 Aug '23

11 Aug '23

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.

1 8

[Bug 55416] New: psapi:psapi_main - check_QueryWorkingSetEx() sometimes fails on Windows 10
by WineHQ Bugzilla 11 Aug '23

11 Aug '23

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.

1 2

[Bug 55426] New: user32:msg - test_swp_paint_region_on_show() sometimes fails on w7u
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

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.

1 2

[Bug 55425] New: user32:msg - test_swp_paint_region_on_extend_zerosize() sometimes fails on w7u
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

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.

1 3

[Bug 55381] New: installing synaptics fingerprint reader driver fails
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

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.

1 2

[Bug 54095] New: quartz:filtermapper sometimes crashes on exit in Wine
by WineHQ Bugzilla 10 Aug '23

10 Aug '23

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.

1 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs August 2023