wine-bugs February 2020

wine-bugs@winehq.org

1 participants
7246 discussions

[Bug 44146] New: Crysis 2: DX11 is a slideshow
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44146 Bug ID: 44146 Summary: Crysis 2: DX11 is a slideshow Product: Wine Version: 3.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Hi, trying to play Crysis 2 with DX11 is actually impossible, it is a complete slideshow. Switching from DX9 to DX11 the FPS drop from ~ 40 to ~ 8 fps. Tons of fixmes are spit out: 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. 0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #24: 0048:fixme:d3d_shader:print_glsl_info_log Vertex info 0048:fixme:d3d_shader:print_glsl_info_log ----------- 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[8]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[10]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[12]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[13]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[14]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[15]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[16]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[17]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[18]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[19]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[20]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[21]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[22]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[23]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[24]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[25]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[26]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[27]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[28]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[29]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[30]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0048:fixme:d3d_shader:print_glsl_info_log Fragment info 0048:fixme:d3d_shader:print_glsl_info_log ------------- 0048:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "R0.yzw" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. 0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x800000c2. 0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. 0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #27: 0048:fixme:d3d_shader:print_glsl_info_log Vertex info 0048:fixme:d3d_shader:print_glsl_info_log ----------- 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1].zw" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[8]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[10]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[12]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[13]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[14]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[15]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[16]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[17]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[18]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[19]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[20]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[21]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[22]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[23]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[24]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[25]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[26]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[27]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[28]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[29]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[30]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0048:fixme:d3d_shader:print_glsl_info_log Fragment info 0048:fixme:d3d_shader:print_glsl_info_log ------------- 0048:fixme:d3d_shader:print_glsl_info_log 0(26) : warning C7050: "R0.yzw" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. My GPU: Nvidia GTX 970 (384.98) Memory: 16GB CPU: Core i5 3570k Opensuse Tumbleweed, latest Snapshot Many thanks ! Christian -- 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 13

[Bug 22755] New: Regression : win16 installer program of "de rouck" freeze
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=22755 Summary: Regression : win16 installer program of "de rouck" freeze Product: Wine Version: 0.9.31. Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: vincent.hardy.be(a)gmail.com Created an attachment (id=28058) --> (http://bugs.winehq.org/attachment.cgi?id=28058) wine-1.1.31 screenshot It works with wine-1.1.30. With wine-1.1.31, see screenshot Regression test says : 3b1186de5aeabd261e70dab8b78a730030075ca1 is the first bad commit commit 3b1186de5aeabd261e70dab8b78a730030075ca1 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Oct 7 17:14:10 2009 +0200 kernel32: Move the 16-bit string functions to kernel16.c. :040000 040000 3412021b8c21c250ee3ccc60ce31c3f3f9365c50 3c5be0f4e2330e28e86e4b839447d40d88bf42f3 M dlls -- 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 11

[Bug 47189] New: Vortex doesn't start
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=47189 Bug ID: 47189 Summary: Vortex doesn't start Product: Wine Version: 4.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: logicalman101(a)gmail.com Distribution: --- Vortex doesn't run past installation phase no matter what version of dotnet I have installed. -- 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 22

[Bug 44822] New: Warframe can't update / game can't run
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44822 Bug ID: 44822 Summary: Warframe can't update / game can't run Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Warframe can't get past updating process, hence game won't start. This is a fresh install. Installs fine via steam. Starts with workarounds: winetricks: d3dx9 wininet winhttp xact hosts corefonts fontfix vcrun2015 Updating fails with the message "Update Failed! The content servers are temporarily" No workarounds have fixed this so far. Attempts to install other Visual C++ packages haven't helped. Various DLL overrides haven't helped. -- 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 13

[Bug 33131] New: taskkill doesn't support /fi (filtering) option
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=33131 Bug #: 33131 Summary: taskkill doesn't support /fi (filtering) option Product: Wine Version: 1.5.25 Platform: x86-64 OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Blocks: 33130 Classification: Unclassified Noticed while looking at bug 33130 0067:Call KERNEL32.CreateProcessW(00000000,008fcb00 L"C:\\windows\\system32\\taskkill.exe /F /Fi \"MODULES eq AutoupdatePlugin.cpl\" /T",00000000,00000000,00000000,00000400,00000000,00000000,008fb1fc,008fb240) ret=7e4d517f -- 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 3

[Bug 24169] New: QuarkXPress version 8.x hangs on start (missing double quoting of browser path in HKCR\htmlfile\shell\open\command)
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=24169 Summary: QuarkXPress version 8.x hangs on start (missing double quoting of browser path in HKCR\htmlfile\shell\open\command) Product: Wine Version: 1.3.1 Platform: x86 URL: http://downloads.quark.com/Details.aspx?fid=163&&mid=2 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, someone in appdb reported QuarkXPress version 8.x (2010 version) hangs on start. Downloaded a 60-day trial ... it does indeed - due to a Wine shortcoming and an application bug. ;-) Basically the app retrieves default browser setting from registry and does some parsing to extract browser (unquoting and splitting '\' '/' path delimiter). Their parsing is broken in a way that it can't cope with missing double quotes around browser path leading to endless looping. HKEY_CLASSES_ROOT\htmlfile\shell\open\command -> C:\windows\system32\winebrowser.exe -nohome With the browser path in double quotes, QuarkXPress 8 starts fine. "C:\windows\system32\winebrowser.exe" -nohome The quoting is most likely present in Windows as the app would loop there too without. Regards -- 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 47584] New: Ryzen APU Device ID
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=47584 Bug ID: 47584 Summary: Ryzen APU Device ID Product: Wine Version: 4.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: vasthusya(a)gmail.com Distribution: --- Created attachment 64991 --> https://bugs.winehq.org/attachment.cgi?id=64991 Add Ryzen APU device IDs. The GPU description table is missing Ryzen APU device IDs. 0x15dd : Raven Ridge 0x15d8 : Picasso -- 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 3

[Bug 31033] New: Multiple apps need IWbemServices::GetObject to retrieve WMI class instances
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=31033 Bug #: 31033 Summary: Multiple apps need IWbemServices::GetObject to retrieve WMI class instances Product: Wine Version: 1.5.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: wmi&wbemprox AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, continuation of bug 20651 Multiple apps still fail to query for WMI classes/properties because IWbemServices::GetObject method is not implemented (they use a different method). One app is bug 28682 (Ragnarok downloader) Example .NET code: --- snip --- ManagementClass class2 = new ManagementClass("Win32_Processor"); foreach (ManagementObject obj2 in class2.GetInstances()) { if (str == string.Empty) { str = obj2.Properties["ProcessorId"].Value.ToString(); } } --- snip --- MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/aa392109%28v=vs.85%… Regards -- 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 8

[Bug 24225] New: provide "taskkill" command line tool to aid installers (Impulse installer and more)
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=24225 Summary: provide "taskkill" command line tool to aid installers (Impulse installer and more) Product: Wine Version: 1.3.1 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, various installers use "taskkill" command line tool to terminate running processes, preventing possible sharing/update problems with components to be installed. --- snip --- wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" --- snip --- Trace logs for "Impulse" installer as example: --- snip --- 0034:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulse.exe",00000000,00000000,00000000,00000010,00000000,00000000,0108e980,0108e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 0034:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... 0037:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulsedock.exe",00000000,00000000,00000000,00000010,00000000,00000000,0118e980,0118e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 0037:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... 003a:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulsemini.exe",00000000,00000000,00000000,00000010,00000000,00000000,00e5e980,00e5e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 003a:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... 003d:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulsenow.exe",00000000,00000000,00000000,00000010,00000000,00000000,0108e980,0108e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 003d:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... --- snip --- Wine should provide such a tool to aid installers. Reference: http://technet.microsoft.com/en-us/library/bb491009.aspx Regards -- 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 5

[Bug 32758] New: TurboTax 2012 fails to run update service
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=32758 Bug #: 32758 Summary: TurboTax 2012 fails to run update service Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: focht(a)gmx.net Depends on: 27991 Classification: Unclassified Using wine-1.5.22, you'll need to workaround bug 27991, and install dotnet40 with winetricks. The installer will then work fine. Try to start it, and you'll get 3 errors on start about the update service not working. The relevant turbotax help links: http://turbotax.intuit.com/support/iq/Update-Product/Error-5639--Can-t-Conf… http://turbotax.intuit.com/support/iq/Connectivity-Errors/Error-5640--Can-t… stdout shows: Operation is not supported on this platform. 3 times, which is probably related. -- 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 35

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 February 2020