Comment 30 for bug 577038

The problem is on opening a file on an NFS volume, not on save.

Openoffice.org in karmic did not worked well either but no hard lock was observed. It was unable to open nfs files R/W because it was always complaining that nfs files are locked by 'unknown' (another known bug of ooo on NFS). Since Lucid ooo had the lock problem (bug https://bugs.launchpad.net/openoffice/+bug/577038 on launchpad, bug http://qa.openoffice.org/issues/show_bug.cgi?id=113330 on ooo)

No other application have this problem on NFS.

nfs server is synology ds207+ :

Export :
/volume1/PC 192.168.0.1(rw,sync,no_wdelay,no_root_squash,insecure_locks,anonuid=0,anongid=0)

OS:
Linux synology 2.6.15 #1354 Sat Oct 23 01:49:30 CST 2010 armv5tejl GNU/Linux synology_88f5281_207+

Kubuntu natty:
mount:
synology:/volume1/PC on /mnt/pc type nfs (rw,addr=192.168.0.49)

fstab:
synology:/volume1/PC /mnt/pc nfs _netdev,nouser,auto,rw,dev,exec,suid 0 0

just for information, opening files on an iSCSI share is working, so the problem is really tight to NFS

Also as noted, a workaround is opening nfs files directly with the command
/usr/lib/libreoffice/program/oosplash.bin -writer "<path to file on nfs share>"

And finally note that the fileselector is sometimes relly sllllloooowwww to discover files on local disks, but when we open start libreoffice with /usr/lib/libreoffice/program/oosplash.bin -writer, then we have no problem to navigate quickly among the file system with the fileselector.

All this seems linked to settings in the libreoffice launch script./usr/lib/libreoffice/program/soffice