I am baffled by a very peculiar problem, every time I open any .odt, .docx, .pdf with either Writer or Draw they show the little floating box with the loading bar. But then at the half way point my system completely freezes. Then killing it with a long press of the on/off button is necessary to be able to restart/do anything.
I have tried different files, opened them with Okular, Onlyoffice etc., its only Libreoffice that completely freaks out. I only have one extension installed, that enables better image export. (ancient I know but it still works and the in built functionality is too bad for my needs: Export As Images » Extensions).
Starting in safemode kinda works, I can start and use the Programs, Writer etc. but when I try to apply a full factory reset, it just freezes again. Tried twice, it just clears the contents of that window but the borders remain. Then it either freezes that Window or my System.
Shutting my System down while it wasnt frozen but LibreOffice was unresponsive, takes a long time.
It gets stuck at the step of
“A stop job is running for User Manager for UID 1000 (x/x mins)” for five to ten minutes.
Also
“systemd-shutdown[1]: waiting for process 69694 (soffice.bin)” takes a while to finish.
Trying to open Writer/Draw without any document shows nothing, Writer shortly displays the blue icon in the taskbar but that soon vanishes. The process soffice.bin then appears as a zombie process in Ksysguard.
Changing users doesnt really help, the loading banner reaches 100% and it doesnt freeze anything, but the Program doesnt actually open.
I have uninstalled fresh and moved to still, then back again, the error persists nonetheless.
So as a summary:
Starting in safe-mode without acceleration works, but it also works fine with acceleration. Also deleting the extension doesnt help.
I however cant use it normally at all.
Either I open a document with LO and it freezes/crashes my System, or I open LO by itself and it just dies in the background/doesnt start and freezes the process to complete unresponsiveness.
So as this is pretty much the first time I want/have to diagnose whats even happening, my primary question is, where do I find or how to I trigger the creation of logs that can be helpful in this case?
Im on the latest updates available for LO and my system (EndeavourOS(Arch), KDE Plasma) and my specs should be quite enough for it. [Ryzen 5900X - 64GB RAM - RX 6800XT - 200GB free space on the home disk]
Thanks, any help is greatly appreciated.