https://bugs.winehq.org/show_bug.cgi?id=43415
Bug ID: 43415 Summary: All versions of Google Chrome fail to display a webpage Product: Wine Version: 2.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: arnfranke@yahoo.com Distribution: ---
Created attachment 58770 --> https://bugs.winehq.org/attachment.cgi?id=58770 Backtrace for an error Chrome 59 32-bit threw in Win7 mode
All versions of Google Chrome fail to display a webpage.
Versions tested: 1.0.154.59, "chrome32_49.0.2623.75", "chrome64_49.0.2623.75", "Chrome-48.0.2564.97", "Chrome64_48.0.2564.109", "chrome32_50.0.2661.75", "chrome64_50.0.2661.75", "chrome32_55.0.2883.75", "chrome32_58.0.3029.96", "chrome64_58.0.3029.96", "chrome32_59.0.3071.86", "chrome64_59.0.3071.86".
Wine versions tested: 2.12, 2.13
AppDB page: https://appdb.winehq.org/objectManager.php?sClass=application&iId=8177
I really don't have many details about this problem, but it should be easy to reproduce.
https://bugs.winehq.org/show_bug.cgi?id=43415
Aaron Franke arnfranke@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #1 from Aaron Franke arnfranke@yahoo.com --- Created attachment 58771 --> https://bugs.winehq.org/attachment.cgi?id=58771 Backtrace for an error Chrome 59 32-bit threw in WinXP mode
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #2 from Aaron Franke arnfranke@yahoo.com --- Created attachment 58772 --> https://bugs.winehq.org/attachment.cgi?id=58772 Backtrace for an error Chrome 59 64-bit threw in Win7 mode
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #3 from Aaron Franke arnfranke@yahoo.com --- Created attachment 58773 --> https://bugs.winehq.org/attachment.cgi?id=58773 Log of Chrome 1.0.154.59 in Windows XP mode
https://bugs.winehq.org/show_bug.cgi?id=43415
Aaron Franke arnfranke@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P4 Severity|normal |major URL| |https://appdb.winehq.org/ob | |jectManager.php?sClass=appl | |ication&iId=8177
https://bugs.winehq.org/show_bug.cgi?id=43415
Aaron Franke arnfranke@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86 |x86-64
https://bugs.winehq.org/show_bug.cgi?id=43415
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- I'd like to test, but how did you get past Bug 43416?
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- Thanks for the update on Bug 43416. I can confirm that it doesn't display anything on any page I try to go to, not even any text.
https://bugs.winehq.org/show_bug.cgi?id=43415
Aaron Franke arnfranke@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|All versions of Google |All versions of Google |Chrome fail to display a |Chrome fail to display any |webpage |and all webpages
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #6 from Aaron Franke arnfranke@yahoo.com --- Probably related: https://bugs.winehq.org/show_bug.cgi?id=39403 which is blocked by https://bugs.winehq.org/show_bug.cgi?id=21232.
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- Agreed. It works with "wine chrome.exe --no-sandbox". Still no fonts, but webpages load fine.
https://bugs.winehq.org/show_bug.cgi?id=43415
Aaron Franke arnfranke@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |21232
https://bugs.winehq.org/show_bug.cgi?id=43415
Aaron Franke arnfranke@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P4 |P3
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #8 from Austin English austinenglish@gmail.com --- (In reply to Aaron Franke from comment #6)
Probably related: https://bugs.winehq.org/show_bug.cgi?id=39403 which is blocked by https://bugs.winehq.org/show_bug.cgi?id=21232.
How is this bug different from those two? It looks to me to be a duplicate.
https://bugs.winehq.org/show_bug.cgi?id=43415
salamander purake salamanderrake@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |salamanderrake@gmail.com
--- Comment #9 from salamander purake salamanderrake@gmail.com --- This bug is the mother of all bugs related to CEF, which includes steam, uplay, and EpicGameslauncher and any that render using CEF. Is there anyone working on it, has anyone had any issues getting chromes stuff to work under wine?
https://bugs.winehq.org/show_bug.cgi?id=43415
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=43415
Johan Gardhage johan.gardhage@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |johan.gardhage@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43415
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shinoyumi456@gmail.com
--- Comment #10 from Anastasius Focht focht@gmx.net --- *** Bug 44716 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=43415
alasky@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alasky@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=43415
winetaste@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetaste@gmx.net
https://bugs.winehq.org/show_bug.cgi?id=43415
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43415 Bug 43415 depends on bug 21232, which changed state.
Bug 21232 Summary: Multiple games and applications (Chromium-based browser engines, Blizzard games, League of Legends) crash due to hooking/anticheat validation (needs syscall thunks in ntdll.dll) https://bugs.winehq.org/show_bug.cgi?id=21232
What |Removed |Added ---------------------------------------------------------------------------- Status|STAGED |RESOLVED Resolution|--- |FIXED
https://bugs.winehq.org/show_bug.cgi?id=43415
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch
--- Comment #11 from mirh mirh@protonmail.ch --- How are we going now? I see a fairly successful test result record with 5.5-staging.
https://bugs.winehq.org/show_bug.cgi?id=43415
minion minion.procyk@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |minion.procyk@gmail.com
--- Comment #12 from minion minion.procyk@gmail.com --- i'm having trouble seeing any pages as well using latest wine with or without staging patches. just a black screen and spam regarding shaders.
-- snip -- 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 05bc:fixme:hlsl_parser:hlsl_lex Unsupported preprocessor #pragma directive at line 10. 0674:fixme:hlsl_parser:hlsl_lex Unsupported preprocessor #pragma directive at line 9. -- snip --
the window itself seems to work as i can press the close button even though i can't see it.
wine --version wine-5.21-69-gb940c5e7c91
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #13 from Fabian Maurer dark.shadow4@web.de --- Newer versions of google chrome have problems with d3d as well, and they might still suffer from bug 49840 (need to retest).
https://bugs.winehq.org/show_bug.cgi?id=43415
lizhenbo litimetal@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |litimetal@gmail.com
--- Comment #14 from lizhenbo litimetal@gmail.com --- (In reply to minion from comment #12)
i'm having trouble seeing any pages as well using latest wine with or without staging patches. just a black screen and spam regarding shaders.
-- snip -- 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 0674:fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. 05bc:fixme:hlsl_parser:hlsl_lex Unsupported preprocessor #pragma directive at line 10. 0674:fixme:hlsl_parser:hlsl_lex Unsupported preprocessor #pragma directive at line 9. -- snip --
the window itself seems to work as i can press the close button even though i can't see it.
wine --version wine-5.21-69-gb940c5e7c91
I have the same issue in wine-6.2 Maybe bug 50696 is caused by this issue (or a dup of this one)
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #15 from lizhenbo litimetal@gmail.com --- Created attachment 69579 --> https://bugs.winehq.org/attachment.cgi?id=69579 WINEDEBUG=+d3dcompiler,+hlsl_parser log
I executed with WINEDEBUG=+d3dcompiler,+hlsl_parser wine chrome.exe
Is this relevant? --snip-- 026c:trace:d3dcompiler:compile_shader Compiler messages: 026c:trace:d3dcompiler:compile_shader "C:\fakepath:41:8: error: syntax error, unexpected KW_CBUFFER\n" 026c:trace:d3dcompiler:compile_shader Shader source: 026c:trace:d3dcompiler:compile_shader "# 1 "C:\fakepath" 1\nstruct VS_OUTPUT\n{\n float4 dx_Position : SV_Position;\n float4 gl_Position : TEXCOORD2;\n float4 v0 : TEXCOORD0;\n float2 v1 : TEXCOORD1;\n};\n\n#pragma warning( disable: 3556 3571 )\nfloat4 vec4_ctor(float x0, float x1, float x2, float x3)\n{\n retu"... --snip--
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #16 from Jactry Zeng jactry92@gmail.com --- (In reply to lizhenbo from comment #15)
Created attachment 69579 [details] WINEDEBUG=+d3dcompiler,+hlsl_parser log
I executed with WINEDEBUG=+d3dcompiler,+hlsl_parser wine chrome.exe
Is this relevant? --snip-- 026c:trace:d3dcompiler:compile_shader Compiler messages: 026c:trace:d3dcompiler:compile_shader "C:\fakepath:41:8: error: syntax error, unexpected KW_CBUFFER\n" 026c:trace:d3dcompiler:compile_shader Shader source: 026c:trace:d3dcompiler:compile_shader "# 1 "C:\fakepath" 1\nstruct VS_OUTPUT\n{\n float4 dx_Position : SV_Position;\n float4 gl_Position : TEXCOORD2;\n float4 v0 : TEXCOORD0;\n float2 v1 : TEXCOORD1;\n};\n\n#pragma warning( disable: 3556 3571 )\nfloat4 vec4_ctor(float x0, float x1, float x2, float x3)\n{\n retu"... --snip--
Does the native d3dcompiler help?
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #17 from lizhenbo litimetal@gmail.com --- (In reply to Jactry Zeng from comment #16)
(In reply to lizhenbo from comment #15)
Created attachment 69579 [details] WINEDEBUG=+d3dcompiler,+hlsl_parser log
I executed with WINEDEBUG=+d3dcompiler,+hlsl_parser wine chrome.exe
Is this relevant? --snip-- 026c:trace:d3dcompiler:compile_shader Compiler messages: 026c:trace:d3dcompiler:compile_shader "C:\fakepath:41:8: error: syntax error, unexpected KW_CBUFFER\n" 026c:trace:d3dcompiler:compile_shader Shader source: 026c:trace:d3dcompiler:compile_shader "# 1 "C:\fakepath" 1\nstruct VS_OUTPUT\n{\n float4 dx_Position : SV_Position;\n float4 gl_Position : TEXCOORD2;\n float4 v0 : TEXCOORD0;\n float2 v1 : TEXCOORD1;\n};\n\n#pragma warning( disable: 3556 3571 )\nfloat4 vec4_ctor(float x0, float x1, float x2, float x3)\n{\n retu"... --snip--
Does the native d3dcompiler help?
Yes!
In winecfg, set d3dcompiler_47.dll as Native (d3dcompiler_47.dll is shipped with Chrome 89.0.4389.82), this bug will be workarounded.
Besides, in appdb, vivid reported that installing DXVK could workaround some issues (likely to be this bug 43415) https://appdb.winehq.org/objectManager.php?sClass=version&iId=37350
https://bugs.winehq.org/show_bug.cgi?id=43415
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #18 from Louis Lenders xerox.xerox2000x@gmail.com --- Created attachment 71718 --> https://bugs.winehq.org/attachment.cgi?id=71718 screenshot
It looks like this bug is now evolved into a d3dcompiler-issue
I tested current version https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F9...
Only needed 'winetricks arial' to get it installed and running to load webpages.
When you explicitely set d3dcompiler_47 to builtin issues appear, see screenshot
0a9c:fixme:d3dcompiler:D3DCompile2 HLSL shader compilation is not yet implemented. 0a9c:fixme:d3dcompiler:D3DCompile2 HLSL shader compilation is not yet implemented.
I think for now setting component d3dcompiler, or resolve as fixed as many issues seem to be fixed ?
https://bugs.winehq.org/show_bug.cgi?id=43415
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d-util Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Severity|major |normal
--- Comment #19 from Louis Lenders xerox.xerox2000x@gmail.com --- setting component
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #20 from Fabian Maurer dark.shadow4@web.de --- Is this still an issue? I tried GoogleChromePortable_118.0.5993.118_online.paf with wine-8.19, and after "winetricks arial" it works fine.
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #21 from Aaron Franke arnfranke@yahoo.com --- It looks like this may have been fixed in Wine 5.18 https://bugs.winehq.org/show_bug.cgi?id=21232
https://bugs.winehq.org/show_bug.cgi?id=43415
--- Comment #22 from Ken Sharp imwellcushtymelike@gmail.com --- Are you saying that it IS fixed?