October 2021 - Wine-bugs - list.winehq.org

[Bug 38756] New: FutureMark SystemInformation diagnostics (.NET 4.0 app) crashes when clicking 'connect' (COM support for 'new' moniker and 'BIND_OPTS3' missing)
by wine-bugs＠winehq.org 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=38756 Bug ID: 38756 Summary: FutureMark SystemInformation diagnostics (.NET 4.0 app) crashes when clicking 'connect' (COM support for 'new' moniker and 'BIND_OPTS3' missing) Product: Wine Version: 1.7.45 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, split off from bug 27185 which is about Wine-Mono. The installer installs the following prerequisites on its own: * DirectX Jun 2010 * Microsoft .NET Framework 4 Client Profile 4.0.30319 * Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219 .NET Framework 4.0 install only works right away if Wine-Mono has been removed prior the install or Wine was built without Mono support as I do. The first problem after installation is bug 15670 --- snip --- Unhandled Exception: System.Windows.Markup.XamlParseException: The invocation of the constructor on type 'Futuremark.PCMark7.PCMark7Gui.WelcomeWindow' that matches the specified binding constraints threw an exception. ---> System.IO.IsolatedStorage.IsolatedStorageException: Unable to create the store directory. (Exception from HRESULT: 0x80131468) at System.IO.IsolatedStorage.IsolatedStorageFile.GetRootDir(IsolatedStorageScope scope, StringHandleOnStack retRootDir) at System.IO.IsolatedStorage.IsolatedStorageFile.InitGlobalsNonRoamingUser(IsolatedStorageScope scope) at System.IO.IsolatedStorage.IsolatedStorageFile.GetRootDir(IsolatedStorageScope scope) at System.IO.IsolatedStorage.IsolatedStorageFile.GetGlobalFileIOPerm(IsolatedStorageScope scope) at System.IO.IsolatedStorage.IsolatedStorageFile.Init(IsolatedStorageScope scope) at Futuremark.BenchmarkUtility.Identifier.set_Key(String value) at Futuremark.PCMark7.PCMarkEssence.LicenseManager.ValidateKey(String key, Boolean online) at Futuremark.PCMark7.PCMarkEssence.LicenseManager..ctor(IOnlineMessenger onlineMessenger) at Futuremark.PCMark7.PCMarkEssence.UIController..ctor() at Futuremark.PCMark7.PCMark7Gui.WelcomeWindow..ctor() --- End of inner exception stack trace --- --- snip --- Next problem: --- snip --- 002d:Call user32.MessageBoxW(00000000,0106f914 L"Initializing Futuremark SystemInfo failed.\nPlease verify that version 4.0 or newer is installed properly.",0106fea8 L"PCMark 7 - SystemInfo failure",00000000) ret=0545b07f --- snip --- http://community.futuremark.com/forum/showthread.php?181303-Problem-futurem… Looks like a separate (COM) service component. Trying to use the diagnosis tool which ought to connect to the service also fails: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Futuremark/Futuremark SystemInfo $ wine ./FMSIDiag.exe ... fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000401,(nil),0x0001,0x00000000,0x33bcac,(nil)): stub err:eventlog:ReportEventW L"Application: FMSIDiag.exe\nFramework Version: v4.0.30319\nDescription: The application requested process termination through System.Environment.FailFast(string message).\nMessage: Unrecoverable system error.\nStack:\n at System.Environment.FailFast(System.String)\n at MS.Internal.Invariant.FailFa"... fixme:advapi:DeregisterEventSource (0xcafe4242) stub --- snip --- -> bug 32323 ('winetricks -q corefonts') Running it again: --- snip --- ... Unhandled Exception: FMSIDiag.SystemInfoException: SystemInfo initialization failed. at FMSIDiag.SystemInfo2.Init(Boolean tryElevate) at FMSIDiag.SystemInfo2.Init() at FMSIDiag.Core.Connect() at FMSIDiag.MainWindow.buttonBasicConnect_Click(Object sender, RoutedEventArgs e) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e) at System.Windows.Controls.Primitives.ButtonBase.OnClick() at System.Windows.Controls.Button.OnClick() --- snip --- First-chance exception caught with managed debugger: --- snip --- Child SP IP Call Site 0559ce14 7b8455e1 [HelperMethodFrame: 0559ce14] 0559ce64 05039207 DomainBoundILStubClass.IL_STUB_PInvoke(System.String, BIND_OPTS3 ByRef, System.Guid) 0559ce68 0503904c [InlinedCallFrame: 0559ce68] FMSIDiag.UACManager.CoGetObject(System.String, BIND_OPTS3 ByRef, System.Guid) 0559cf38 0503904c FMSIDiag.UACManager.LaunchCOMObject(System.Guid, System.Guid) 0559cfac 05038dbd FMSIDiag.SystemInfo2.ThreadInit(Boolean) ... --- snip --- Relevant part of trace log: --- snip --- 0040:Call ole32.CoGetObject(00dce0ac L"new:{f9c82199-b002-41b4-8b00-0f1eca89425f}",054bce6c,054bcee8,054bce64) ret=053a0e78 ... 0040:Ret ole32.CoGetObject() retval=80070057 ret=053a0e78 ... 0040:trace:seh:raise_exception code=e0434352 flags=1 addr=0x7b8455e1 ip=7b8455e1 tid=0040 0040:trace:seh:raise_exception info[0]=80070057 0040:trace:seh:raise_exception info[1]=00000000 0040:trace:seh:raise_exception info[2]=00000000 0040:trace:seh:raise_exception info[3]=00000000 0040:trace:seh:raise_exception info[4]=79140000 0040:trace:seh:raise_exception eax=7b83247d ebx=00000005 ecx=00000014 edx=054bcc44 esi=054bcce4 edi=054bccb0 0040:trace:seh:raise_exception ebp=054bcc88 esp=054bcc24 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00200283 0040:trace:seh:call_vectored_handlers calling handler at 0x791f5a7c code=e0434352 flags=1 ... --- snip --- Relevant .NET code: --- snip --- // FMSIDiag.SystemInfo2 private void ThreadInit(bool tryElevate) { if (this.m_FMSI != null) { return; } this.m_FMSI = UACManager.LaunchCOMObject( new Guid("F9C82199-B002-41B4-8B00-0F1ECA89425F"), new Guid("93382A45-8441-4A42-BE09-95C7D0550B94")); if (this.m_FMSI != null) { this.m_FuturemarkSystemInfo = (IFuturemarkSystemInfo2)this.m_FMSI; this.m_FuturemarkSystemInfoVersion = (IFuturemarkSystemInfoVersion)this.m_FMSI; this.m_FuturemarkSystemInfoMultiGPU = (IFuturemarkSystemInfoMultiGPU)this.m_FMSI; this.m_FuturemarkSystemInfoQuery = (IFuturemarkSystemInfoQuery)this.m_FMSI; this.m_FuturemarkSystemInfoLegacyQuery = (IFuturemarkSystemInfoLegacyQuery)this.m_FMSI; this.m_FuturemarkSystemInfoQueryStorage = (IFuturemarkSystemInfoQueryStorage)this.m_FMSI; this.m_FuturemarkSystemInfoMonitoring = (IFuturemarkSystemInfoMonitoring)this.m_FMSI; this.m_Initialized = true; } } ... // FMSIDiag.UACManager [return: MarshalAs(UnmanagedType.Interface)] public static object LaunchCOMObject(Guid Clsid, Guid InterfaceID) { string str = Clsid.ToString("B"); string pszName = "new:" + str; UACManager.BIND_OPTS3 bIND_OPTS = default(UACManager.BIND_OPTS3); bIND_OPTS.cbStruct = (uint)Marshal.SizeOf(bIND_OPTS); bIND_OPTS.hwnd = IntPtr.Zero; bIND_OPTS.dwClassContext = 4u; object result = null; try { result = UACManager.CoGetObject(pszName, ref bIND_OPTS, InterfaceID); } catch (Exception) { result = null; } return result; } --- snip --- Registry entry of COM server: --- snip --- REGEDIT4 [HKEY_CLASSES_ROOT\CLSID\{F9C82199-B002-41B4-8B00-0F1ECA89425F}] @="Futuremark SystemInfo v2 Class" "AppID"="{1BF1C030-CE12-4A8A-A4E1-EDDCE7176799}" "LocalizedString"="@C:\\Program Files\\Futuremark\\Futuremark SystemInfo\\FMSISvc.exe,-101" [HKEY_CLASSES_ROOT\CLSID\{F9C82199-B002-41B4-8B00-0F1ECA89425F}\LocalService] @="\"C:\\Program Files\\Futuremark\\Futuremark SystemInfo\\FMSISvc.exe\"" [HKEY_CLASSES_ROOT\CLSID\{F9C82199-B002-41B4-8B00-0F1ECA89425F}\ProgID] @="FuturemarkSystemInfo2.1" [HKEY_CLASSES_ROOT\CLSID\{F9C82199-B002-41B4-8B00-0F1ECA89425F}\Programmable] [HKEY_CLASSES_ROOT\CLSID\{F9C82199-B002-41B4-8B00-0F1ECA89425F}\TypeLib] @="{0E985ACA-E998-460F-B705-8436E606F78C}" [HKEY_CLASSES_ROOT\CLSID\{F9C82199-B002-41B4-8B00-0F1ECA89425F}\VersionIndependentProgID] @="FuturemarkSystemInfo2" --- snip --- Article: http://chrison.net/UACElevationInManagedCodeStartingElevatedCOMComponents.a… ("UAC Elevation in Managed Code: Starting Elevated COM Components") which is courtesy of: https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/5706957f-b96b… Although the app .NET class is called 'UACManager' the code seems to contradict this. The elevation moniker syntax is not used: MSDN: https://msdn.microsoft.com/en-us/library/windows/desktop/ms679687%28v=vs.85… --- snip --- Elevation:Administrator!new:{guid} Elevation:Highest!new:{guid} --- snip --- What's new is the use of the 'new' moniker though: http://thrysoee.dk/InsideCOM+/ch11e.htm ("The New Moniker") and BIND_OPTS3: MSDN: https://msdn.microsoft.com/en-us/library/windows/desktop/aa746553%28v=vs.85… $ sha1sum PCMark_7_v104_installer.zip 1a13ea91439ae4d81a153ca777ecb74e42394015 PCMark_7_v104_installer.zip $ du -sh PCMark_7_v104_installer.zip 304M PCMark_7_v104_installer.zip $ wine --version wine-1.7.45 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 8

[Bug 42243] New: 3DMark11 installer crashes with access violation in Freetype because font data is released too early
by wine-bugs＠winehq.org 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=42243 Bug ID: 42243 Summary: 3DMark11 installer crashes with access violation in Freetype because font data is released too early Product: Wine Version: 2.0-rc5 Hardware: x86 URL: https://ftp.computerbase.de/dl-856/UeQSx5zAJUXrxV_B1iD Xuw/1484758851/3DMark11-v1-0-132.zip OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)winehq.org Reporter: sebastian(a)fds-team.de CC: bunglehead(a)gmail.com Distribution: --- The installer needs a Wine prefix with dotnet40 and Windows version set to Windows 7. On one of my machines everything works as expected, on the other one I'm getting an access violation in Freetype. Relevant lines from the terminal output: --- snip --- 003a:trace:dwrite:init_freetype FreeType version is 2.6.3 [...] 003a:trace:dwrite:dwritefontface_GetGdiCompatibleGlyphMetrics (0x101499f8)->(15.00 1.00 (nil) 0 0x11fb140 8 0x11fb15c 0) 003a:trace:dwrite:dwritefontface_GetDesignGlyphMetrics (0x101499f8)->(0x11fb140 1 0x438c9d4 0) 003a:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7db2a994 ip=7db2a994 tid=003a 003a:trace:seh:raise_exception info[0]=00000000 003a:trace:seh:raise_exception info[1]=0204d620 003a:trace:seh:raise_exception eax=0204d620 ebx=00000173 ecx=7dbb8000 edx=00000000 esi=7db7f840 edi=7db27800 003a:trace:seh:raise_exception ebp=7cccc420 esp=0438c530 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00210207 [...] wine: Unhandled page fault on read access to 0x0204d620 at address 0x7db2a994 (thread 003a), starting debugger... [...] Backtrace: =>0 0x7db2a994 TT_RunIns+0xf4() in libfreetype.so.6 (0x7cccc420) 1 0x7db2de84 in libfreetype.so.6 (+0x28e83) (0x0438c6a4) 2 0x7db2dfb4 in libfreetype.so.6 (+0x28fb3) (0x7cc867a0) 3 0x7db17c58 FT_Load_Glyph+0x187() in libfreetype.so.6 (0x0438c7e8) 4 0x7db684e6 in libfreetype.so.6 (+0x634e5) (0x7cc91be0) 5 0x7db6827f in libfreetype.so.6 (+0x6327e) (0x7cc00ee0) 6 0x7db67984 in libfreetype.so.6 (+0x62983) (0x7cc9b448) 7 0x7db692bb FTC_ImageCache_Lookup+0x21a() in libfreetype.so.6 (0x7cc9b448) 8 0x7cf4f18b freetype_get_glyph_advance+0x91(fontface=0x101499f8, emSize=15.000000, index=0x26, mode=DWRITE_MEASURING_MODE_GDI_CLASSIC) [.../dlls/dwrite/freetype.c:798] in dwrite (0x0438c9a8) --- snip --- Further debugging revealed that the actual problem is in face_requester(). The memory address lies within a range previously passed to FT_New_Memory_Face. --- snip --- hr = IDWriteFontFileStream_ReadFileFragment(stream, &data_ptr, 0, data_size, &context); if (FAILED(hr)) { fterror = FT_Err_Invalid_Stream_Read; goto fail; } index = IDWriteFontFace_GetIndex(fontface); fterror = pFT_New_Memory_Face(library, data_ptr, data_size, index, face); IDWriteFontFileStream_ReleaseFileFragment(stream, context); --- snip --- The file fragment is released immediately after creating the new font face, which should not be a problem for the builtin implementation. In this case however it seems that the application is using its own implementation which deallocates memory in ReleaseFileFragment. The freetype docs say: """You must not deallocate the memory before calling FT_Done_Face.""" Commenting out the line with IDWriteFontFileStream_ReleaseFileFragment fixes the crash. $ sha256sum 3DMark11-v1-0-132.zip 0a375c6b024deddf3f805ec26a308eaa6b1f6a4f898fe972407d40dcee4ca078 3DMark11-v1-0-132.zip Tested with Wine version 2.0-rc5. -- 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 6

[Bug 38411] New: Infinite wait for start
by wine-bugs＠winehq.org 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=38411 Bug ID: 38411 Summary: Infinite wait for start Product: Wine Version: 1.7.40 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru err:ntdll:RtlpWaitForCriticalSection section 0x9f0060 "heap.c: HEAP.critSection" wait timed out in thread 0063, blocked by 005d, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7bc9801c "loader.c: loader_section" wait timed out in thread 0050, blocked by 0063, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7bc9801c "loader.c: loader_section" wait timed out in thread 0051, blocked by 0063, retrying (60 sec) What is the reason to wait 60sec again and again if we have emulated hardware? -- 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 27

[Bug 43857] New: WoW PTR 7.3.2 crashes on startup
by wine-bugs＠winehq.org 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=43857 Bug ID: 43857 Summary: WoW PTR 7.3.2 crashes on startup Product: Wine Version: 2.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 59417 --> https://bugs.winehq.org/attachment.cgi?id=59417 Picture of the error window When i start the current WoW PTR client it takes quite some time to display anything and 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.

2 6

[Bug 47889] New: user32:edit fails on Win 8.1 since the RX 460 GPU got installed
by WineHQ Bugzilla 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=47889 Bug ID: 47889 Summary: user32:edit fails on Win 8.1 since the RX 460 GPU got installed Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:edit fails on cw-rx460 / Windows 8.1 since the RX 460 GPU got installed (2019-09-25): edit.c:3127: Test failed: expected 1, got 0 edit.c:3129: Test failed: expected 1, got 0 edit.c:3131: Test failed: expected 005E0054, got 00000000 edit.c:3133: Test failed: expected 1, got 0 edit.c:3139: Test failed: got 21 edit.c:3145: Test failed: got 21 https://test.winehq.org/data/tests/user32:edit.html See also bug 47888 about the user32:clipboard failures which started at the same time. -- 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 51686] New: Battle.net: No text is displayed in GUIs
by WineHQ Bugzilla 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=51686 Bug ID: 51686 Summary: Battle.net: No text is displayed in GUIs Product: Wine-staging Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I have fresh Fedora 34 and wine staging 6.15 installation and fresh x64 Prefix. Only winetricks override is for corefonts. When starting Battle/net Launcher or Installer, I see no text; just windows and pictures/graphics. -- 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 51954] New: Adobe Lightroom Classic 11.0 needs api-ms-win-core-winrt-error-l1-1-0.dll.RoOriginateError
by WineHQ Bugzilla 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=51954 Bug ID: 51954 Summary: Adobe Lightroom Classic 11.0 needs api-ms-win-core-winrt-error-l1-1-0.dll.RoOriginateErro r Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: bugs(a)bzatek.net Distribution: --- Clean prefix, env set to Win10, only vcrun2015 (tried also vcrun2019) installed that is needed by Lightroom. > wine: Call from 000000007B03A40F to unimplemented function api-ms-win-core-winrt-error-l1-1-0.dll.RoOriginateError, aborting > wine: Unimplemented function api-ms-win-core-winrt-error-l1-1-0.dll.RoOriginateError called at address 000000007B03A40F (thread 0114), starting debugger... > Unhandled exception: unimplemented function api-ms-win-core-winrt-error-l1-1-0.dll.RoOriginateError called in 64-bit code (0x000000007b03a40 ... Erm, found a random api-ms-win-core-winrt-error-l1-1-0.dll (version 6.2.8400.0) in Google (Eh...) and Lightroom works just like before. -- 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 30623] New: iTunes 10.6.1 UI corruption
by wine-bugs＠winehq.org 20 Nov '21

20 Nov '21

http://bugs.winehq.org/show_bug.cgi?id=30623 Bug #: 30623 Summary: iTunes 10.6.1 UI corruption Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: medasaro(a)comcast.net Classification: Unclassified Created attachment 40098 --> http://bugs.winehq.org/attachment.cgi?id=40098 iTunes 10.6.1 Running on Wine 1.5.3 showing UI corruption Install iTunes 10.6.1 into a clean wine prefix using the latest wine version and no changes to the default setup (Windows version set to WINXP). iTunes will install and launch, but the main window is mostly black and missing buttons / features. See the attached screenshot. -- 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 16

[Bug 51005] New: Game properties windows on steam do not longer opens without corefonts
by WineHQ Bugzilla 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=51005 Bug ID: 51005 Summary: Game properties windows on steam do not longer opens without corefonts Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andy86(a)fastwebnet.it Distribution: --- When I do a right click then select properties on a game steam nothing happens anymore if I used clean prefix without corefonts. Normally a steam window should open, and I should be able to select "general, updates, local files, etc..." and run e.g. the cache verification. Trying to look in the wine terminal output I found that when you click on that entry nothing is printed out, also trying to make log more verbose than default. I can't say how long this has been happening as I don't make much use of it, but I've gone back to wine 5.1 without finding any working versions and it seems strange that it hasn't worked for so long and after one of last steam updates the properties window has change its appearance, so I think this bug may has been introduced as a result of an update from steam. -- 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

[Bug 51253] New: Overwatch video settings don't display high refresh rate
by WineHQ Bugzilla 20 Nov '21

20 Nov '21

https://bugs.winehq.org/show_bug.cgi?id=51253 Bug ID: 51253 Summary: Overwatch video settings don't display high refresh rate Product: Wine-staging Version: 6.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b1779506(a)trbvn.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Running here Overwatch on screen with 120HZ, which works fine on Windows 10. However, on wine-staging-6.10, on video settings, it only displays the standard 1920x1080 at 50Hz, with frequency slightly increasing when resolution is reduced. In Windows it has the FHD at 120Hz. Nvidia graphics card here. -- 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