Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: Paul de Vrieze <pauldv@g.o>
Subject: Re: openoffice-bin-2.0.2 hang for regular users
Date: Thu, 23 Mar 2006 14:15:39 +0100
On Thursday 23 March 2006 14:07, Scott Stoddard wrote:

> I don't know if this has been resolved yet, but I was having a similar
> (read: exactly the same) problem.  Are you using nfs-mounted home
> directories by any chance?
>
> In my case we're using a diskless gentoo system where the home
> directories are all nfs mounts to the server.  The problem had to do
> with nfs file locking.  It can be solved by editing
> /usr/lib/openoffice/program/soffice and commenting out these two lines:
>
> SAL_ENABLE_FILE_LOCKING=1
> export SAL_ENABLE_FILE_LOCKING
>
> Note that setting it =0 was not enough for me, I had to comment them out.
>
> Everything worked fine after that.

Of course the correct solution is to enable nfs locking.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@g.o
Homepage: http://www.devrieze.net
Attachment:
pgpE1gxGarnm4.pgp (PGP signature)
Replies:
Re: openoffice-bin-2.0.2 hang for regular users
-- Scott Stoddard
References:
openoffice-bin-2.0.2 hang for regular users
-- Andreas Vinsander
Re: openoffice-bin-2.0.2 hang for regular users
-- Scott Stoddard
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: openoffice-bin-2.0.2 hang for regular users
Next by thread:
Re: openoffice-bin-2.0.2 hang for regular users
Previous by date:
Re: openoffice-bin-2.0.2 hang for regular users
Next by date:
Re: openoffice-bin-2.0.2 hang for regular users


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.