Created attachment 159404 [details] Base .odb file for tracking computer backups. (crash repeatable) This bug was filed from the crash reporting server and is br-b873dc06-5270-4a91-9193-b94cba5f0861. ========================================= Repeatable crashes happened both when (1) copying text from a database column or, after that crashed Base, while (2) trying to recover the .odb file. File was located in my Dell e4200 laptop's home directory. Numerous Base crashes happened over several hours; Base had been exited and re-launched several times during that period. Did not reboot. Specs for laptop (running Peppermint Linux) at https://www.dell.com/support/home/us/en/04/product-support/servicetag/0-SUtJMDM1SkpuTmwrYVB3MXBqR1I5dz090/overview and uname -a info: Linux kitten-e4200 4.15.0-91-generic #92~16.04.1-Ubuntu SMP Fri Feb 28 14:57:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (1) Recreating copy-text crash. Database "BackTrack.odb" (attached to bug report) was open. Opened existing "CPU_Names" table with about 14 entries in Table Data view, clicked into "Usage" field (it was empty), typed in "standby", then double-clicked to highlight the word, intending to paste it elsewhere. Pressed Ctrl-C to copy that plain text, and Base crashed. This was repeated at least three times, in between the crashes while attempting to recover the .odb files. (2) Crash during LibreOffice 6.4 Document Recovery. About 75% of the time, while recovering from the crashes in (1) above, the recovery process itself would crash (2-3 duplicate entries for BackTrack.odb were displayed) . About 25% of the time the recovery process would complete, and Base would function correctly--until it would crash again, though not necessarily by only the copy-text crash (it crashes in several other areas). Thanks. Please excuse the content/format. It's been many years since I submitted something to Bugzilla.
Have tried to reproduce this bug, but no crash appeared while following the description. My System: OpenSUSE 15.1 64bit rpm Linux, LO Version: 6.4.3.1 Build-ID: 4d2b2b47cca498fed6abf712a36d0788901091eb
Not reproducible under Windows 10. Version: 6.4.2.2 (x64) Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3
3 things you can do: 1) Give a try to https://wiki.documentfoundation.org/QA/FirstSteps then test again 2) Perhaps it may help you upgrade your Ubuntu. 16.04 is LTS from 2016, meanwhile there's 18.04 from 2018 and 20.04 release is planned in the next weeks. 3) Provide a minimal step by step process to reproduce this.
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
In doing the following, I believed would this reset my LibreOffice user profile as requested; not sure if it did, as all the custom User Data was still present from before. I removed all traces of all LibreOffice versions (6.3.4 , 6.3.5, 6.4.2), installed only LO 6.3.5.2 Stable, and re-tested Base and Calc. While they don't repeatedly crash now, every time I Save and Exit or Close the database and exit Base, then re-launch Base, it thinks that Base previously crashed and runs the LibreOffice 6.3 Document Recovery module for two (dup-named) documents. This Document Recovery module has an inconsistency in the Status of the recovered documents. Even though the upper message shows "Recovery of your documents was finished. Click 'Finish' to see your documents.", the Status of the Base document(s) remain(s) at "Recovery in Progress" instead of the expected "Finished" or "Recovered" or some such. This loop continues. I click 'Finish' to re-launch the database, do something and Save or nothing, then exit and the next time I launch Base, it again thinks that it crashed and it runs the LibreOffice 6.3 Document Recovery module again. I Discarded the database document rather than recover it, to see if I could cancel this Recovery loop.
On pc Debian x86-64 with master sources updated today, I gave it a try but didn't reproduce this. Several things: - it seems you had several LO versions installed. I think you should remove all LO versions and download 6.4.3 from official website - do you have crashes or weird behaviours on other softwares? - do you reproduce this on another machine? Finally, it could be interesting you retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)
Thank you, Julien Nabet. I will first deinstall current 6.3.5.2 version, install LO 6.4.3 (run it with a backtrace), and if there's *still* a problem, then update Ubuntu to something a bit more recent.
[Automated Action] NeedInfo-To-Unconfirmed
I copied my problematic database over to an Ubuntu 18.2 (Sonya, Mint MATE 1.18.0) system running LibreOffice 6.3.4.2, and there were no problems opening, modifying, saving at all. So it appears that the problem was related to Ubuntu 16.04. On the 18.2 system, I downloaded 6.4.2.2, but hadn't tested the database using LibreOffice 6.4.2.2. Is that necessary, considering the problem didn't reappear?
Thank you for your feedback. Let's put this one to WFM then.