https://bugs.documentfoundation.org/show_bug.cgi?id=146364

            Bug ID: 146364
           Summary: Calc does not report the file closing to 7Zip if
                    another LibreOffice document is open
           Product: LibreOffice
           Version: 3.3 all versions
          Hardware: x86 (IA32)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: tfar...@gmx.at

Description:
I store several .ods files in a 7Zip archive with password.
To edit such a calc table I open the archive in 7Zip, open the file under
Users\MyNamw\AppDAta\Temp\..., edit it, write it back and exit LibreOffice.
Then 7Zip asks me if I want to update the archive, works very nice.

However if I forget to CLOSE ALL LibreOffice files before opening the target
file then it happens very often that LibreOffice does not report the file
closing to 7Zip, it does not ask me to save and and ALL MY EDITINGS GET LOST.
I use LibreOffice 7.1.3.2 (x86)
Build:  
https://git.libreoffice.org/core/+log/47f78053abe362b9384784d31a6e56f8511eb1c1

with  Windows 10.0 Build 19042

I found the same problem with OpenOffice as well.

Steps to Reproduce:
1. Make a 7Zip archive with a calc x.ods file, open and change it.
2. Open a different LibreOffice file and do NOT close it.
3. Save the first file and exit from calc.
7Zip does not ask if update the archive and my changes get lost.

Actual Results:
See above

Expected Results:
My changes get lost


Reproducible: Sometimes


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: at
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

Versionsinformation
7.1.3.2 (x86) / LibreOffice Community 47f78053abe362b9384784d31...
CPU-Threads: 2; BS: Windows 10.0 Build 19042 Ul-Render: Skia/Raster; VCL: win
de-DE (de_DE); Ul: de-DE Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to