December 2022 - Wine-bugs - list.winehq.org

[Bug 53986] New: wininet:http - test_concurrent_header_access() sometimes fails on Windows 7 & 8
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53986 Bug ID: 53986 Summary: wininet:http - test_concurrent_header_access() sometimes fails on Windows 7 & 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wininet:http - test_concurrent_header_access() sometimes fails on Windows 7 & 8: http.c:7825: Test failed: HttpQueryInfoA failed 6 See https://test.winehq.org/data/patterns.html#wininet:http This is an old failure going back to at least 2022-06-07 and the failure rate is below 2% so it is going to be hard to reproduce. -- 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 54042] New: wmvcore:wmvcore - test_sync_reader_types() sometimes gets an NS_E_INCOMPATIBLE_FORMAT error in Wine
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54042 Bug ID: 54042 Summary: wmvcore:wmvcore - test_sync_reader_types() sometimes gets an NS_E_INCOMPATIBLE_FORMAT error in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- wmvcore:wmvcore - test_sync_reader_types() sometimes gets an NS_E_INCOMPATIBLE_FORMAT error in Wine: wmvcore.c:1521: Test marked todo: Stream 0: Got output number 0. wmvcore.c:1579: Test failed: Stream 0: Got hr 0xc00d0041. wmvcore.c:1586: Test marked todo: Stream 0: Got hr 0. See https://test.winehq.org/data/patterns.html#wmvcore:wmvcore This failure first happened on 2022-09-27, there are no record of it in the previous 4 months, and it has happened about every other week since. So it is probably caused by a change in Wine that occurred in September. -- 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 54187] New: dxgi:dxgi - test_swapchain_parameters() sometimes gets access denied errors on Windows 8
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54187 Bug ID: 54187 Summary: dxgi:dxgi - test_swapchain_parameters() sometimes gets access denied errors on Windows 8 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 dxgi:dxgi - test_swapchain_parameters() sometimes gets access denied errors on Windows 8: dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 10. dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 11. dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 20. dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 33. dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 34. dxgi.c:4487: Test failed: Got unexpected hr 0x80070005, test 43. See https://test.winehq.org/data/patterns.html#dxgi:dxgi Where 0x80070005 == E_ACCESSDENIED This always happens with the same set of 6 tests. This happened once on w8adm (2022-11-29) but usually happens on w864 (4 instances) where the test runs with elevated privileges. -- 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 42384] New: WinOmega 10.00.24 attempts to use certmgr.msc
by wine-bugs＠winehq.org 19 Dec '22

19 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=42384 Bug ID: 42384 Summary: WinOmega 10.00.24 attempts to use certmgr.msc Product: Wine Version: 2.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: info(a)winomega.com Distribution: --- Created attachment 57179 --> https://bugs.winehq.org/attachment.cgi?id=57179 certmgr.msc error WinOmega 10.00.24 (https://appdb.winehq.org/objectManager.php?sClass=version&iId=33538) is yields an error (see screenshot) when attempting to manage certificates through: Facturación -> Clientes -> Firmar -> Factura-e The program relies on certmgr.msc (MMC snap-in) for certificate management. A possible workaround could be to use certmgr.exe (Certificate Manager Tool) in its stead. However certmgr.exe isn't usable due to bug 42383 (https://bugs.winehq.org/show_bug.cgi?id=42383) -- 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 51588] New: MS Visio 2016 not work
by WineHQ Bugzilla 19 Dec '22

19 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=51588 Bug ID: 51588 Summary: MS Visio 2016 not work Product: Wine Version: 6.0.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mettalhunter(a)yahoo.com.ar Distribution: --- Created attachment 70436 --> https://bugs.winehq.org/attachment.cgi?id=70436 cosole output Hi! I installed MS Visio 2016 but it does not start, not show Windows, nothing. I used Gentoo Linux with Wine-6.0 and Wine-6.14. I installed: riched20, riched30, mfc40, mfc42, msxml6, msxml3, vcrun (2008 until 2017), msftedit. What is 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.

1 4

[Bug 54179] New: Maximized windows are not maximized with built-in decorations
by WineHQ Bugzilla 19 Dec '22

19 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54179 Bug ID: 54179 Summary: Maximized windows are not maximized with built-in decorations Product: Wine Version: 8.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 73705 --> https://bugs.winehq.org/attachment.cgi?id=73705 Maximized notepad Steps to reproduce: 1) winecfg -> Graphics -> uncheck "Allow the window manager to decorate the windows" 2) Run [wine] notepad 3) Maximize it Results: You can still resize the window as the mouse cursor changes to double-arrows at the borders of the screen. Expected results: The window is indeed maximized and cannot be resized unless you restore/unmaximize it. -- 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 50298] New: w1064v1909 shows the "create a Windows account" fullscreen dialog
by WineHQ Bugzilla 19 Dec '22

19 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=50298 Bug ID: 50298 Summary: w1064v1909 shows the "create a Windows account" fullscreen dialog Product: Wine-Testbot 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: --- Created attachment 68868 --> https://bugs.winehq.org/attachment.cgi?id=68868 w1064v1909 "Let's finish setting up your device" dialog w1064v1909 corresponds to the 1909-live snapshot of the w1064 VM. That snapshot is created automatically by the TestBot. Currently this snapshot opens on the "create a Windows account" fullscreen dialog, the one with the following title: Let's finish setting up your device It seems this dialog 'pops up' automatically on boot if one does not provide a Microsoft account when installing Windows. When that happens is hard to predict, Windows seems to wait a few days or reboots before doing. Furthermore something WineTest does seems to make this dialog go away because it's not visible in the final WineTest screenshot. However it is visible if one runs a single test such as ntdll:exception. It's not entirely clear if this dialog is interfering with some tests but its presence is definitely unwanted. -- 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 6

[Bug 47847] New: Disable Windows 10's "privacy wizard" after locale change
by WineHQ Bugzilla 19 Dec '22

19 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=47847 Bug ID: 47847 Summary: Disable Windows 10's "privacy wizard" after locale change Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The TestBot can automatically set up locale-specific live snapshots (after the locale has been manually installed, see point 1 of bug 47804). However on Windows 10 the mandatory reboot is sometimes followed by a wizard asking a bunch of questions like whether to use audio speech recognition, what kind of reports to send Microsoft, etc. I think this is the "Choose your Privacy Settings" wizard. Of course that breaks the snapshot creation since the TestBot cannot answer these questions, fails to detect they are even being asked (because TestAgentd is already running in the background), and creates a snapshot of the half-baked state. So one question is: how can one prevent Windows from putting up this wizard? But then, while I had this wizard for the French locale, I did not get it for Arabic. Would it perchance only happen for European locales? If so the pain may be bearable. -- 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 9

[Bug 51411] New: Add a mixed locale Windows test configuration.
by WineHQ Bugzilla 19 Dec '22

19 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=51411 Bug ID: 51411 Summary: Add a mixed locale Windows test configuration. Product: Wine-Testbot 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: --- The TestBot's locale test configurations usually have a matching set of locales for SystemDefaultLCID, USystemPreferredUILanguages, UserDefaultUILanguage and ThreadUILanguage. For instance for French we have: SystemDefaultLCID 040c UserDefaultLCID 0409 ThreadLocale 0409 SystemPreferredUILanguages 040C,0409 UserDefaultUILanguage 040c ThreadUILanguage 040c As a result tests can substitute GetSystemDefaultLCID() for GetThreadUILanguage() and get away with it. In turn this allows Wine to substitute these too without causing the tests to fail (see for instance mlang:mlang, bug 51410). To avoid this the TestBot needs a test configuration where all the important locale settings are different so these issues are detected immediately. -- 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 51451] New: Many Windows 10 VMs are incompletely localized
by WineHQ Bugzilla 19 Dec '22

19 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=51451 Bug ID: 51451 Summary: Many Windows 10 VMs are incompletely localized Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The localized w10pro64* VMs don't have the right UserDefaultLCID and are sometimes missing even more: w10pro64 fr_FR SystemDefaultLCID 040c UserDefaultLCID 0409 <--- should be 040c ThreadLocale 0409 ??? SystemPreferredUILanguages 040C,0409 UserDefaultUILanguage 040c ThreadUILanguage 040c w10pro64 ar_MA SystemDefaultLCID 0c01 UserDefaultLCID 0409 <--- should be 0c01 ThreadLocale 0409 ??? SystemPreferredUILanguages 0409 <--- should contain 0c01 UserDefaultUILanguage 0409 <--- should be 0c01 ThreadUILanguage 0409 <--- should be 0c01 w10pro64 he_IL UserDefaultLCID 0409 <--- should be 40d w10pro64 hi_IN Being a Unicode-only language means setting the system locale to Hindi was not possible in older Windows versions (up to early Windows 10). Now it is but it's considered Beta and uses the UTF-8 encoding in ANSI APIs. So it's not clear if it should be changed (and how to do it programmatically). SystemDefaultLCID 0409 <--- Unicode-only language UserDefaultLCID 0409 <--- should be 0439 ThreadLocale 0409 ??? SystemPreferredUILanguages 0439,0409 UserDefaultUILanguage 0439 ThreadUILanguage 0439 w10pro64 ja_JP UserDefaultLCID 0409 <--- should be 411 w10pro64 ko_KO UserDefaultLCID 0409 <--- should be 412 w10pro64 pt_BR UserDefaultLCID 0409 <--- should be 416 w10pro64 ru_RU UserDefaultLCID 0409 <--- should be 419 w10pro64 zh_CN UserDefaultLCID 0409 <--- should be 804 This prevents testing how Windows behaves when formatting and parsing their currencies in oleaut32:varformat for instance. Strangely enough the w7u* VMs don't have this issue: w7u de_DE SystemDefaultLCID 0407 UserDefaultLCID 0407 ThreadLocale 0407 SystemPreferredUILanguages 0407 UserDefaultUILanguage 0407 ThreadUILanguage 0407 -- 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