Description: crash when I try to open tables or the form. it kills all other open document of LibreOffice (Writer, Calc) recovery is announced successful but I cannot open my database because of the immediate crash after clicking the 'open' button Steps to Reproduce: 1 .open the document (odt) 2. click Tables (right or left no difference) 3. crash Actual Results: crash, demand for recovery Expected Results: open the list of tables in the database Reproducible: Always User Profile Reset: No Additional Info: Linux village 3.16.0-4-686-pae #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) i686 GNU/Linux User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Firefox/52.0
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 136354 [details] the base document I cannot access anymore
The test file opens fine for me on Version: 5.4.1.2 Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 Threads CPU : 8; OS : Mac OS X 10.12.6; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group Your Linux kernel is PAE, surely that is 32bit ? In which case, the crashing is probably due to a kernel bug, you need to change your kernel to one that doesn't crash. See also bug 108619 *** This bug has been marked as a duplicate of bug 108619 ***
Thank you, Alex presently I'm doing a work in progress on my computer which is more important for me than LO Base. I'm just afraid to do any radical changes before the work is done. And yes my kernal is 32 bit but but it didn't crash the Base for at least one year.
(In reply to ogoltsoff from comment #4) > Thank you, Alex > presently I'm doing a work in progress on my computer which is more > important for me than LO Base. I'm just afraid to do any radical changes > before the work is done. > And yes my kernal is 32 bit but but it didn't crash the Base for at least > one year. If you read through bug 108619 you will understand that the problem came about because of changes in some *versions* of the 32bit kernel - these kernels were updated by the respective distribution providers (Debian/Ubuntu/etc) and that is what started the crashing in various X apps - note that Libreoffice is not the only application affected here. The solution is to use whatever mechanism your Linux distribution provides to manage kernel versions, and switch to a kernel that no longer has the problem. Most distros now provide alternative kernel versions that you can use instead of the problematic one.
(In reply to Alex Thurgood from comment #5) > (In reply to ogoltsoff from comment #4) > > Thank you, Alex > > presently I'm doing a work in progress on my computer which is more > > important for me than LO Base. I'm just afraid to do any radical changes > > before the work is done. > > And yes my kernal is 32 bit but but it didn't crash the Base for at least > > one year. > > If you read through bug 108619 you will understand that the problem came > about because of changes in some *versions* of the 32bit kernel - these > kernels were updated by the respective distribution providers > (Debian/Ubuntu/etc) and that is what started the crashing in various X apps > - note that Libreoffice is not the only application affected here. > > The solution is to use whatever mechanism your Linux distribution provides > to manage kernel versions, and switch to a kernel that no longer has the > problem. Most distros now provide alternative kernel versions that you can > use instead of the problematic one. Yes, I read through the cross-out bug and see that in your opinion Debian 8 is the culprit. some day when my work-in-progress be over I'll look into kernels closer right now you may as well cross the bug I reported out