desktop-packages team mailing list archive

[Bug Watch Updater <577038@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 5 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=36852.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-05-04T19:00:37+00:00 PascalCavy wrote:

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

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/577038/comments/25

------------------------------------------------------------------------
On 2011-05-05T07:07:14+00:00 Sumuthu wrote:

Fridrich-> more info? Thanks!

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/577038/comments/26

------------------------------------------------------------------------
On 2011-09-15T13:06:26+00:00 Alex Thurgood wrote:

(In reply to comment #0)

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


FWIW, there is what appears to be an identical problem on AFS mounted shares, see bug 40907


Alex

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/577038/comments/27

------------------------------------------------------------------------
On 2011-09-15T17:56:42+00:00 PascalCavy wrote:

still no fix for that bug ? It renders libreoffice unusable in a shared
environnement

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/577038/comments/30

------------------------------------------------------------------------
On 2011-12-24T17:41:07+00:00 eflester wrote:

This has been a problem for me ever since I started using Libre Office,
which is about 2 years, I think. To fix it, I go into the soffice script
and comment out everything from "#adjust environment" through the "fi"
just before "if [ -z "$SAL_NOOPENGL" ]; then" (do not comment out this
last line, I include it only as a reference.)

I use recent versions of Ubuntu, such as 11.04, and Libre Office, as
well as OpenOffice (which has the same bug) on various computers,
attached to a Synology NAS appliance on which I'm using NFS to share
files. The problem is evident on all these computers.

I also use LibreOffice on Windows and don't notice this problem when
accessing files from the Samba service on the NAS.

Reply at: https://bugs.launchpad.net/df-
libreoffice/+bug/577038/comments/34

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/577038

Title:
  [Upstream] Hard lock in opening files from a remote NFS volume

Status in LibreOffice Productivity Suite:
  Confirmed
Status in LibreOffice:
  Confirmed
Status in The OpenOffice.org Suite:
  New
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  I recently updated to Lucid, and noticed that Openoffice would lock
  with opening certain files. First I thought the problem was a corrupt
  file, now I can reproducibly hard lock OO.org when trying to open ANY
  file (.xls, .doc, .odt) that is present in a remote NFS volume
  (locally mounted).

  Any file on the local hard disk can be opened without problems.
  Any file on the mounted NFS directory causes a hard lock, requiring a force-quit.

  Other applications don't show this behaviour (e.g. gedit, command line
  programs).

  Filesystem            Size  Used Avail Use% Mounted on
  /dev/md0               70G   17G   50G  26% /
  192.168.10.72:/home/fernan    243G  182G   42G  82% /home/fernan/gama-remote

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org 1:3.2.0-7ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri May  7 11:48:21 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/577038/+subscriptions