Chrome won't launch from Porteus 32-bit on some PC's

Post#16 by **Payoon** » 26 Jun 2015, 19:22

Hi Neko,
thanks a lot for your hint. It solved my problem. Sorry I reply very late, but I simply missed to follow up this thread. I took the libs from debian [libudev1_215-17+deb8u1_amd64]. They also work. So the problem can be regarded as solved. Domo arigato.

Payoon

Post#17 by **neko** » 27 Jun 2015, 02:24

@Payoon
I am glad that it was useful for you.

Now I upload Google-Chrome pakages that are for a 'aFVWM' desktop.
These packages may be used for another desktop.
But these packages have the issue that a 360 degree Youtube can't be watched.

"Google chrome for v3.1 Porteus aFVWM"
http://forum.porteus.org/viewtopic.php? ... 571#p33571

Thanks.

Post#18 by **Payoon** » 27 Jun 2015, 22:42

Hi Neko,
after I downloaded your module google-chrome-43.0.2357.130-1.xzm I couldn't start it. I always get a message
like

xxx Bad NaCl Helper ***

. Googling told me I should correctly configure the sandbox. But how? The main and only reason I upgraded to porteus 3.1 from 2.1 was that chrome wouldn't accept the old kernel in its newer versions. I have also tried the latest download from google chrome by copying the content of opt/google/chrome of the debian binary into the original module of porteus 3.1. The message is exactly the same. I could move to firefox but I really love chrome because of its speed and the outstanding print function.
The message with

Bad NaCl Helper

seems to be a common thing with chrome, but really nowhere a clear explanation how to get rid of it. Any idea?

Regards Payoon

Post#19 by **neko** » 28 Jun 2015, 17:21

@Payoon
This article might be usefull for your case.

"it only starts when running it with --no-sandbox"
http://code.google.com/p/chromium/issue ... ?id=478530

Thanks.

Post#20 by **Payoon** » 29 Jun 2015, 19:09

Hi Neko,
thanks for your help. I will try that, but still don't understand what causes the error message. Is it Chrome that doesn't like the kernel or is Porteus 3.1 itself not suitable for that Chrome release. Maybe we never know.

Greetings to Japan

Payoon

Post#21 by **neko** » 30 Jun 2015, 02:20

@Payoon

You pointed out that
A Chrome running is depending on the 2 factors
which are 'the kernel or is Porteus 3.1' and 'Chrome release'.

Therefor I made the ISO that has Kernel 3.18.16 and Google-Chrome 43.0.2357.130-1,
and then tested the ISO on my PC.
It was OK.

The ISO that was tested successfully is following.
XFCE_de-kernel.v3.18.16-x86_64-2.iso (206 M)
http://www.mediafire.com/download/avz96 ... 6_64-2.iso
md5sum: f2de06714d7e67d3728e02c60880bac2 XFCE_de-kernel.v3.18.16-x86_64-2.iso

64 bit XFCE locale 'de_DE' including Google-Chrome.
Google-Chrome is executed with the option '--disable-gpu'.

About kernel 3.18.16, please refer
http://forum.porteus.org/viewtopic.php? ... =45#p34291

About Google-Chrome, please refer
http://forum.porteus.org/viewtopic.php? ... =45#p33571

Thanks.

Post#22 by **Payoon** » 30 Jun 2015, 11:13

Hello Neko,
thank you very much that you made porteus with kernel 3.18 and chrome 43. I'm very happy about it, but the sad news is that I get the same "bad NaCl helper" message like before. What I still have to try is to use that with the udev1 library. Otherwise the only eplanation for me would be the hardware, because it works for you but not for me. But I have new hp notebook with amd a8. Don't know what could be wrong. I will try udev1 and if that doesn't work, I will wait for next porteus release and go with firefox until then. But I will miss chrome. Whe n you print something from the internet, nothing is more elegant than chrome. Thank you very very very much for investing so much time to help me. I'll let you know about testing kernel 3.18 together with libudev1.

Sayonara

Payoon

Post#23 by **donald** » 30 Jun 2015, 12:48

What I have found (about it) is that
the current Google-Chrome need a kernel (higher than 3.17) compiled with
namespace, seccomp, tsync support.
otherwise it will not lauch because the sandbox is not working.

You can try to run chrome without sandbox
google-chrome-stable --disable-setuid-sandbox
or
google-chrome-stable --no-sandbox

Post#24 by **Payoon** » 30 Jun 2015, 14:26

Hi Donald, Hi Neko

found the reason for the problem. As some kind of bad habit I used my porteus always as root ( it's like smoking, everybody knows it can be harmful, but many do it anyway). So far I always adapted a line

--user-data-dir

at the end of google-chrome script in /opt/google/chrome and I could use the browser like any other user. But after Chrome 41 (that I still use as 32bit) it doesn't seem to be sufficient any more. Neko, I have tested your porteus with kernel 3.18.9 as user guest and everything works fine. The solution for me is: In the future be only root when absolutely necessary.

Thanks to both of You for support.
It's hot here. Now time for icecold beer.
Payoon

Post#25 by **Payoon** » 30 Jun 2015, 15:10

One word to the developers of chrome:

when the reason why chrome won't work is, that I am root, you should tell me explicitely and not let chrome spit out some unidentifiable nonsens

Nevertheless a great browser.

Payoon

Post#26 by **neko** » 30 Jun 2015, 18:41

------------------------------------------------------------------------------------------------
@donald
I rebuilt kernel 3.18.16 with the config that was changed from your information.
And Google-Chrome could be executed without the option '--disable-gpu'.
By the side effect of omitting '--disable-gpu' option,
Google-Chrome can watch a '360 degree youtube'.

[old config]
# CONFIG_NAMESPACES is not set
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_SECCOMP=y

[new config]
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_SECCOMP=y

The ISO that was tested is following.
XFCE_de-kernel.v3.18.16-x86_64-3.iso (206 M)
http://www.mediafire.com/download/uqlgd ... 6_64-3.iso
md5sum: 026bbc93c7aa384e652f99d3b7283d12 XFCE_de-kernel.v3.18.16-x86_64-3.iso

I will update 3.18.16 kernel build.
Thank you for your information.

------------------------------------------------------------------------------------------------
@Payoon

I tested the Google-Chrome in live of XFCE_de-kernel.v3.18.16-x86_64-3.iso by 'root' usr.
The result was same as yours.
# google-chrome-stable
# google-chrome-stable --disable-setuid-sandbox
# google-chrome-stable --no-sandbox

The same "root user" problem was discussed on the following site.
http://www.pclinuxos.com/forum/index.php?topic=132020.0

It is regrettable. But I give up.

Thanks.
------------------------------------------------------------------------------------------------

Porteus

Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's

Re: Chrome won't launch from Porteus 32-bit on some PC's