Created attachment 89106 [details] Listing of directory showing empty files (i.e. files with 0 byte count) Problem description: Steps to reproduce: 1. ....Not sure 2. .... 3. .... Current behavior:There were over 26,000 empty backups in ~/.config/libreoffice/4/user/backup. At 10:00 AM over 8,000 had been created since midnight. All were empty. I have attached a ls -la from that directory. Expected behavior: at least one would have been a valid backup. Operating System: Fedora Version: 3.6.6.2 release
How do you get backups from a *.odb-file? I have searched all my different installations of LO - have over 30 versions installed for testing. I couldn't find any file in any backup-folder of this versions. My system: OpenSUSE 12.3 64bit rpm
Robert, have you looked that the directory that I posted? Does it exist? Is there anything in it?
(In reply to comment #2) > Robert, have you looked that the directory that I posted? Does it exist? > Is there anything in it? The folders do exist. I have three folders in ~/.config/libreoffice : 3, 4 and 4-suse (also two old folders, renamed while testing something). In this folders I could open the /user/backup -folder, but there is nothing inside. Backup for database-files doesn't work with the backup-functions of LO. It's because the data in the database where saved independent of the saving-function of LO.
Following previous comment by Robert about backup behaviour for database files, should be notabug. May be I'm wrong, please reopen..
I am still experiencing the problem. I had changed some of the backup values in the options (don't remember what was changed) but I still have to go in and delete these empty files. The database engine is hsql. From what I see the data is stored in the odb file. In there also are my forms, queries, and reports. I discovered this by opening the odb file with an archive manager (ark I believe). I have thought about changing the database engine and tried mysql but the documentation that I found assumes that you know all about it which I don't. I have learned to live with the quirks by manually copying the database and archiving it myself. I am reopening this per ign Christian.
If you only want to save the database-file when the file has just been opened, try the following macro and link it to Tools → Customize → Open Document: https://bugs.freedesktop.org/show_bug.cgi?id=80072#c1 The macro copies one file of the opened *.odb-file to to the Backup-Folder of LO. It will copy up to 5 files and then it will delete the oldest file with copying a new with the same name. So you will have a backup without copying the file by hand. Could it be Bug80072 has the same intention as this bug?
Never independently confirmed by QA team - moving to UNCONFIRMED to make sure they see it. Thanks for your patience and understanding.
@Vince : please retest with a latest production release of LibreOffice and a clean user profile to see if this is still happening. LO is normally incapable of producing backup database files using the builtin backup mechanism used for other document types. This might explain why you were getting 0 byte length files. If you feel that the issue is really that LO should be able to create such backup files, i.e. a new feature, please change your title to reflect that.
I have had a look at ...user/backup for other backup-files I created with a macro. There were a lot backup-files in the folder. All except one were created between 2014-10-14 8:23 and 2014-10-14 8:27. Beginning with the name of the *.odb-file and ending with _0odb up to _1643odb . Most of the files seem to be empty. I don't know which LO-version I used at that time. Could be a 4.2-version, because I had created an example-database for Base Handbook. There are some macros inside. Don't know the reason for this backups, but I could confirm the behavior happend also here. My System: OpenSUSE 12.3 64bit rpm Linux with many different LO-versions for testing ...
Adding self to CC if not already on
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
This bug is hard to reproduce. At this moment the .../user/backup-folder is complete empty here. No file inside, also no database-file.
I received a request to see if this was still happening. I am running Version 5.0.0.5 and it is still happening. I had turned off taking a backup by going to Options - Load/Save - General and clearing Always create backup copies. I turned it back on, opened a Base window and opened a database. After about 4 hours, there were over 86,000 entries in ~/.config/libreoffice/4/user/backup. So, to me it looks like it is still happening. BTW, I am turning backup back off.
I am currently running Fedora 21 64 bit.Version 5.0.0.5 is the latest version available through yum. I am working on upgrading all of my systems to Fedora 23 with my main desktop as the last one to make sure I work out all of the kinks in the upgrade process. It looks like Fed 23 has version 5.0.4. I will try again after upgrading to 23.
Couldn't reproduce with 5.3.0.0 (master) or 5.1.4.1
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
I had this happen in 5.1.6.2 (right when "recovery" managed to destroy half of a sheet, at that) - most likely it was because of a crash, since there's a lock file next to it. Well, that and it crashed from as much as looking at it funny. Do you have a bunch of corresponding "~lock.*#" files next to those zero-sized "*.bak" files too? (And just to be sure, do you have free space on that partition when this happens? I had some bug a few years ago that spammed ~/.xsession-error with several GB of error messages until it suffocated partition with /home/ - and then there's ~/.cache etc)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Vince Radice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
With -no response for many years (since 5.0) -no reproducible steps -no duplicates and very few CCs I'm going to close this as INSUFFICIENTDATA
We shouldn't close a bug if there isn't asked for new information. I will get this buggy behavior while editing forms in Base with macros. Sometimes I see the GUI seems to hang, but is available a little bit later. Then I have a look into the backup folder and could see all this backups. If we know reproducable steps we will report. But it is still a bug, also in LO 7.*!
Created attachment 188379 [details] abc...odg: 243 character long named file that failes autosave, leaving 0-sized file Since autosave is now the default in 7.6, the steps are simply to open the document and make a change. Every 10 minutes another 0-sized file is created (assuming a modification was made to trigger autosave). The problem in this particular case is that it is trying to create a lock file, and adding the lock prefix pushes the filename beyond the 255 character limit.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/65db5b6a34c4cb781e7a9ab813801a0e0d114da5 tdf#71550 autosave: remove empty, new file on failed autosave It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/973ef754442027b7508efbe8a7fb714856a72d1a tdf#71550 autosave: remove empty, new file on failed autosave It will be available in 7.6.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/eef0c5d4d45ba35acfb6d8f7551fe565ca4badaa tdf#71550 autorecovery: use osl::File::Remove when isEmptyFileUrl It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.