Activity log for bug #40537

Date Who What changed Old value New value Message
2006-04-21 11:31:25 Swirly bug added bug
2006-10-21 01:43:51 Larry bug assigned to openoffice (upstream)
2006-12-17 03:58:28 Bug Watch Updater openoffice: status Unknown Confirmed
2007-04-17 11:19:29 Philipp Schlesinger bug assigned to openoffice.org (Debian)
2007-04-18 06:47:37 Bug Watch Updater openoffice.org: status Unknown Unconfirmed
2007-10-21 17:36:04 Chris Cheney openoffice.org: importance Medium Wishlist
2007-10-21 17:38:28 Chris Cheney description 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. 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.
2007-10-21 17:38:28 Chris Cheney title Openoffice.org2 cannot write to NFS files OpenOffice cannot write to NFS files
2007-10-21 17:38:43 Chris Cheney openoffice.org: status New Confirmed
2008-03-15 07:56:37 Chris Cheney title OpenOffice cannot write to NFS files [Upstream] [hardy] OpenOffice cannot write to NFS files
2008-06-08 02:10:16 Bug Watch Updater openoffice.org: status New Fix Released
2008-06-14 01:41:13 Chris Cheney openoffice.org: status Confirmed Triaged
2008-09-26 16:41:39 Rolf Leggewie openoffice.org: status Triaged Incomplete
2008-10-01 12:14:15 Neil Munro openoffice.org: status Incomplete Confirmed
2008-10-01 12:14:15 Neil Munro openoffice.org: statusexplanation Marked as confirmed since it's a known bug and it's in upstream debian and openoffice, however debian closed the bug from lack of activity it seems, it seems this particular bug is several years old now and was first reported in 2005.
2008-10-17 04:02:32 Chris Cheney openoffice.org: status Confirmed Incomplete
2008-10-17 04:02:32 Chris Cheney openoffice.org: importance Wishlist Undecided
2008-10-17 04:02:32 Chris Cheney openoffice.org: statusexplanation Marked as confirmed since it's a known bug and it's in upstream debian and openoffice, however debian closed the bug from lack of activity it seems, it seems this particular bug is several years old now and was first reported in 2005. Do you still have this problem with openoffice.org 1:2.4.1-9ubuntu2 in Ubuntu 8.10? I can not reproduce this problem on Intrepid with nfs-common and nfs-kernel-server. I installed nfs-kernel-server on my desktop amd64 machine and just nfs-common on my laptop. Connected my laptop to my desktop and wrote files to the desktop without any problems.
2008-10-19 06:34:30 Chris Cheney openoffice.org: status Incomplete Fix Released
2008-10-19 06:34:30 Chris Cheney openoffice.org: statusexplanation Do you still have this problem with openoffice.org 1:2.4.1-9ubuntu2 in Ubuntu 8.10? I can not reproduce this problem on Intrepid with nfs-common and nfs-kernel-server. I installed nfs-kernel-server on my desktop amd64 machine and just nfs-common on my laptop. Connected my laptop to my desktop and wrote files to the desktop without any problems.
2010-02-28 19:28:18 fabio openoffice.org (Ubuntu): status Fix Released Fix Committed
2010-02-28 19:28:33 fabio openoffice.org (Ubuntu): status Fix Committed Fix Released
2011-06-04 14:57:57 Steffen Rusitschka removed subscriber Steffen Rusitschka
2013-06-19 00:42:06 KennoVO attachment added libreoffice.patch https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/40537/+attachment/3706957/+files/libreoffice.patch
2013-06-19 11:07:47 penalvch bug task added libreoffice (Ubuntu)
2013-06-19 11:19:58 penalvch summary [Upstream] [hardy] OpenOffice cannot write to NFS files Cannot write to NFS files
2013-06-19 12:18:52 Ubuntu Foundations Team Bug Bot tags regression regression-release patch regression regression-release
2013-06-19 12:19:00 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2013-06-20 16:34:13 Thomas Hotz bug added subscriber Thomas Hotz
2013-07-13 07:26:25 Thomas Hotz libreoffice (Ubuntu): status New Confirmed
2014-08-08 14:53:52 Bryan Quigley libreoffice (Ubuntu): status Confirmed Incomplete
2014-09-16 13:59:23 Bryan Quigley libreoffice (Ubuntu): status Incomplete Invalid
2014-09-16 13:59:39 Bryan Quigley openoffice: importance Unknown Undecided
2014-09-16 13:59:39 Bryan Quigley openoffice: status Confirmed New
2014-09-16 13:59:39 Bryan Quigley openoffice: remote watch OpenOffice.org Issue Tracker #51903
2014-09-16 13:59:50 Bryan Quigley openoffice: status New Invalid