https://bugs.documentfoundation.org/show_bug.cgi?id=164482
BDF <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEEDINFO |RESOLVED --- Comment #14 from BDF <[email protected]> --- Thankfully there was no hurry as university kept me busy until the end of last month. Today I had a whole day to do all the testing and I have good and bad news. # The bad one news are that even after several hours of trying I wasn't able to setup a debugging environment on my system and run it. >From what I understood the main problem was that I was using the flatpack version [1] of LibreOffice and that the sandboxed nature of flatpacks were messing with gdb and --backtrace. I tired to solve with this with the help of ChatGPT and tested everything I could, but with no luck. As I had no idea what the problem was, I asked ChatGPT to summarise the problem: o) gdb and --backtrace Issue: I initially tried to use gdb with the --backtrace option, but received the error: “Can't find the tool 'gdb', --backtrace option will be ignored.” I resolved this by installing the necessary debug symbols (flatpak install org.libreoffice.LibreOffice.Debug) and enabling debuginfod to download the required symbols. o) Running flatpak run inside gdb: When attempting to run the application directly with gdb, I encountered an issue with the --backtrace flag, as flatpak didn’t seem to pass it properly to the LibreOffice binary. The application also didn’t consistently reproduce the crash, making it difficult to capture a backtrace during a live session. Because I was testing on a live system, I wasn't to worried breaking or messing up anything so I also installed the package from the ubuntu repo (24.2.7.2 [1]). But there I couldn't get the gdbtrace.log for whatever reason. # The good news is that the bug seems to no longer be an issue as I can no longer reproduce it. Not on my test live USB as well as on my system I saw it the encountered it the first time. Neither in my uploaded demo file nor in my arrow heavy file that once was the reason I filed this bug report. As I had pretty much no time for testing in the last months I can't tell you if the "fix" is related to the ubuntu base, the KDEneon changes on top, changes in the Plasma desktop or if maybe a change in LibreOffice did the trick. I may can recheck on an older system (eg. with plasma 6.1/2/3) but I'm not sure if there would be a great interest in this as a) nobody was able to reproduce the bug and b) who would install an old version of LibreOffice or Ubuntu if it's not an LTS version? Long story short: As I can no longer reproduce the bug I will close this bug report but will open it again once it pops up again (and then sink even more hours into finding out how to debug with flatpack) @BogdanB: Thank you for your patience @Julien Nabet: Thank you for the link to the site explaining backtrace though I was not able to get one [1] Version: 25.2.4.3 (X86_64) / LibreOffice Community Build ID: 33e196637044ead23f5c3226cde09b47731f7e27 CPU threads: 12; OS: Linux 6.11; UI render: default; VCL: gtk3 Locale: de-AT (de_AT.UTF-8); UI: de-DE Flatpak Calc: threaded [2] Version: 24.2.7.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 16; OS: Linux 6.11; UI render: default; VCL: gtk3 Locale: en-US (C.UTF-8); UI: en-US Ubuntu package version: 4:24.2.7-0ubuntu0.24.04.4 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
