https://bugs.documentfoundation.org/show_bug.cgi?id=152347
--- Comment #2 from Neko-san <nekone...@proton.me> --- Created attachment 183965 --> https://bugs.documentfoundation.org/attachment.cgi?id=183965&action=edit StartCenter .desktop Example Files I had installed it from the repos, however I should elaborate a bit more on that: the debug symbols for LibreOffice itself aren't provided on Arch, so I had to use ASP (https://wiki.archlinux.org/title/Arch_Build_System#Retrieve_PKGBUILD_source_using_Git) to pull the Arch build process for LibreOffice and compile it from the source code to get the debug symbols myself. That aside, I've attempted what you said about the debug backtrace out of curiosity and noticed something very odd. When launched from a .desktop file, that targets a symbolic link to "/usr/lib/libreoffice/program/soffice" from "/usr/bin", the bug is easily reproducible but, when launched directly from a terminal, it doesn't for some reason that I can't identify. Additionally, modifying the .desktop file to point to "/usr/lib/libreoffice/program/soffice" directly, with and without the --backtrace argument, in the .desktop file also causes this to be reproducible; however, attempting to use the backtrace argument via the .desktop file is pointless because, as soon as the program crashes, the spawned terminal window keeping track of the process immediately exits. That said, the manual debug backtrace I provided (by attaching a gdb process via the terminal separately) is the only way that can reliably track what's happening. -- You are receiving this mail because: You are the assignee for the bug.
