Re: Issue 82150 in chromium: 'execv failed: Permission denied' error when Chrome from zip file or manually unpacked deb file
chro...@googlecode.com
Status: WontFix
Comment #2 on issue 82150 by mb...@google.com: 'execv failed: Permission
denied' error when Chrome from zip file or manually unpacked deb file
http://code.google.com/p/chromium/issues/detail?id=82150
Upon further investigation, it appears that this problem is related to
AppArmor, not SELinux or Chrome.
When AppArmor is enabled, it is necessary to configure an AppArmor profile
for the chrome-sandbox program. It appears that the
/etc/apparmor.d/abstractions/ubuntu-browsers configuration file has an
entry by default for /opt/google/chrome/google-chrome. This suggests that
google-chrome will run correctly when installed exactly in
/opt/google/chrome, but that it won't work by default when installed
elsewhere (without creating a new AppArmor profile for the new location).
All said, the easiest thing is probably just to run with the --no-sandbox
option when running Chrome out of a zip file.
Closing as "won't fix" since this is an AppArmor problem, not a Chrome
problem.
chro...@googlecode.com
Comment #3 on issue 82150 by kut...@gmail.com: 'execv failed: Permission
http://code.google.com/p/chromium/issues/detail?id=82150
This command fixed google-chrome in my fedora 15
#chcon -t textrel_shlib_t /opt/google/chrome/chrome-sandbox
It allows the chrome sandbox to access the shared libraries
chro...@googlecode.com
chro...@googlecode.com
Comment #5 on issue 82150 by kiran.te...@indiayouth.info: 'execv failed:
file
http://code.google.com/p/chromium/issues/detail?id=82150
Why is this not getting solved ? it is been running from several sub
versions right from chrome 13.
chro...@googlecode.com
Comment #6 on issue 82150 by mb...@google.com: 'execv failed: Permission
http://code.google.com/p/chromium/issues/detail?id=82150
Hi Kiran,
Are you running into the issue of trying to manually extract chrome from a
deb or zip file and then run it? The work-around is to use --no-sandbox.
If this doesn't work, then you may have a different issue.
The problem is with AppArmor, not Chrome, and we don't directly control
AppArmor configurations in Linux distributions.
chro...@googlecode.com
Comment #8 on issue 82150 by mb...@google.com: 'execv failed: Permission
http://code.google.com/p/chromium/issues/detail?id=82150
Kiran: This is a bit outside my knowledge area, but it appears that chcon
is an SELinux command, not an AppArmor command, so this problem on Fedora
may be an SELinux issue after all. From reading this thread, it seems like
you are likely running into a different issue than what this bug was
originally opened for. Please feel free to open a new bug with a
description of the problem that you're seeing, and make sure to include
things like verbatim output from the terminal and any special features in
your distribution (like having SELinux enabled).
chro...@googlecode.com
Comment #9 on issue 82150 by enso...@google.com: 'execv failed: Permission
http://code.google.com/p/chromium/issues/detail?id=82150
> chcon -t textrel_shlib_t ./chrome_sandbox
chcon: can't apply partial context to unlabeled file `./chrome_sandbox'
using --no-sandbox works though. this is on ubuntu, so it would probably
need a apparmor alike workaround too.
chro...@googlecode.com
Comment #10 on issue 82150 by james.pe...@linuxjet.com: 'execv failed:
file
http://code.google.com/p/chromium/issues/detail?id=82150
I can confirm that the fix works with CentOS 6.2 as well, "BUT", I do not
have apparmor installed and I am getting the same issue. This definatley
suggests that it is not an Apparmor issue. Please look into further.
google-chrome
execv failed: Permission denied
chro...@googlecode.com
Comment #11 on issue 82150 by AYa...@gmail.com: 'execv failed: Permission
http://code.google.com/p/chromium/issues/detail?id=82150