I recently upgraded Ubuntu from 18.04 x64 to 20.04. Along with that upgrade came Libreoffice 6.4.7.2. Initially, none of my .odb files would function. I finally found a resolution by changing the string db:parameter-name-substitution="false"/>< to db:parameter-name-substitution="true" />< in content.xml of the ,odb file. After that change, I could load my files through LO Base. However, I now find that I can only accomplish a few actions before Base crashes. For example, I have a form with 3 subforms. I can do a search using the form to find a specific record. However, I am limited to no more than 3 actions (cursor movement, update a field, etc.) before Base crashes. Another example is if I search for a record in the form and try to change a field in a subform, Base crashes. A final example is if I only Open the data base, after moving through a few records by moving forward or backward, Base crashes. If I start Base in safe mode, I have the same problem. If I start Base from a terminal, I get no messages at all after the crash. In fact, I can let LO Base recover the data base, restart, let it crash, ad infinitum, and I receive no messages. I am connecting to a MySQL data base using the MySQL direct connector. I have four .odb files representing four data bases. Only one fails. I can provide that .odb file along with the exported tables from MySQL if you should so desire.
Created attachment 172031 [details] strace ofnBase during failure I ran strace while executing the LO Base program against the .odb file that keeps crashing. While running, strace captured the events including the recovery of the file after crashing. Since I don't know what to look for, I am submitting it to you so that you can tell what is happening.
Thank you for reporting the bug. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
I installed Libreoffice 7.1.3, and the problem is no longer present. I can replace my distro LO (6.4.7.2) with LO 7.1.3, but the bug still remains in 6.4.7.2 which is the current version for Ubuntu 20.04. Shouldn't this problem be fixed in 6.4.7.2? If there is a way I can provide more information through logs or tracing, I will be happy to do that Just let me know. Thanks.
I should have mentioned that I did receive 2 messages while running LO Base 7.1.3. The were as follows: (soffice:30900): Gtk-CRITICAL **: 14:22:21.658: gtk_tree_model_iter_nth_child: assertion 'n >= 0' failed (soffice:30900): Gtk-CRITICAL **: 14:22:21.659: gtk_list_store_remove: assertion 'iter_is_valid (iter, list_store)' failed These errors, while listed did not cause the program to crash. I have not tried to reseasrch these messages as yet.
[Automated Action] NeedInfo-To-Unconfirmed
The issue you are reporting is against the Ubuntu version of LibreOffice, so it would be up to the Ubuntu package maintainers to sort that one out and update the packages in their LTS. Given that 6.4.x is EOL for the LibreOffice project, you will probably be reliant on the LTS of Canonical to fix this bug at some stage (probably by forcing update to newer version where the problem has been fixed upstream in the main LO project). Just out of interest, for the failing database file, does it contain a combobox ?
No, there are no combo boxes in any of the forms for the database file in question. I suppose I can find out how to make the package maintainers aware of this problem with LO Base 6.4.7.2, but do you know that off hand?
(In reply to Cecil Carpenter from comment #7) > No, there are no combo boxes in any of the forms for the database file in > question. > > I suppose I can find out how to make the package maintainers aware of this > problem with LO Base 6.4.7.2, but do you know that off hand? Maybe searching on the Launchpad, and if nothing found, reporting it there : https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=libreoffice+crash&search=Search&field.status%3Alist=NEW
Reading comment 3, the pb has been fixed. 6.4 branch is EOL (like 7.0 and 7.1). So let's put this one to WFM then. About gtk errors, it's another problem. I think you should upgrade Ubuntu (it will provide you a more recent LO version from Ubuntu repository) and give a new try. If you got gtk errors, please submit a new bugtracker.