Hello,
Chrome 61 did work fine here, as well as Chromium 61 does (from which I’m writing). Both chromium-stable-62 and chromium-unstable-63 start up but don’t show anything in their tabs, even when I want **chrome://settings/
**Note that behaviour showed both after installation from Leap packages and from an RPM downloaded from Google, and both from a filled .config/google-chrome directory and after both cache and config was removed.
Which diagnostics can I give you to resolve this?
Regards,
Probably a bug.
Chromium/Chrome are unique web browsers, unlike other browsers the default search page is a locally stored page, not downloaded from the Internet.
I assume that everything else should work fine… ie. Search, surf to destination URLs.
TSU
No. Nothing loads, not even the settings.
To have a useful conversation, can anyone on Leap 42.2 confirm or deny that google-chrome-62 works as usual? (Note: the upgrade package was installed today so you might not have it).
Wherever you’re getting your chromium from, nothing later than 61 seems to be in any openSUSE repo.
Didn’t check google-chrome, don’t have a 42.2 machine with that around handy…
Are you sure you don’t have a network configuration error or similar? No error displayed at all, only a white, blank window?
Try launching from a command line and see if any errors are thrown.
TSU
The update broke all 4 42.2 systems I applied it to, had to roll back to the previous version to get the browser to work.
Symptoms of the broken update, extensions fail to load (Privacy Badger and Vanilla Cookie Manager) and the browser canvas is a dark gray and blank. Help, settings or web pages will not load.
I’d upload screenshots of the problem and the Chrome info from Yast if I could figure out uploading images in this forum.
For now find an old Chrome .RPM and manually load it, then lock it from further updates and you will be working again.
Google chrome might be different, but Chromium which comes from the OSS is only at 61.
And, it might be possible but doubtful that there is any 62 update because it’s also not listed at software.opensuse.org. If indeed such an update existed, then that’s pretty fast recalling and erasing all evidence.
Where are you getting your chromium unstable?
AFAIK you can only get unsatable and canary as Chromium Project downloads so won’t be updated via YaST, zypper or apper.
TSU
I’m getting my Chrome directly from the Google repositories: http://dl.google.com/linux/chrome/rpm/stable/x86_64 that I have installed in yast.
Up to this point Chrome has been picking up new releases from google with no issues but the update to v 62.0.3202.62-1 causes this problem.
Rolling back (manually installing the older version I had available) v [FONT=arial]60.0.3112.90-1 goes back to working normally.
It looks like the Google installer is also offering up [/FONT]v 62.0.3202.62-1 from here: https://www.google.com/chrome/browser/desktop/index.html (you must switch the default from deb to rpm on the download page)
I just tried this on a fresh install of 42.3 and the Google download is working, I confirmed it is the same 62.xxx version of Chrome.
i install also the latest stable chrome (62) and also have empty black tabs
soo anyone solved it?
However, I just upgraded to 42.3 and it still doesn’t work.
So one needs a fresh 42.3 install?
I have a support ticket in with Google on this. There is a possibility it is a “known issue.” I will post later if I get a fix.
Same problem here on 42.3.
It still works in a VM though!
You can still use Chrome 62…, if you start it with “–no-sandbox”.
Starting from CLI:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[17720:17748:1020/070746.757387:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1020/070746.757540:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[17720:17748:1020/070746.784785:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1020/070746.784879:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[17720:17748:1020/070749.785921:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1020/070749.786022:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[17720:17748:1020/070755.280639:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1020/070755.280778:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[17720:17748:1020/070757.492182:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1020/070757.492277:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
See also this thread: https://forums.opensuse.org/showthread.php/527688-Google-Chrome-not-working-after-update
The same(?) problems now appear with chromium-62 with today’s update. Lock your chromium-61. Why are these versions passed to users at all is beyond me.
Came to report the same problem with Chromium 62, lock yours before it breaks or roll-back and then lock it.
At least with the Suse version, Chormium you have the option to roll-back to a working version.
Working version of Chromium now available for updates, quick test but it looks good
62.0.3202.75-121.1-x86_64