wine-bugs May 2022

wine-bugs@winehq.org

1 participants
3544 discussions

[Bug 47229] New: gog.com - The Void: crashes when entering two game locations
by wine-bugs＠winehq.org 14 May '22

14 May '22

https://bugs.winehq.org/show_bug.cgi?id=47229 Bug ID: 47229 Summary: gog.com - The Void: crashes when entering two game locations Product: Wine Version: 4.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru Distribution: --- Created attachment 64501 --> https://bugs.winehq.org/attachment.cgi?id=64501 Output log of wine before crashing Video game The Void (GOG edittion) crashes with "Unhandled page fault on read access to 0x00000000 at address 0x1953eb7" in the same locations every time. It's make finish game impossible. There are at least two problem places at game. See more in attachment 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.

2 29

[Bug 47720] New: eac3to performance issues
by wine-bugs＠winehq.org 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=47720 Bug ID: 47720 Summary: eac3to performance issues Product: Wine Version: 4.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 65192 --> https://bugs.winehq.org/attachment.cgi?id=65192 wine version eac3to used to work well a year ago but now has a few issues which need to be addressed not least of which is it takes 4 times longer to demux than it does when run under windows. Also the lossless check seems not to be done and certainly is not reported. A number of warnings which are generated apparently needlessly. I have attached screen shots from under wine and under windows which will show clearly the issues. -- 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 8

[Bug 51312] New: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460)
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=51312 Bug ID: 51312 Summary: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460) Product: Wine Version: 6.10 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 gets failures of the form: https://test.winehq.org/data/patterns.html#dxgi:dxgi dxgi.c:1460: Test failed: Mode 3: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 22: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 55: Modes should have been sorted, refresh rate 59.940060 < 75.000000. * These failures happen on all available Windows versions (8.1 to 10 2009). * They also happen regardless of the Radeon driver version: 19.11.3 to 21.4.1. * They don't happen on machines with any other GPU (cw-gtx560 and QEmu VMs). * They also happen systematically so are not probably caused by a threading issue. * So this really looks like a Radeon-specific behavior. The failing test was introduced by the following commit: commit eb2028fa90c41d3b7b8b4f924cd86059c5ba1e0d Author: Andrew Eikum <aeikum(a)codeweavers.com> AuthorDate: Mon Oct 28 16:59:18 2019 +0330 dxgi: Sort reported output modes. Sekiro: Shadows Die Twice depends on this for its mode switching. Signed-off-by: Andrew Eikum <aeikum(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Does the application crash on Windows machines with an AMD GPU? Or does the Radeon driver return the wrong order only on some GPUs? If the application does not crash maybe our order specification is a bit too strict? Given that an application depends on this we probably want Wine to respect the ordering. Just add a broken()? -- 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 7

[Bug 52996] New: comdlg32:printdlg fails when OneNote is installed
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=52996 Bug ID: 52996 Summary: comdlg32:printdlg fails when OneNote is installed Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comdlg32:printdlg fails on cw-gtx560 and cw-rx460 when running Windows 1809 and 1909: printdlg.c:198: driver 'winspool' device 'OneNote' port 'Microsoft.Office.OneNote_16001.11629.20028.0_x64__8wekyb3d8bbwe_microsoft.onenoteim_S-1-5-21-2735375161-1667520140-535807745-1002' printdlg.c:215: Test failed: got 0 with 2 and 00000000 for '' (expected '>1' and '!= NULL') printdlg.c:220: Test failed: got driver 'winspool' (expected '') https://test.winehq.org/data/tests/comdlg32:printdlg.html It turns out these test configurations are the only ones that have this 'OneNote' line. All the others have the following trace instead: printdlg.c:198: driver 'winspool' device 'Microsoft Print to PDF' port 'PORTPROMPT:' So my understanding is that 'Microsoft Print to PDF' is the default printer for all the machines except for these four where "OneNote" is the default instead. I don't know how "OneNote" came to be the default on these machines. I don't think it was intentional on my part. Rather I suspect there was some randomness in the order in which some Windows updates were installed or something like that. For reference the cw-rx460-1909 machine has the following printers: * Fax * Microsoft Print to PDF --> This seems to be the default printer on all other machines. * Microsoft XPS Document Writer * OneNote --> This is the one that's selected by default in notepad, so presumably the default printer. (The Windows 10 1909 GUI does not make that really clear anywhere else that I could find) So it seems like the test should be adjusted to not fail with the OneNote printer. That or that check should be skipped? -- 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 50368] New: DragonAge Origins Launcher doesn't toggle music status
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=50368 Bug ID: 50368 Summary: DragonAge Origins Launcher doesn't toggle music status Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: ArchLinux Until recently the Dragon Age Origins Launcher didn't work at all becouse bug #44185 that was recently fixed. However now, the laucnehr start, it play correctly the music but the toggle button to disable/enable the music doesn't work. This is the flow of what seems the issue: 0164:trace:mci:mciSendStringW (L"pause all", 0074EE48, 100, 00000000) 0164:trace:mci:mciSendStringW verb=L"pause" on dev=L"all"; offset=4 0164:trace:mci:mciSendStringW [-1, MCI_PAUSE, 00000000, 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000] 0164:fixme:mci:MCI_SendCommand unhandled MCI_ALL_DEVICE_ID 0164:trace:mci:mciSendStringW => 117 wine isn't handling correctly the MCI_ALL_DEVICE_ID case in cases others then closing the device. This affect just the launcher (the game should work properly if not regressed recently, still didn't try) so low priority, but other programs may be affected. -- 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 52990] New: MFMEv20 Emulator needs user32.RegisterTouchWindow implementation
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52990 Bug ID: 52990 Summary: MFMEv20 Emulator needs user32.RegisterTouchWindow implementation Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian With wine-7.8, the application pops up an error dialog on start: RegisterTouchWindow Failed. If the function is hacked to return TRUE instead of FALSE, the application then starts fine. -- 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 51217] New: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51217 Bug ID: 51217 Summary: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:info has a failure on w1064v1607 (Windows 10 64-bit version 1607 running the 32-bit tests): https://test.winehq.org/data/patterns.html#ntdll:info info.c:3024: Test failed: wrong result 0 This is a check of the RtlWow64IsWowGuestMachineSupported() result. The commit that introduced this check is: commit 4f8ede8e7665328a2a3ccd303875e239bf443512 Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Thu Apr 29 17:15:15 2021 +0200 ntdll: Implement RtlWow64IsWowGuestMachineSupported(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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

[Bug 51078] New: mshtml:events hangs on Windows 10 1709
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51078 Bug ID: 51078 Summary: mshtml:events hangs on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 69941 --> https://bugs.winehq.org/attachment.cgi?id=69941 Patch to more reliably reproduce the hang mshtml:events sometimes hangs on Windows 10 1709: http://winetest.dolphin/data/patterns.html#mshtml:events For some reason this only happens on Windows 1709 (the reports say this is mshtml 11.0.16299.309). The test proceeds all the way to the end but then does not exit because the mshtml component still has threads running: VSyncHelper Internet Explorer_Hidden MSCTFIME UI Commenting out the test_focus() run gets rid of the hangs. Also running the test with WINETEST_INTERACTIVE=1 greatly increases the probability of getting a hang. I attached a patch that does that and can be used to reproduce the hang on the TestBot's w1064v1709 VM. So this is clearly related to focus. -- 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 52988] New: comctl32:monthcal fails on Windows in Korean because of unexpected IME messages
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52988 Bug ID: 52988 Summary: comctl32:monthcal fails on Windows in Korean because of unexpected IME messages Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:monthcal fails on Windows in Korean because of unexpected IME messages: monthcal.c:631: Test failed: create parent window: the msg 0x0007 was expected, but got msg 0x0282 instead monthcal.c:631: Test failed: create parent window: the msg 0x0047 was expected, but got msg 0x0024 instead monthcal.c:631: Test failed: create parent window: the msg 0x0005 was expected, but got msg 0x0282 instead monthcal.c:631: Test failed: create parent window: the msg 0x0003 was expected, but got msg 0x0281 instead monthcal.c:631: Test failed: create parent window: the msg sequence is not complete: expected 0000 - actual 0282 monthcal.c:631: Failed sequence create parent window: monthcal.c:631: 0: expected: 0024 - actual: 0024 wp 00000000 lp 0072f630 monthcal.c:631: 1: expected: 0081 - actual: 0081 wp 00000000 lp 0072f5e0 monthcal.c:631: 2: expected: 0083 - actual: 0083 wp 00000000 lp 0072f650 monthcal.c:631: 3: expected: 0001 - actual: 0001 wp 00000000 lp 0072f590 monthcal.c:631: 4: expected: 0018 - actual: 0018 wp 00000001 lp 00000000 monthcal.c:631: 5: expected: 0046 - actual: 0046 wp 00000000 lp 0072f630 monthcal.c:631: 6: expected: 030f - actual: 0046 wp 00000000 lp 0072f630 monthcal.c:631: 7: expected: 0046 - actual: 001c wp 00000001 lp 0000095c monthcal.c:631: 8: expected: 0047 - actual: 0086 wp 00000001 lp 00000000 monthcal.c:631: 9: expected: 001c - actual: 0006 wp 00000001 lp 00000000 monthcal.c:631: 10: expected: 0086 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 11: expected: 0006 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 12: expected: 0281 - actual: 0024 wp 00000000 lp 0072d650 monthcal.c:631: 13: expected: 0282 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 14: expected: 0007 - actual: 0281 wp 00000001 lp c000000f monthcal.c:631: 15: expected: 0047 - actual: 0282 wp 00000002 lp 00000000 monthcal.c:631: 16: expected: 0083 - actual: 0007 wp 00000000 lp 00000000 monthcal.c:631: 17: expected: 0005 - actual: 0047 wp 00000000 lp 0072f630 monthcal.c:631: 18: expected: 0003 - actual: 0005 wp 00000000 lp 01d701ee monthcal.c:631: 19: expected: nothing - actual: 0003 wp 00000000 lp 001a0003 monthcal.c:655: old style: 0x50800000, new style: 0x50800002 monthcal.c:655: old style: 0x50800000, new style: 0x50800000 monthcal.c:655: old style: 0x50800002, new style: 0x50800000 monthcal.c:655: old style: 0x50800002, new style: 0x50800002 monthcal.c:655: old style: 0x50800000, new style: 0x50800001 monthcal.c:655: old style: 0x50800000, new style: 0x50800000 monthcal.c:655: old style: 0x50800001, new style: 0x50800000 monthcal.c:655: old style: 0x50800001, new style: 0x50800001 https://test.winehq.org/data/patterns.html#comctl32:monthcal WM_GETMINMAXINFO == 0x0024 WM_IME_SETCONTEXT == 0x0281 WM_IME_NOTIFY == 0x0282 create_parent_window_seq[] already has some optional IME messages so it looks like more need to be added / moved to another place. The WM_GETMINMAXINFO is new though. -- 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 39659] New: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop
by wine-bugs＠winehq.org 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=39659 Bug ID: 39659 Summary: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop Product: Wine Version: 1.8-rc1 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Created attachment 52866 --> https://bugs.winehq.org/attachment.cgi?id=52866 log of test failure Test report: https://test.winehq.org/data/1d19eb15d4abfdd14dccc5ac05b83c0ee1a1ace1/win8_… Message tests calling SetFocus() on a button fail on my Windows 8 machine, because they get a WM_CANCELMODE message they weren't expecting. I have no idea what's special about my setup. It doesn't matter if I run the test stand-alone or with the full test suite, or if I run it as a dedicated user with a default configuration. -- 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 5

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 May 2022