Bug 136190 - Opening a file twice in quick succession results in two r/w windows of the same document
Summary: Opening a file twice in quick succession results in two r/w windows of the sa...
Status: RESOLVED DUPLICATE of bug 137356
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.1 all versions
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-27 15:39 UTC by dan.roth
Modified: 2021-04-23 05:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dan.roth 2020-08-27 15:39:48 UTC
Overview: 

Opening a file twice in quick succession results in 2 read/write windows of the same document. A customer of ours has a hyperlink on a website, which triggers a script that opens a document with the 'soffice' command.

The users often double-klick on this link, which results in this problem.

Steps to Reproduce:

    1) Open the same file with "soffice <document.odt>" command twice.
        Alternatively you can use the following command to emulate this: "soffice <document.odt> & soffice <document.odt>"

Actual Results: 
    
    Two windows editing the same file open. 

Expected Results: 

    One window opens editing the file. The second command doesn't open a new window but instead sets the window focus to the first window.

Build Date & Hardware: 

    V6.1.6.3 release 3 on RHEL7


Additional Builds and Platforms: 

    Also reproduced on: Ubuntu 20.04 V6.4.2.2 6.4.2-0ubuntu3 and on Mac OS with Libreoffice 6 (exact version unknown)
Comment 1 Justin L 2020-12-15 10:59:16 UTC
Implied here is that if there is a delay so that the document is actually already opened before the second instance is started, then it works as expected.

And I can confirm that.
It sounds like NOTOURBUG to me.
Comment 2 Aron Budea 2021-04-23 05:50:52 UTC
I'm going to assume this is bug 137356, please try with version 7.1, which contains the fix, and reset status to UNCONFIRMED if the bug still occurs.

*** This bug has been marked as a duplicate of bug 137356 ***