This is nothing short of appalling: - Issue still present in LibreOffice on Precise (LTS) - It's been 7 (seven) years - Currently, the workaround is to edit a file that gets overwritten with every update: http://ubuntuforums.org/showthread.php?t=1645957&p=11891452#post11891452
The attached patch yields control over these essential flags back to /etc/libreoffice/soffice.sh , which is part of libreoffice-common but is ignored by /usr/lib/libreoffice/program/soffice (in the same package). It would be trivial for the package maintainer to apply this fix, with no loss of functionality whatsoever. People who are on NSFv3 simply would have to edit a flag in /etc/libreoffice/soffice.sh one time; since it's in /etc , later updates should leave it alone. Nothing changes for anyone else. ** Patch added: "libreoffice.patch" https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/40537/+attachment/3706957/+files/libreoffice.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/40537 Title: [Upstream] [hardy] OpenOffice cannot write to NFS files Status in The OpenOffice.org Suite: Confirmed Status in “openoffice.org” package in Ubuntu: Fix Released Status in “openoffice.org” package in Debian: Fix Released Bug description: SOLUTION: 1. Use NFSv4 if possible 2. Install nfs-common package if not installed == Opening a file within an NFS mounted filesystem causes OpenOffice to show the file in read-only mode, and remove the margins and various other editing widgets from the application window. Any attempt to save a document to an NFS mount results in an error dialog that contains the text:- Error saving the document Filename.odt: General Error. General input/output error. This makes the application extremely awkward to use in an office type environment, and is a huge step backwards in functionality from the OpenOffice.org 1.1.4 package it replaced for me. This bug is know in debian as bug #335742. It was closed by un upstream release. In breezy, there is no way to work around the bug wich make ooo unusable in breezy in an office environment with NFS. A partial solution would be to release a backport for openoffice.org2 from dapper, as the version in dapper works. To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/40537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
