Using LO base and having the backup directory on the same partition as the
LO-database leads to increasing respose times of Lo and finally hang up.
Restart of LO then requires retart of Windowes session.
During the LO Session thousends of empty backup files named like:
"databasename.odb_0odb" are stored.
The problem appears on Win 7 X64 and Linus Mint (16 an 17) usinf LO 126.96.36.199.
On ohther operating system I have not testet, but knowing from other user, that it will not appear on openSuse.
Same problem by using LO 188.8.131.52 release. The error occurs frequently on Win7 , rare on openSUSE 13.1.
It dosn't appear every time, I can not figure out what the reason is. I suspect it occurs when I make changes to the forms and reports in the database.
That's right, I just looked it up and found and deleted 8000 remaining rests of two (frequently crashing!) .odb-files with size "0"
(LO 424 on Win7)
Just for me to know (as I look through the LO-Filestructur to find more infos about .odb-files):
is it right,
-- that .odb-files will have no backup and no locking
-- that the working odb is a copy to the memory only
-- that - except closing the odb - there is no way to save odb from memory to disk?
Probably a duplicate of bug 46635.
Best regards. JBF
Dear bug submitter,
In order to confirm your bug we need a document. If possible the document should be minimalistic. If you need to anonymize your document, follow this link: https://wiki.documentfoundation.org/Anonymizing_a_document#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
Altered title to correspond to reported behaviour. There are other similar reports about the ghost backup files, so this might be the earliest report of such, or then again a duplicate of an earlier one
Adding self to CC if not already on
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
This NEEDINFO message was generated on: 2015-07-18
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID 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 FDO
Message generated on: 2015-09-03