Archlinux. Kernel 5.1.8. extra/libreoffice-fresh 6.2.4-1 [installed] extra/libreoffice-fresh-de 6.2.4-1 [installed] extra/libreoffice-fresh-en-gb 6.2.4-1 [installed] extra/libreoffice-fresh-fr 6.2.4-1 [installed] community/libreoffice-extension-texmaths 0.48-1 [installed] Under Wayland using sway version 1.1-rc1 Always reproducable, since a few months actually ;) So now I thought: OK, lets report it :) `libreoffice` free(): invalid pointer Application Error Please see attached `env` and `strace libreoffice` and `journalctl during crash` as well. Please advise.
Created attachment 152376 [details] output of 'strace libreoffice'
Created attachment 152377 [details] output of 'env'
Created attachment 152378 [details] journalctl during the crash
Could you give a try to https://wiki.documentfoundation.org/QA/FirstSteps ? Then if you still reproduce this, would it be possible to have a stacktrace (different from strace), see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace ?
Hi there, thanks for the quick comment. I feel that I did the steps mentioned here: 'First steps to take before submitting a bug' 1 The very first step: reproduce bug using latest fresh/still version Archlinux should provide the latest. Updated my system 1 week ago. Bug present since long. Lots of updates to latest versions happened before reporting. Bug 100% consistant and reproducable. 2 Corrupted user profile I can give that a try. Even though I would say if libreoffice crashes because of a profile setting, then this should still considered a bug worth fixing. 3 Graphics-related issues (OpenGL) This step asks me to do stuff within Libreoffice, which I can't as it crashes ;) 4 Computation-related issues in Calc (OpenCL) This step asks me to do stuff within Libreoffice, which I can't as it crashes ;) As for the backtrace: Absolutely this is a very reasonable request and I will get right on to it. Thanks!
Created attachment 152390 [details] output of 'soffice --valgrind'
Created attachment 152391 [details] output of 'VALGRIND=callgrind /usr/lib/libreoffice/program/soffice'
Created attachment 152392 [details] callgrind.out.xxxx created by 'VALGRIND=callgrind /usr/lib/libreoffice/program/soffice'
Hope that helps. Please let me know. Thanks a lot in advance!
Knuth: you retrieved a Valgrind and a Callgrind trace. I noticed Antidote in your Valgrind trace. For the test, could you remove any non default extension + rename your LO directory profile and give a new try? "backtrace" part is first paragraph in https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace I quote: "The backtrace is useful for analysing the reasons why an application crashes or freezes. The backtrace can be run without the debugging packages, but it wont be as useful, but still could potentially provide at least some information. You might use the following steps:..."
Hi Julien, Thanks for reminding me of the Antidote (great product by the way :))! I did now try (as you had suggested) to start with a clean libreoffice user profile. And now it works. I appologize and will remember the importance of user profiles for libreoffice going forward. Now is the question: Do you still want to keep investigating or 'case closed' ? From my end, it would be OK to close the ticket. Knuth
PS: Here is what I did exactly to resolve the problem: mv ~/.config/libreoffice ~/.config/libreoffice.ORIG
[Automated Action] NeedInfo-To-Unconfirmed
Let's put this one to WFM then.