Confirmed - this workaround fixes it on my system as well. Thanks.
Andy
--
----------------------------------------------------------------------
Andrew J Perrin - andrew_per...@unc.edu - http://perrin.socsci.unc.edu
Associate Professor and Associate Chair of Sociology
University of North Carolina - CB#3210, Chapel Hill, NC 27599-3210 USA
On Thu, 7 May 2009, Angel Marin wrote:
Andrew J Perrin wrote:
An interesting update: the problem does not seem to exist with OpenOffice
native files (OpenDocument), i.e., .odt and .ods files. It happens with the
same files saved in Microsoft formats, i.e., .doc and .xls, in the same
directories.
We get this for all document formats where user opening the file does not
have regular unix perms to write the file.
This looks like openoffice 3 trying to be smart figuring that if file perms
are 644 and you're not the owner you won't be able to write to the file ...
that's correct except for filesystems like afs that have their own acl system
and completely ignore the regular unix perms.
So it looks like an upstream screw up in the oo.org 3 cycle.
As a workaround you can chmod all openoffice files to 666 and folders to 777
and let afs handle read/write access when it has to.
--
To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
