Google Chrome as Local App?

[Nick Fenger]

Sure enough! Chrome runs as a local app perfectly with this:

nick at ltsp87:~$ chromium-browser --user-data-dir=/tmp

This does not work:

nick at ltsp87:~$ chromium-browser --user-data-dir=/home/nick
[3629:3629:1639260269:ERROR:chrome/browser/process_singleton_linux.cc(780)]
Failed to bind() /home/nick/SingletonSocket: Operation not permitted
[3629:3629:1639260356:ERROR:chrome/browser/browser_main.cc(997)] Failed to
create a ProcessSingleton for your profile directory. This means that
running multiple instances would start multiple browser processes rather
than opening a new window in the existing process. Aborting now to avoid
profile corruption.
n.

I will try Stéphane's "ugly workaround" tomorrow.

Thanks,

-Nick



On Tue, Sep 7, 2010 at 7:42 PM, Stéphane Graber <stgraber at ubuntu.com> wrote:

> On Tue, 2010-09-07 at 08:20 -0700, Richard Doyle wrote:
> > On Tue, 2010-09-07 at 08:52 -0400, Jonathan Carter (highvoltage) wrote:
> > > Hi Nick
> > >
> > > On 07/09/2010 00:25, Nick Fenger wrote:
> > > > I'm wondering if anyone has google chrome working as a local app? If
> so,
> > > > what configuration worked? NFS instead of NBD? Chrome works much
> better
> > > > with google docs so I would like to get it going.
> > >
> > > Adding this to lts.conf should do the trick:
> > >
> > > SSH_FOLLOW_SYMLINKS=False
> >
> > Not sure why, but Chrome doesn't work as a localapp without also setting
> > NFS_HOME on our Lucid system.
> >
> > >
> > > -Jonathan
>
> Hello,
>
> With the one included in Lucid there's a small issue as it tries to
> create a socket on sshfs which isn't supported by that filesystem.
>
> An ugly workaround is something like this (to run in your home directory
> on your thin client):
> mv ~/.config/chromium ~/.config/chromium.orig
> mkdir /tmp/.config-chromium
> ln -sf /tmp/.config-chromium ~/.config/chromium
> ln -sf ~/.config/chromium.orig/Default /tmp/.config-chromium/Default
>
>
> That's hackish but usually works fine, it basically creates a new
> directory in /tmp, then make chromium's configuration directory point to
> that so that it writes to tmpfs instead of sshfs then symlink the actual
> configuration directory back to the original configuration.
> That way the socket is created in /tmp and the rest of your
> configuration remains in your home directory.
>
> Alternatively, Jonathan suggested (in real-life ;)) that he might have
> been using a PPA for his chromium last time he tried, so maybe the PPA
> builds of chromium work fine with just ssh_follow_symlinks disabled (you
> need that in all cases).
>
> Hope it helps
>
>
> --
> Stéphane Graber
> Ubuntu developer
> http://www.ubuntu.com
>
> --
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>
>


-- 
Nick Fenger
-Information Technology

Trillium Charter School
5420 N. Interstate Ave
Portland, OR 97217
(503) 285-3833
http://www.trilliumcharterschool.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20100909/fffb8413/attachment.htm