Just for reference, Chrome's bug id
http://code.google.com/p/chromium/issues/detail?id=87704 .
Fixed supposedly on the alpha branch.
Configure 32-bit Linux to be PIC-clean.
> This change alters the asm defines so that libvpx is free of text
> relocations
> on 32-bit Linux.
> -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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-sandb
On Sun, Oct 2, 2011 at 9:01 PM, jackson byers wrote:
> mike cloaked responded:
>
>>The last update to chrome in f14 gave avc denials and in order to get
>>chrome to run after that it was necessary to run the following
>>commands (as root) before chrome would run again:
>
>>semanage fcontext -a -t
mike cloaked responded:
>The last update to chrome in f14 gave avc denials and in order to get
>chrome to run after that it was necessary to run the following
>commands (as root) before chrome would run again:
>semanage fcontext -a -t textrel_shlib_t '/opt/google/chrome/chrome'
>restorecon -v '/o
my last reply was incomplete; I did both of the commands as per Lance:
>give this out with root:
>semanage fcontext -a -s system_u -t usr_t /opt/google/chrome/chrome-sandbox
>restorecon -v /opt/google/chrome/chrome-sandbox
Jack
--
users mailing list
users@lists.fedoraproject.org
To unsubscri
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.
google-chrome
/opt/google/chrome/chrome: error while loading shared libraries: cannot restore
segment prot after reloc: Permission denied
give this out with root:
semanage fcontext -a -s system_u -t usr_t /opt/google/chrome/chrome-sandbox
restorecon -v /opt/google/chrome/chrome-sandbox
O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2011 03:40 PM, jackson byers wrote:
> Daniel J Walsh replied
>
>
>> This is definitely something in SELinux. The current upstream
>> google chrome is a little strange from an SELinux point of view.
>> Have you tried chromium?
>
>> http://
On Fri, Sep 30, 2011 at 8:40 PM, jackson byers wrote:
> Daniel J Walsh replied
>
>
>>This is definitely something in SELinux. The current upstream google
>>chrome is a little strange from an SELinux point of view. Have you
>>tried chromium?
>
>>http://fedoraproject.org/wiki/Chromium
>
>
> well,
Daniel J Walsh replied
>This is definitely something in SELinux. The current upstream google
>chrome is a little strange from an SELinux point of view. Have you
>tried chromium?
>http://fedoraproject.org/wiki/Chromium
well, no. Advice on this llist over last year or so is that
google-chro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2011 08:14 PM, Kernel Guardian wrote:
> SELinux rules. Look into /var/log/messages and
> /var/log/audit/audit.log. at least in my case. chrome works well on
> F15.
>
>
> On 29 September 2011 19:05, jackson byers
> wrote:
>> $ uname -r 2.6.
SELinux rules.
Look into /var/log/messages and /var/log/audit/audit.log.
at least in my case.
chrome works well on F15.
On 29 September 2011 19:05, jackson byers wrote:
> $ uname -r
> 2.6.35.13-92.fc14.i686.PAE
>
>
> after a recent 'yum update', google-chrome won't launch.
>
> same response wi
$ uname -r
2.6.35.13-92.fc14.i686.PAE
after a recent 'yum update', google-chrome won't launch.
same response with updated 2.6.35.14-96.fc14.i686.PAE
$ ls -l /opt/google/chrome/chrome
-rwxr-xr-x. 1 root root 55207772 Sep 27 01:46 /opt/google/chrome/chrome
$ /opt/google/chrome/chrome: error
13 matches
Mail list logo
