Launchpad has imported 14 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=75488.
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 2014-02-25T10:28:48+00:00 Patrick Smits wrote: Created attachment 94709 (Dutch) screenshot with error Problem description: Steps to reproduce: 1. User 1 creates a shared document and saves it on a network share. 2. User 2 edits the documents and saves it. 3. User 1 tries to reopen it, which results in the error in the (Dutch) screenshot. The buttons translate as Open Read-only, Open copy, Cancel. Current behavior: Document is locked by User 2, so User 1 can't edit it Expected behavior: File system lock is released, so User 1 can edit the document. Operating System: All Version: 4.2.0.4 release Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/2 ------------------------------------------------------------------------ On 2014-02-25T11:29:24+00:00 Cno wrote: Hi p, thanks for the report. Can you pls give details on the network, for people that want to reproduce the issue? Best, Cor Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/3 ------------------------------------------------------------------------ On 2014-02-25T12:13:08+00:00 Patrick Smits wrote: Yep, Documents are shared via a Synology NAS. We use Windows clients. If we use ODS as exchange format it just works. The problem occurs only with XLS. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/4 ------------------------------------------------------------------------ On 2014-02-25T12:42:42+00:00 Cno wrote: thanks, Looks like Bug 36852, Bug 63995 are closely related. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/5 ------------------------------------------------------------------------ On 2014-09-30T17:52:45+00:00 Raal wrote: I can reproduce with following configuration LO 4.3.3, Ubuntu LO 4.3.2, Win7 in virtualbox on the same machine shared /tmp between Linux and Windows When shared file is XLS, then error message appears: Document file 'file.xls' is locked for editing by When shared file is XLSX, then error message is: This document was last saved by Excel. Some formula cells may produce different results when recalculated. Do you want to recalculate all formula cells now? <YES> This spreadsheet is no longer in shared mode. Save your spreadsheet to a separate file and merge your changes to the shared spreadsheet manually. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/7 ------------------------------------------------------------------------ On 2015-06-21T19:05:22+00:00 Barta-c wrote: (In reply to raal from comment #4) > I can reproduce with following configuration > > LO 4.3.3, Ubuntu > LO 4.3.2, Win7 in virtualbox on the same machine > shared /tmp between Linux and Windows > > ... I set status to NEW because of this confirmation. did you try with 4.4.3.2? is the bug still present ? Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/8 ------------------------------------------------------------------------ On 2015-06-22T09:36:29+00:00 Patrick Smits wrote: Yep, behavior is still the same with 4.4.3.2. However I also noticed something else. If the shared xls is created and saved, as soon as you close the document, it no longer is shared. So even user 1 can't open the document as shared xls document anymore. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/9 ------------------------------------------------------------------------ On 2016-03-22T21:18:30+00:00 Christophelyon+libreoffice wrote: I was about to file a new bug report for a similar problem, so I'm updating this one instead. I've noticed locking problems when I want to open LO files stored on my Synology NAS, exported via NFS. I ran LO from Linux Ubuntu clients (15.10). When trying to open a file on the NFS server, LO shows an error message (after about 30 seconds, probably a timeout) and proposes to open the file read-only or to open a copy. I "solved" the problem by rebooting the NAS, but it re-occurs after some time. I've just given a quick look at LO sources, and noticed that in sal/osl/unx/file.cxx (openFilePath), locks are acquired using fcntl(F_WRLCK), but I couldn't find code to unlock the file. There is support to unlock files in sal/osl/unx/profile.cxx (OslProfile_lockFile), but I don't know if it's actually used. My assumption is that LO could keep acquiring locks, never releasing them, until the NAS is out of resources. Is that plausible? Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/10 ------------------------------------------------------------------------ On 2016-03-27T20:31:17+00:00 Christophelyon+libreoffice wrote: Actually I just ran $ strace -f soffice /path/to/nfs/file |& grep LK [pid 19093] fcntl(14, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19093] fcntl(14, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19093] fcntl(29, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0} <unfinished ...> [pid 19093] fcntl(35, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19093] fcntl(35, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19093] fcntl(35, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19093] fcntl(42, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19093] fcntl(42, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19096] fcntl(43, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 [pid 19107] fcntl(14, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0 I only opened the file, then quit libreoffice. As you can see several locks are acquired, but none is released. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/11 ------------------------------------------------------------------------ On 2017-12-18T03:26:37+00:00 Qa-admin-q wrote: ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/12 ------------------------------------------------------------------------ On 2017-12-18T20:22:45+00:00 Christophelyon+libreoffice wrote: I've just run the same command as in comment #8: $ Actually I just ran $ strace -f soffice /path/to/nfs/file |& grep LK [pid 19070] fcntl(15, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(15, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(24, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0} <unfinished ...> [pid 19073] fcntl(25, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(27, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(33, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(33, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(39, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19096] fcntl(37, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(24, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(24, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19099] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 [pid 19070] fcntl(16, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 So, as expected nothing has changed here. This time, I used version 1:5.4.2-0ubuntu0.17.10.1 from Ubuntu 17.10 Is anyone actually looking at bug reports? Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/13 ------------------------------------------------------------------------ On 2017-12-18T20:33:44+00:00 Beluga wrote: *** Bug 94152 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/14 ------------------------------------------------------------------------ On 2018-12-20T03:55:48+00:00 Qa-admin-q wrote: ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/15 ------------------------------------------------------------------------ On 2018-12-20T07:58:33+00:00 Christophelyon+libreoffice wrote: Hello, Just re-tested with libreoffice from my Ubuntu-18.04.1 machine. Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.2 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group Same command as in comment #8, same issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1232872/comments/16 ** Changed in: df-libreoffice Status: Unknown => Confirmed ** Changed in: df-libreoffice Importance: Unknown => Medium -- 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/1232872 Title: NFS / lock problem with LibreOffice wth 13.04 Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Incomplete Bug description: Hi all, I have a problem very similar to what is exposed in question #234375. Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing documents via NFS with LibreOffice. The slash screen display for about 30s, then there is a popup warning saying that another user has opened the file, and offering to open a copy, open as readonly or cancel. The point is, no other user has opened that file (being the only user on my personal PC, but storing my documents on NAS). So I tried the suggestion about adding "noauto" in /etc/fstab and changing /etc/rc.local, with no luck. But the modification of /usr/lib/libreoffice/program/soffice: ################## # STAR_PROFILE_LOCKING_DISABLED=1 export STAR_PROFILE_LOCKING_DISABLED # # file locking now enabled by default #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ... #export SAL_ENABLE_FILE_LOCKING ####################################### (That is, uncomment the first 2 lines, and commenting the other 2) This works OK. If this is the official way of fixing things, then I guess LibreOffice deserves an update on Ubuntu at least. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1232872/+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
