Created attachment 96277 [details] This is the error log file referenced by the command ;line crash report Problem description: New catastrophic problem from out of the blue. I loaded a a docx file, tried to export it as a PDF and LO crashed. Now all saving, exporting or opening a new document within LO causes a catastrophic crash. LO is unusable. Steps to reproduce: 1. Open LO. I can open existing files or start a new file. 2. When I try to save the file LO crashes. Or when I try to export the file LO crashes. Or when I try to open a new file using the open file dialog LO crashes. I can open a file from the recent document que If I run "soffice" from the command line I get the following pnb@linux-qcore:~> soffice # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f37216d8270, pid=5466, tid=139874848377408 # # JRE version: OpenJDK Runtime Environment (7.0_51) (build 1.7.0_51-b00) # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x33270] g_type_check_instance_cast+0x10 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/jvm-5466/hs_error.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # [error occurred during error reporting , id 0xb] pnb@linux-qcore:~> ^C Current behavior: Expected behavior: Operating System: openSUSE Version: 4.1.5.3 release
as the problem is java related...do you need java? how about disabling it: tools->options->LibreOffice Advanced and untick "use a java runtime environment" If this doesn't work can you upload the docx file pls? Cheers
I tried running LO without Java to see if that would help - it still crashed when opening a file from within LO, exporting as pdf or saving. I did find a work around - Under tools ->LibreOffice ->General ->Open/Save dialogs check "Use LibreOffice dialogs". When this is checked and I am using LO dialogs everything works as it should. Whew, I can live with this. I do not believe this issue was related to the particular .docx file I loaded rather it is something in KDE or some other system API that has recently changed - I have no clue.
I have the same issue, and the workaround works for me too. I'm not using Gnome or KDE, so it's unlikely to be an issue with them.
I also happened to run into this bug. Downstream (more info): https://bugs.sabayon.org/show_bug.cgi?id=4665 Summary: LO with gtk theme oxygen-gtk causes segfault when opening file dialog. Workaround: Change gtk theme to something different than oxygen-gtk. I myself haven't tested it, so confirmation would be nice. OS: Sabayon LO version: 4.2.1.1
*** This bug has been marked as a duplicate of bug 76121 ***