google-chrome stop work

whyequeme · n00b Joined: 27 Jun 2012 Posts: 3

Today i update google-chrome from 19.0.1084.56_p140965:stable to 20.0.1132.43_p143823:stable and chrome stop work. Just run 3 processes:

\_ /opt/google/chrome/chrome --extra-plugin-dir=/usr/lib/nsbrowser/plugins
| \_ /opt/google/chrome/chrome --extra-plugin-dir=/usr/lib/nsbrowser/plugins
| \_ [chrome-sandbox] <defunct>

No error message in console, no any window appear.

swimmer · Posted: Wed Jun 27, 2012 10:43 pm Post subject:

I got an emerge log message saying that I need both PID_NS & NET_NS compiled into the kernel to make sandbox work ... it's for chrome:unstable though but I might be helpful for you as well.

Kindly yours
swimmer

whyequeme · n00b Joined: 27 Jun 2012 Posts: 3

I don't have this message, but i check my kernel config and both options enabled:

zcat /proc/config.gz | grep "PID_NS\|NET_NS"
CONFIG_PID_NS=y
CONFIG_NET_NS=y

Wolfbone · n00b Joined: 29 Sep 2004 Posts: 30

I'm having (different) serious troubles with the recent 'stable' o_O google-chrome update too. I really need it to be working and yet when I go to reinstall the working previous version just a few hours later I find that the ebuild no longer exists. Unbelievable. :-(

floppymaster · Posted: Fri Jun 29, 2012 3:09 pm Post subject:

You can blame Google for the missing ebuilds; they remove the distfiles for old versions from their servers, and we can't mirror them due to licensing issues.

Wolfbone · n00b Joined: 29 Sep 2004 Posts: 30

floppymaster · Posted: Fri Jun 29, 2012 4:41 pm Post subject:

chromium-19 was removed from the tree as soon as chromium-20 was marked stable. This was a security related bump, and our security team doesn't like having insecure versions in the tree.

You can retrieve old ebuilds from the CVS attic.

http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/?hideattic=0

http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/google-chrome/?hideattic=0

whyequeme · n00b Joined: 27 Jun 2012 Posts: 3

In my case problem was in flash plugin. I remove /opt/google/chrome/PepperFlash folder and its help.
In chrome-20 flash plugin compile with SSE2 instructions which my old CPU not support. Hmm, guys from Google could print some error message or just autodisable flash plugin. Maybe should be add sse2check option in ebuild?

floppymaster · Posted: Fri Jun 29, 2012 5:14 pm Post subject:

Ah, good catch. Can you file a bug please?

Wolfbone · n00b Joined: 29 Sep 2004 Posts: 30