I am getting this orange bar as of the subject of this thread every time I use chromium. Question:
a) can I get rid of it permanently without having to click it away every time?
b) is there a reason why the setting --no sandbox has been applied?
Version of Chromium:
Version 19.0.1066.0 (svn126066)
Version of openSUSE 12.1
Thank you.
Hey stakanov,
Which repo are you having Chromium installed from ? I’m running 19.0.1074 from Index of /repositories/network:/chromium these repos, and don’t have the issue
O.K. I will try. The version was from the regular update repo. Is this maybe because I run secure file permissions? I will try out and report back.
O.K. this is the same issue with the one of the build service repo. From the command line it is more specific:
chromium
[20104:20104:11559773058:ERROR:renderer_main.cc(224)] Running without renderer sandbox
any idea?
O.K. if you start the program directly it give you the reason:
/usr/lib64/chromium> /usr/lib64/chromium/chromium[21836:21836:14956187797:
FATAL:zygote_host_impl_linux.cc(148)]
The SUID sandbox helper binary was found, but is not configured correctly.
Rather than run without sandboxing I'm aborting now.
You need to make sure that /usr/lib/chrome_sandbox is owned by root and has mode 4755
Fine, I suppose that this is, given secure file permissions, a bug, as this should haven been included as setting in the permissions. Then this would call for a bug report. Does anybody know if the issue is already addressed?
On 2012-03-20 13:26, stakanov wrote:
> any idea?
Look at how the application is started: menu entry, script… somewhere
that option is written.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
In fact,
# chmod 4755 /usr/lib/chrome_sandbox
solves it.
I will try to find out if a bug report regarding secure permissions has been raised. After all, having chrome running in a sandbox should be compliant with the philosophy of secure permission settings. Or am I wrong?