wine-bugs

wine-bugs@winehq.org

1 participants
158797 discussions

[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

[Bug 30875] New: Unable to deselect character blocks in BMFont
by wine-bugs＠winehq.org 12 May '22

12 May '22

http://bugs.winehq.org/show_bug.cgi?id=30875 Bug #: 30875 Summary: Unable to deselect character blocks in BMFont Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dav75uk(a)yahoo.co.uk Classification: Unclassified Run BMFont (http://www.angelcode.com/products/bmfont/) and click on some of the checkboxes to the right to select characters to be included. It is not possible to uncheck the checkboxes. Workaround is to unselect one of the characters (click on a character in that range) which changes the full checked box to a part check box. The part check box can be unselected. -- 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 7

[Bug 52911] New: ole32:moniker fails on Windows in the UTF-8 codepage
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52911 Bug ID: 52911 Summary: ole32:moniker fails on Windows in the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ole32:moniker fails on Windows in the UTF-8 codepage: moniker.c:2189: Test failed: IsEqual failed with error 0x000001 [...] https://test.winehq.org/data/patterns.html#ole32:moniker So the failures happen because moniker1 and moniker2 are always different. Adding a call to winetest_push_context() shows that the failures all happen for string 2 which ole32:moniker uses to skip tests on code pages where there are round-trip issues: {0xc0, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, 0xc8, 0xc9, 0xca, 0xcb, 0xcc, 0xcd, 0xce, 0xcf, 0xd0, 0}, [...] skip("string 2 doesn't round trip in codepage %u\n", GetACP() ); So it looks like the skip fails to trigger for the UTF-8 codepage (or that we should do something else to make the UTF-8 case 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.

1 2

[Bug 45432] New: Implement Windows Native Firewall Rules for Lightwave Software Licensing - netfw_rules
by wine-bugs＠winehq.org 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=45432 Bug ID: 45432 Summary: Implement Windows Native Firewall Rules for Lightwave Software Licensing - netfw_rules Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: newel.anderson(a)gmail.com Distribution: --- Created attachment 61753 --> https://bugs.winehq.org/attachment.cgi?id=61753 Terminal logs installing and launching Lightwave under WIne 3.11 in Linux Lightwave requires Windows Native Firewall Inbound/Outbound Rules in order to register/activate one's license. For reference, please see: https://forum.winehq.org/viewtopic.php?f=8&t=30847&p=116945#p116945 (I'm wineink) Towards the end of the above thread I posted terminal output as well as screenshots. Disabling Windows Firewall, as well as deleting the inbound/outbound rules in Windows, deactivates my license. Re-enabling the rules and Windows Firewall reactivates my license. Since this functionality doesn't exist in Wine, Wine hasn't to my knowledge implemented Windows Native Firewall Rules, it's impossible to register/activate my legally purchased license in Wine. Thank you for your time and consideration. ***Please note, the above applies only to a FULL license of Lightwave. The trial, which is node-locked, works as designed. Unfortunately, the FULL license is not node-locked. -- 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 45

[Bug 52986] New: d3d9:device - In Wine test_vertex_buffer_read_write() fails on on cw-rx460
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52986 Bug ID: 52986 Summary: d3d9:device - In Wine test_vertex_buffer_read_write() fails on on cw-rx460 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 - In Wine test_vertex_buffer_read_write() only succeeds on cw-rx460: device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 0. device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 1. device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 2. https://test.winehq.org/data/patterns.html#d3d9:device This is specific to this machine so it seems likely that this is related to the graphics card / driver. -- 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 0

[Bug 52985] New: d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52985 Bug ID: 52985 Summary: d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm 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: --- Created attachment 72354 --> https://bugs.winehq.org/attachment.cgi?id=72354 The TestBot's fvwm configuration d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm: device.c:4822: Test failed: Received unexpected WM_SIZE message. https://test.winehq.org/data/patterns.html#d3d9:device This failure happens on cw-gtx560, cw-rx460 and debian11 VM which all run Debian 11 with fvwm, and on debiant VM which runs Debian Testing with fvwm. But it does not happen on fg-deb64 which runs Debian 11 too, but with KDE's window manager. So it is pretty likely that this failure only happens when running fvwm. -- 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 52984] New: d3d8:device - test_cursor_pos() missing a MOUSEMOVE on cw-gtx560 and cw-rx460
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52984 Bug ID: 52984 Summary: d3d8:device - test_cursor_pos() missing a MOUSEMOVE on cw-gtx560 and cw-rx460 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 d3d8:device - test_cursor_pos() is missing a MOUSEMOVE most of the time on cw-gtx560 and cw-rx460: device.c:1324: Test failed: Didn't receive MOUSEMOVE 0 (50, 50). https://test.winehq.org/data/patterns.html#d3d8:device This happens almost systematically on cw-gtx560 and cw-rx460 with Windows 10 1709 to 1909 but happens much less frequently with more recent Windows versions. Also it never happens in the TestBot VMs running the same Windows versions and also does not happen on fgtb-w10pro64-rx550. So it may be related to the set of display modes that the monitor supports which would explain why the KVM-connected machines are impacted and not the others. Or it could be related to the GPU drivers and fgtb-w10pro64-rx550 just got lucky because it's on a more recent 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.

1 1

[Bug 52935] New: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52935 Bug ID: 52935 Summary: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage 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:tab's test_tab(-1&-3) fails on Windows with the UTF-8 codepage: tab.c:591: Testing with default MinWidth tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] tab.c:593: Testing with MinWidth set to -3 tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] https://test.winehq.org/data/patterns.html#comctl32:tab Hindi + UTF-8 is the only locale where this test fails on Windows at this time. In particular there is no failure on the standard Hindi locale (English system locale) so this appears to be specific to UTF-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.

1 2

[Bug 52939] New: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52939 Bug ID: 52939 Summary: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 72312 --> https://bugs.winehq.org/attachment.cgi?id=72312 Loop on test_RegNotifyChangeKeyValue() to reproduce the event failures advapi32:registry's test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions: registry.c:3471: Test failed: expected ERROR_SUCCESS, got 6 registry.c:3599: Test failed: expected WAIT_OBJECT_0, got 258 https://test.winehq.org/data/patterns.html#advapi32:registry The failure is pretty rare so it is likely to cause false positives. The attached patch makes it possible to systematically reproduce the issue, at least on my test VM. With the 10000 loops I get 4 to 5 cases with the failure (so a rate of 0.05%) and a test run still takes under 8 seconds. -- 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 52925] New: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc)
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52925 Bug ID: 52925 Summary: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc) Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com usp10:usp10's wgDefault check in test_ScriptGetFontProperties() fails on some bitmap fonts in a number of locales: * Arabic usp10.c:2591: Test failed: bitmap font System wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 0126, tmDefaultChar 0085 * Hebrew usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 01ac, tmDefaultChar 0080 * Hindi + UTF-8 (no failure for plain Hindi) usp10.c:2591: Test failed: bitmap font System wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Courier wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 00fd, tmDefaultChar 0081 usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 00fd, tmDefaultChar 0080 * Japanese usp10.c:2591: Test failed: bitmap font FixedSys wgDefault 00f0, tmDefaultChar 00a0 usp10.c:2591: Test failed: bitmap font @FixedSys wgDefault 00f0, tmDefaultChar 00a0 * Chinese usp10.c:2591: Test failed: bitmap font System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Fixedsys wgDefault 00ac, tmDefaultChar 0080 https://test.winehq.org/data/patterns.html#usp10:usp10 In each case we get the expected value on Windows with a number of fonts but there are some exceptions that cause the failures. For a given locale the exceptions all have the same wgDefault value which means there is probably some logic to it. So we either need to come up with a better way to find the expected wgDefault value, or to radically loosen the test, or to restrict the test to some 'safe' fonts, or to remove the test entirely. -- 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 52981] New: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52981 Bug ID: 52981 Summary: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Most of test_SpeechRecognizer() is skipped when run with elevated privileges: speech.c:896: SpeechRecognizer default language L"fr-FR". speech.c:1172: Tests skipped: Could not init SpeechRecognizer with default language! https://test.winehq.org/data/patterns.html#windows.media.speech:speech The involved lines are: 919 hr = RoActivateInstance(hstr, &inspectable); 922 if (hr == S_OK) ... 1170 else if (hr == SPERR_WINRT_INTERNAL_ERROR) /* Not sure when this triggers. Probably if a language pack is not installed. */ 1171 { 1172 win_skip("Could not init SpeechRecognizer with default language!\n"); An analysis of the test results across Windows versions shows that we see this SPERR_WINRT_INTERNAL_ERROR on Windows 10 >= 1809: cw-gtx560-1507 S_OK cw-rx460-1507 S_OK w1064v1507 S_OK w1064v1607 S_OK cw-gtx560-1709 S_OK cw-rx460-1709 S_OK w1064v1709 S_OK cw-gtx560-1809 skipped cw-rx460-1809 skipped w1064v1809 skipped cw-gtx560-1909 skipped cw-rx460-1909 skipped w1064v1909 skipped w1064v2004 skipped cw-gtx560-2009 skipped cw-rx460-2009 skipped w1064v2009 skipped cw-gtx560-21h1 skipped cw-rx460-21h1 skipped w10pro64-21h1 skipped cw-gtx560-21h2 skipped cw-rx460-21h2 skipped w1064-21h2 skipped w10pro64-21h2 skipped So far that looks pretty clear cut: Microsoft changed things around 1809 such that processes running with elevated privileges cannot / are not allowed to perform speech recognition. That would mean the test should drop the privileges so it can run on any platform. However the test was not skipped in the w10pro64v2004 and w10pro64 (21H1) test configurations... until they were upgraded. So this indicates that there may be a way to get this test to work even while retaining elevated privileges. But how? To help debug the issue I added two test configurations: * w10pro64restored The w10pro64 VM restored from a backup of the pre-2022-05 upgrade VM. Surprisingly the test still ends up being skipped! * w10pro64old Luckily before the upgrade I moved the old VM out of the way. It is now available as w10pro64old with the exact same live snapshots. Comfortingly the test is still not skipped, even after waiting some time and rebooting. That last part indicates there may be something either in the way the TestBot creates the live snapshots, or in the "WineTestBot VMs" checklist I go through when preparing the VMs and the cw-* machines (but then the clear 1809 cutoff point is quite a coincidence). -- 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 0

[Bug 33621] New: [UWIN] ksh93 from UWIN generates a lot of fixme warnings
by wine-bugs＠winehq.org 11 May '22

11 May '22

http://bugs.winehq.org/show_bug.cgi?id=33621 Bug #: 33621 Summary: [UWIN] ksh93 from UWIN generates a lot of fixme warnings Product: Wine Version: 1.5.30 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: simon.toedt(a)gmail.com Classification: Unclassified Running ksh93 (Korn Shell 93) from the UWIN (Unix emulation on Windows) toolkit generates a lot of "fixme" warnings and the shell is generally not useable. The goal is to use WINE for automated testing without having to fire up a full blown Windows system each time in VMware or real iron. Steps to test: 1. Install UWIN: > wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…' > wine uwin-base.2013-02-08.win32.i386.exe 2. Run Windows/UWIN version of ksh93: wine64 'C:\Program Files/UWIN/usr/bin/ksh.exe' fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000000, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:advapi:LsaOpenPolicy ((null),0x23f980,0x00000001,0x23f950) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netbios:NetServerEnum Stub ((null) 100 0x23f440 -1 0x23fbb8 0x23fbc8 24 (null) (nil)) fixme:netapi32:NetGetDCName ((null), (null), 0x23f448) stub! fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0xf70850,symt:0xfce150) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x20e2370,symt:0x2140480) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e98,symt:0x2970264) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2943cb0,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e90,symt:(nil)) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x36b3448,symt:0x378fa1c) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743718,symt:0x37781b4) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743658,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x37425a0,symt:0x3754e38) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work as described in bug 33619. IMO the most pressing problems are: 1. fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. 2. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented 3. fixme:netapi32:NetUserGetInfo Level 3 is not implemented 4. fixme:ntdll:NtSetInformationToken unimplemented class 4 5. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented -- 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 10

[Bug 52968] New: CPU BoostTester manages to run only on real cores in Windows, but not with wine
by WineHQ Bugzilla 09 May '22

09 May '22

https://bugs.winehq.org/show_bug.cgi?id=52968 Bug ID: 52968 Summary: CPU BoostTester manages to run only on real cores in Windows, but not with wine 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: christian.frank(a)gmx.de Distribution: --- Hi, the following tiny porgram is used to test the boost capability of cpus. It detects real cores and only tests those, not the smt siblings. On windows it manages to run on the real cores only. On Linux it runs on the cores 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30 I am using a 5950x. The real cores are 0-15. The siblings ar 16-31. 0+16 is a pair, 1+17, 2+18 etc.. So instead of testing the 16 real cores, it is testing only 8 + siblings. The software is availible here, including source. I don't know if the software is doing some strange things to detect the real cores or if the issue is on the wine side. As the source is just a handful of c++ code, someone with experience might take a look and judge where the problem is, wine or the program. Here is the link: https://github.com/jedi95/BoostTester Many thx ! -- 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 52976] New: Daagon Map Maker on itch.io crash
by WineHQ Bugzilla 08 May '22

08 May '22

https://bugs.winehq.org/show_bug.cgi?id=52976 Bug ID: 52976 Summary: Daagon Map Maker on itch.io crash Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)winehq.org Reporter: ildaniel999(a)hotmail.com Distribution: --- Created attachment 72346 --> https://bugs.winehq.org/attachment.cgi?id=72346 wine file loads up to 100%, changes screen settings, but then crashes -- 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 0

[Bug 52684] New: Command and Conquer Generals (and C&C Zero Hour) have no ground textures
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=52684 Bug ID: 52684 Summary: Command and Conquer Generals (and C&C Zero Hour) have no ground textures Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: bender647(a)yahoo.com Regression SHA1: 1632b8e7a419ebf256c4a356a58d505ef918f2fe Distribution: Slackware Introduced in wine-7.3 with commit 1632b8e7a419ebf256c4a356a58d505ef918f2fe, the C&C Generals game engine does not draw ground textures. The ground (or water) area is black. Reverting to wine-7.2, or applying this commit as a reverse-patch on wine-7.4 will fix the issue. The commit was found by bisecting the git tree. This symptom appears in older bug reports but the fixes there do not appear to work now. Tested on two platforms, but both were Intel i915 graphics. If necessary, I can get access to an Nvidia platform. To reproduce: 1. A free demo is available for download to run the game: https://www.moddb.com/downloads/start/111369 (https://www.moddb.com/games/cc-generals/downloads/command-conquer-generals-…). 2. Install in 32-bit prefix. 3. Run with `wine start generals.exe -nologo` and the game engine will be seen running behind the main menu. The ground will be blank if the bug is present. Verified to affect: https://appdb.winehq.org/objectManager.php?sClass=version&iId=4881 https://appdb.winehq.org/objectManager.php?sClass=version&iId=35407 Likely also: https://appdb.winehq.org/objectManager.php?sClass=version&iId=1717 -- 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 24

[Bug 45098] New: FrostPunk: multiple graphical glitches
by wine-bugs＠winehq.org 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=45098 Bug ID: 45098 Summary: FrostPunk: multiple graphical glitches Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)embed.me.uk Distribution: --- Created attachment 61268 --> https://bugs.winehq.org/attachment.cgi?id=61268 FrostPunk log With patch posted in https://bugs.winehq.org/show_bug.cgi?id=45080 the game sucessfully starts however there are severe graphical glitches which render it unplayable. Log attached. -- 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 15

[Bug 2155] Failure of SetFocus, SetActiveWindow and SetForegroundWindow
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=2155 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de -- 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 0

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