wine-bugs May 2022

wine-bugs@winehq.org

1 participants
3882 discussions

[Bug 40250] New: Stunt GP too fast timer for stunts, waterfall/screen animation and starting screens
by wine-bugs＠winehq.org 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=40250 Bug ID: 40250 Summary: Stunt GP too fast timer for stunts, waterfall/screen animation and starting screens Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 10mkudela(a)gmail.com Distribution: --- In the game time frame required to press Shift key to make stunt is much smaller then in Windows. Also waterfall animation and loading screens are much faster then in Windows. Everything else is at the same speed. One additional animation is faster as well: speed of the text on screen in Germany location is faster as well, but it's speed is changing from what I have noticed. There is probably a timer somewhere that is ticking faster then it should be, and that is used by all those elements. This bug was tested on 1.9.4 version of Wine, but it is also present on older versions. -- 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 9

[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 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

[Bug 12159] New: Alt-click moves the windows instead of giving access to alternate functionalities in Photoshop Cs2
by wine-bugs＠winehq.org 18 Dec '22

18 Dec '22

http://bugs.winehq.org/show_bug.cgi?id=12159 Summary: Alt-click moves the windows instead of giving access to alternate functionalities in Photoshop Cs2 Product: Wine Version: 0.9.58. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mariejoaile(a)gmail.com Steps to reproduce: 1- Open Photoshop 2- Create a new document or open one 3- Pick a selection tool or clone or any of the tool making use of an alternate function using alt 4- Try to use this alt-click option and instead of for instance for the select tool, deselecting, it will move the window. This action is very important because there is no other way to use certain of Photoshop's tool, making tools like clone and healing useless. -- 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 4

[Bug 41784] New: Wine error under LinuxMint 17.3 after running PDF24 Creator
by wine-bugs＠winehq.org 16 Dec '22

16 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=41784 Bug ID: 41784 Summary: Wine error under LinuxMint 17.3 after running PDF24 Creator Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marialvez(a)gmail.com Distribution: --- Created attachment 56219 --> https://bugs.winehq.org/attachment.cgi?id=56219 Using the PDF24 Creator program, in Wine mode and after close the application, my Pc show these bug.- Y work with Linux Mint 17.3 Cinnamon 64-bit Version 2.8.8 Using the PDF24 Creator program, in Wine mode and after close the application, my Pc show these bug.- Y work with Linux Mint 17.3 Cinnamon 64-bit Version 2.8.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.

2 7

[Bug 52930] New: d3dcompiler_47:hlsl_d3d9 fails randomly on Windows
by WineHQ Bugzilla 14 Dec '22

14 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52930 Bug ID: 52930 Summary: d3dcompiler_47:hlsl_d3d9 fails randomly on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 72305 --> https://bugs.winehq.org/attachment.cgi?id=72305 Small patch to apply on top of 58d20aae3772^ to get failures d3dcompiler_47:hlsl_d3d9 fails randomly on Windows 8.1 to 21H2: hlsl_d3d9.c:1691: Test failed: Got unexpected hr 0x88760b59. hlsl_d3d9.c:1692: Test failed: Got unexpected blob. hlsl_d3d9.c:1693: Test failed: Got unexpected errors. https://test.winehq.org/data/patterns.html#d3dcompiler_47:hlsl_d3d9 A bisect against Windows 10 21H1 on cw-gtx560 shows that the failures started with the commit below: commit 58d20aae3772473a90e43ee236b793f0421eecb1 Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Tue Feb 8 19:48:44 2022 +0100 d3dcompiler/tests: Build without -DWINE_NO_LONG_TYPES. Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The patch does not actually make any change that should matter but I have confirmed the bisect result manually: 58d20aae3772^ -> 200 consecutive runs with no failure 58d20aae3772 -> fails after 9 to 33 runs - Applying just the Makefile.in parts and last 4 chunks of hlsl_d3d9.c of that commit is sufficient to get the failures. - Patching only the makefiles is not enough. - I did not try to identify which of the 4 chunks are needed to get failures. They all patch code that's executed after the failure anyway. So there must be some memory corruption that's sensitive to memory layout or some subtle issue with the generated code. I also if(0)ed-out all the other test_xxx() functions, and also if(0)ed-out the tests that preceded the failing one in test_include() but I still get the failure so it's not a case where an ill-advised NULL-behavior test causes memory corruption. -- 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 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