Description of problem: starting Chromium 79 (and also google-chrome-stable 79) through a ssh tunnel gives a blank (white) window. Actually it is possible to click on some buttons if one is able to locate them with the mouse without seeing them. By Clicking on "Chromium Web Browser" in the top bar of the screen, it is possible to open a new window which is visible, but the window has not loaded any personal configuration (bookmarks, extensions etc.) Version-Release number of selected component (if applicable): chromium-79.0.3945.79-1.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. ssh -X -f user@host "/usr/bin/chromium-browser" 2. a blank (white) window opens 3. click on "Chromium Web Browser" in the top bar of the screen and select "Open a New Window" 4. a normal (visible) chromium window opens, but all personal configuration (bookmarks, extensions etc.) is not loaded Actual results: a blank (white) window opens first, it is possible to open a second window but without all personal configuration (bookmarks, extensions etc.) Expected results: a visible window is opened and all personal configuration is loaded. Additional info: chromium 78 works fine (as it has always done) over an ssh tunnel. See also https://support.google.com/chrome/thread/23330705?hl=en
You might want to open a bug with chromium upstream here: https://bugs.chromium.org/p/chromium/issues/list The code diff between 78 and 79 is rather large, and I'm not sure where to even start digging into what would cause X11 forwarding to break.
Upstream chromium bug "Issue 1026950: Regression: displaying over ssh forwarded X11 shows only grey window" https://bugs.chromium.org/p/chromium/issues/detail?id=1026950 according to this, the bug persists also in Google Chrome 80.0.3987.16 beta
Workaround according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949440 Bug seems to be related to MIT-SHM management Works for me right now as follows: - on the target machine install gcc and libX11-devel - download XlibNoSHM.c from above link (at the bottom of the page) - compile (always on target machine) with gcc -shared -fPIC -o XlibNoSHM.so XlibNoSHM.c - start chrome from the client on the target machine with ssh -X -f user@target "LD_PRELOAD='libdl.so ./XlibNoSHM.so' /usr/bin/google-chrome-stable"
The bug persists with google-chrome-stable-80.0.3987.87-1 , the above workaround still works.
With google-chrome-stable-81.0.4044.129-1.x86_64 it is necessary to add also the option --no-sandbox which makes it quite unsafe to use.
Just found another workaround, google-chrome-stable-81.0.4044.129-1.x86_64 starts with ssh -X -f user@target "LD_PRELOAD='libdl.so ./XlibNoSHM.so' /usr/bin/google-chrome-stable --use-gl=swiftshader" as far as I understand, swiftshader is a "high-performance CPU-based implementation of the Vulkan and OpenGL ES graphics APIs, its goal is to provide hardware independence for advanced 3D graphics ... act as drop-in replacements for graphics drivers" (from GitHub) which could mean in some cases worse graphic performances.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still working only with ssh -X -f user@target "LD_PRELOAD='libdl.so ./XlibNoSHM.so' /usr/bin/google-chrome-stable --use-gl=egl"
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.