On Fri, 2011-01-21 at 07:42 -0500, Daniel J Walsh wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/20/2011 05:12 PM, Genes MailLists wrote:
> On 01/20/2011 05:02 PM, Genes MailLists wrote:
>> On 01/20/2011 04:23 PM, Daniel J Walsh wrote:
>>
>>
>> If I want to run google chrome (say)-
>>
>> I tried this:
>>
>> mkdir -p sandbox-home/.config
>> rsync -av ~/.config/google-chrome ~/sandbox-home/.config
>>
>
> (1) Probably relevant - my default proxy is via ssh tunnel ... so I
> guess I need to somehow allow access to those ports on localhost ? Where
> would I do that ?
>
> (2) To avoid this for now - I tried deleting the .config/google-chrome
> so it would be a fresh first time run . same problem ... window starts
> and exits.
>
> Any suggestions ?
>
> thanks!
>
> g
Lets figure out if this is a chromium problem or something else. Does
sandbox -X xterm
Work?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org/
iEYEARECAAYFAk05fykACgkQrlYvE4MpobMDowCgqTtJY8SdLGxBvDwUO2rbJjjC
uTYAn3ON0AxBFJivwiuYh3zDQKaPtdeM
=WVl4
-----END PGP SIGNATURE-----
Hi
Just picking up on this thread - hope I don't confuse the issue
F14 fully updated
kdm, XFCE, NFS4 home directories, NIS
SElinux Enforcing
sandbox -X xterm fails for me
troubleshooter shows 3 problems
SELinux is preventing /usr/bin/Xephyr from using the signal access on a process
SELinux is preventing /usr/bin/Xephyr from search access on the directory /
SELinux is preventing /usr/bin/kdm from add_name access on the directory .Xauthority-c
---------------
Setting SElinux Permissive still fails with the two Xephyr problems
In both cases the display flashes very briefly with a rectangular shape
John