Apache OpenOffice (AOO) Bugzilla – Issue 40750
Resaving files on partitions not mounted with parameter"exec" impossible
Last modified: 2010-11-10 21:35:10 UTC
As described in "http://www.oooforum.org/forum/viewtopic.php?t=14739" it is possible to get the message "Could not create backup copy" when saving to an nfs server which is not mounted in fstab with the option exec under SuSE 9.2. The real problem is that OpenOffice is not saving the document at all. The message suggest it could not create a backup copy (an option when saving which was not set in my environment). This may lead to the loss of data. The error message should be replaced by something like "Could not save document" which will alert the user immediately that there is something really wrong.
*** Issue 36629 has been marked as a duplicate of this issue. ***
please have a look at issue 36639 for a second example
changing summary from "Misleading message when not able to save documents to nfs server" to "Resaving files on partitions not mounted with parameter"exec" impossible"
don't know if this is OOo fault, but still setting to NEW.
TM->requirements: More a wish for a change, for an enhancement than a defect. Please have a look.
enhancement -> defect, because - based on following user list discussion de.openoffice.org - users do face this problem and report, that other applications apart from OOo work flawlessly on this partitions setup. OOo should do the same, thus avoiding user confusion.
maxweber: don't forget to reassign to the default owner when changing the type from RFE to Defect. I could not reproduce with Mandrake 9.0 based system. I suspect this to be a SuSE-only problem. (this was reported to be broken with local (vfat) filesystems on the german-lang mailing list as well) I could not test with a remote filesystem. Summary: If the mount-option "noexec" (implied by the option user(s)) is given on a SuSE-Linux, OOo cannot save files to the mounted filesystem. When the same filesystem is mounted with "exec", OOo can save to the filesystem. This was not reproducible with a Mandrake based distro, but was reported by several users on the german-lang mailing list (users@de.openoffice.org) (all using SuSE linux)
This issue is invalid since it is caused by a bug in the linux kernel. Thanks to Stephan Bergmann for his posting to the de-users mailing-list! More information: http://www.ussg.iu.edu/hypermail/linux/kernel/0410.0/0478.html OOo 2.0 will not be affected by this bug since it is build with a newer version of gcc.
closing issue. Nothing for OOo to do...
This should indeed not be a problem for OOo 2.0, but we can still fix OOo 1.1.5 (to work around the Linux Kernel bug).
.
fixed
How to test: - Use a SuSE 9.2 Linux machine. - Make sure you have some file system mounted noexec. For example, as su, do # mkdir /test # mount -t nfs -o noexec v20z-so3:/export/home /test to mount such an fsys under /test. - Create a document on that fsys. Then reopen the document, modify it, save it: Instead of error box "Could not create backup copy" it should work now. - Don't forget to clean up, as su: # umount /test # rmdir /test - This issue is Linux-specific, but test other platforms for regressions, too. re-open issue and try to reassign to tm@openoffice.org
try to reassign to tm@openoffice.org
try to reset resolution to FIXED
Checked and verified in cws sb30 -> OK !
*** Issue 43707 has been marked as a duplicate of this issue. ***
*** Issue 45121 has been marked as a duplicate of this issue. ***
closed !
Created attachment 73696