Bug 140329 - File cleanup for edited Writer documents not happening when Writer is exited.
Summary: File cleanup for edited Writer documents not happening when Writer is exited.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-11 03:11 UTC by austin.spiegelman
Modified: 2021-11-13 05:46 UTC (History)
2 users (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 austin.spiegelman 2021-02-11 03:11:21 UTC
Description:
My files can be rather large. 1,016,944 character and don't appear to be closing properly if libreOffice Writer is exited without closing the document first... Even if saved. This does not happen every time. if I close the document before exiting the problem is stopped and a bug dialog does not appear the next time that document is opened.

Steps to Reproduce:
1. I open a LibreOffice Writer document directly.
2. Make a few changes.
3. Save those changes.
4. Exit out of LibreOffice Writer without closing the document first.

Actual Results:
A legacy file ".~lock.document.odt#" is left in the folder and causes an error the next time the actual document is opened.

Expected Results:
LibreOffice Writer should exit the opened documents gracefully and clean up after it's when leaving.


Reproducible: Sometimes


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
In order for legacy file to not happen I must select the File menu and then Close the document before I exit the software. Doing this removes the issue.
Comment 1 mulla.tasanim 2021-03-09 21:35:21 UTC
Thank you for reporting the bug. 

I can not reproduce the bug in

Version: 7.0.3.1 (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nb-NO (en_US); UI: en-US
Calc: CL

Version: 7.2.0.0.alpha0+ (x64)
Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 2 Jean-Baptiste Faure 2021-04-15 20:15:57 UTC
Not reproducible for me under Linux/Ubuntu (18.04 x86-64) with LO 7.1 and current master. I never experienced that with older versions.

Could you add information about your Linux distribution, the filesystem, the device on which the file is stored?

What is the size of the file ? I guess one million of character make around 1000 pages, right?

Status has been set to NEEDINFO, please set it back to UNCONFIRMED once requested information has been provided.

Best regards. JBF
Comment 3 QA Administrators 2021-10-13 03:41:18 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2021-11-13 05:46:49 UTC
Dear austin.spiegelman,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp