Download it now!
Bug 119353 - Error backup filename
Summary: Error backup filename
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.5.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoSave-AutoRecovery-Backup
  Show dependency treegraph
 
Reported: 2018-08-18 21:36 UTC by wf-ps
Modified: 2019-03-15 02:40 UTC (History)
4 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 wf-ps 2018-08-18 21:36:30 UTC
LibreOfficePortable_6.0.5_Rev_3_MultilingualStandard.paf

LO saves the backup files in the "backup" directory.
Each backup file is given the filename extension *.bak.

I have the original files xxx.odt and xxx.ods. Both get the backup filename xxx.bak in the backup directory.
So the xxx.bak file has sometimes the content of xxx.odt or xxx.ods.
The backup files should be named xxx.odt.bak and xxx.ods.bak.
Comment 1 Jean-Baptiste Faure 2018-08-19 06:20:45 UTC
Confirmed. Set as enhancement.

Best regards. JBF
Comment 2 Xisco Faulí 2018-08-21 16:26:45 UTC
@Jean-Baptiste Faure, could you please provide the steps to reproduce it?
Comment 3 Jean-Baptiste Faure 2018-08-21 17:16:28 UTC
(In reply to Xisco Faulí from comment #2)
> @Jean-Baptiste Faure, could you please provide the steps to reproduce it?

Easy:

- configure LO to make backups: menu Tools > Options > Load/Save > Check "Always create backup copy"
- create two files, one text document and one spreadsheet with the same basename; for example test.odt and test.ods
- open test.ods, change something, save and close the file -> you have a backup test.bak in the backup directory
- open test.odt, change something, save and close -> you still have a backup test.bak and it is a copy of test.odt, the copy of test.ods has been overwritten.

I agree that this use case is a bad workflow, but sometimes it may arise for good reason.

Now, I am not sure if that behavior should not be considered as a bug instead of an enhancement request. Indeed it works as designed but in some corner case there is dataloss (the backup of the first file).

Best regards. JBF
Comment 4 wf-ps 2018-08-23 07:44:54 UTC
Why an enhancement?
All over the world, a backup function has the sole task of backing up the original file. And that is not guaranteed now. So it's a bug in the backup feature.