Public bug reported:

1) Ubuntu: Ubuntu 12.04.4 LTS
2) Libre Office: 4.2.3~rc3-0ubuntu2~precise1
3) If one person has opened a network shared file, and another one tries to 
open it, the message asking to open it as read only or a copy should be shown.
4) I get the message informing me that the file is damaged and if i want to 
repair it (wichever option i choose, i end up with a "general error").

Notes:
a) This happens if i open a file and i try to open it again
b) Only happens on network shares (smb, cifs, using nautilus, defining them in 
fstab, using pam_mount, etc, this is not the same bug from some time ago were 
smb shares would fail if mounted browsing the windows network in nautilus)
c) Only happens on LTSP thin clients, with libreoffice running on the server.
d) If the user blocking the file is not an LTSP thin client machine, even from 
a thing client machine, you get the correct message. It would seem that only 
thin clients fail to do SOMETHING to correctly inform that the file is blocked.
e) Logging directly to the server (not as a thin client), i don't have this 
issue either

** Affects: libreoffice (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1314768

Title:
  LTSP + Libreoffice + network share + open an already opened file =
  file damaged warning

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  1) Ubuntu: Ubuntu 12.04.4 LTS
  2) Libre Office: 4.2.3~rc3-0ubuntu2~precise1
  3) If one person has opened a network shared file, and another one tries to 
open it, the message asking to open it as read only or a copy should be shown.
  4) I get the message informing me that the file is damaged and if i want to 
repair it (wichever option i choose, i end up with a "general error").

  Notes:
  a) This happens if i open a file and i try to open it again
  b) Only happens on network shares (smb, cifs, using nautilus, defining them 
in fstab, using pam_mount, etc, this is not the same bug from some time ago 
were smb shares would fail if mounted browsing the windows network in nautilus)
  c) Only happens on LTSP thin clients, with libreoffice running on the server.
  d) If the user blocking the file is not an LTSP thin client machine, even 
from a thing client machine, you get the correct message. It would seem that 
only thin clients fail to do SOMETHING to correctly inform that the file is 
blocked.
  e) Logging directly to the server (not as a thin client), i don't have this 
issue either

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1314768/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to