F14, google-chrome won't launch after yum update [SOLVED]
Daniel J Walsh
dwalsh at redhat.com
Mon Oct 3 13:35:54 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
On 10/01/2011 12:56 PM, jackson byers wrote:
> Daniel J Walsh replied
>> My goal is not to get into the blame game, but google-chrome
>> requires some strange access that I have never seen an app need
>> before. Basically an application chrome-sandbox needing to load
>> the the executable (not shared library) chrome which was not
>> compiled with PIC. The latest chrome browser from beta release
>> requires mmap_zero, which is a very dangerous access that we will
>> not give.
>> If you do not want SELinux controlling chrome-sandbox you can
>> turn off the boolean unconfined_chrome_sandbox_transition
>> setsebool -P unconfined_chrome_sandbox_transition 0
> - [root at f14 ~]# setsebool -P unconfined_chrome_sandbox_transition
> 0 libsemanage.dbase_llist_set: record not found in the database (No
> such file or directory). libsemanage.dbase_llist_set: could not set
> record value (No such file or directory). Could not change boolean
> unconfined_chrome_sandbox_transition Could not change policy
> so that failed; all greek to me.
>> The link above has a version of chrome, specially built for
>> Fedora which should work fine with SELinux.
> Daniel, I will keep this as a fallback solution
> ------- Lancebaynes87 replied
>> give this out with root: semanage fcontext -a -s system_u -t
>> usr_t /opt/google/chrome/chrome-sandbox restorecon -v
> [root at f14 ~]# restorecon -v /opt/google/chrome/chrome-sandbox
> restorecon reset /opt/google/chrome/chrome-sandbox context
> Now, chrome comes up!
> Thanks to Daniel for the explanation, even tho my understanding is
> Thanks to Lance for the fix!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the users