Bug Hunting Session
Bug 101537 - Using "working copies" with 2 or more locked documents replace each other
Summary: Using "working copies" with 2 or more locked documents replace each other
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: File-Lock
  Show dependency treegraph
 
Reported: 2016-08-15 09:30 UTC by a07cd040897db54e103c
Modified: 2018-12-21 09:51 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
A Screenshot of the dialog box about locked documents. (11.35 KB, image/png)
2016-08-15 09:30 UTC, a07cd040897db54e103c
Details

Note You need to log in before you can comment on or make changes to this bug.
Description a07cd040897db54e103c 2016-08-15 09:30:23 UTC
Created attachment 126839 [details]
A Screenshot of the dialog box about locked documents.

If user X tries to open a document on a network share, that is already opened by user Y, a message is displayed informing X about the issue and asking X whether to
a) use the original with read-only option
b) use a working copy or
c) Cancel

If you choose option b) on document 1 everything works as expected. If you now open another already locked document 2 also choosing option b) the formerly opened document 1 disappears and document 2 is shown in the window.

Expected behaviour:
The window showing document 1 should stay untouched. Instead another window showing document 2 should be created.
Comment 1 Aron Budea 2016-08-15 11:00:46 UTC
Confirmed with v5.1.4.2 in Windows 7.

The dialog changed in 5.2, and doesn't have Open Copy anymore (there's Open instead, which disregards the lock), at least that's what I saw when I tested locally. Since there's only one further update planned for 5.1 after 5.1.5, it's probably not worth fixing.
Comment 2 QA Administrators 2017-09-01 11:16:14 UTC Comment hidden (obsolete)
Comment 3 a07cd040897db54e103c 2018-06-20 15:15:05 UTC
retested with

Version: 5.2.7.2 (x64)
Build-ID: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10
CPU-Threads: 10; BS-Version: Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group

=> problem is still reproducible
Comment 4 a07cd040897db54e103c 2018-12-21 09:33:41 UTC
retestet with:

Version: 6.1.3.2
Build-ID: 1:6.1.3-2
CPU-Threads: 2; BS: Linux 4.18; UI-Render: Standard; VCL: x11; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded

and 

Version: 6.0.6.2 (x64)
Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
CPU-Threads: 16; BS: Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group

=> problem still exists in both cases, but i noticed the following:

The replacement of the working-copy of the first document DOES NOT appear, if it contains unsaved changes when w-c of the second document is opened. Then the behaviour is as expected.