Version-Release number of selected component: libreoffice-core-4.2.3.2-3.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --writer /home/dgunchev/Documents/0-Gwebu/atpco-db-structure.rtf --splash-pipe=5 crash_function: os::die() executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 os::die() at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #3 VMError::report_and_die() at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #4 crash_handler(int, siginfo_t*, void*) at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #6 ?? #7 os::abort(bool) at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #8 VMError::report_and_die() at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #9 crash_handler(int, siginfo_t*, void*) at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #11 os::is_first_C_frame(frame*) at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #12 VMError::report(outputStream*) at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so #13 VMError::report_and_die() at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.5.1.fc20.x86_64/jre/lib/amd64/server/libjvm.so Potential duplicate: bug 1033501
Created attachment 886519 [details] File: backtrace
Created attachment 886520 [details] File: cgroup
Created attachment 886521 [details] File: core_backtrace
Created attachment 886522 [details] File: dso_list
Created attachment 886523 [details] File: environ
Created attachment 886524 [details] File: hs_err.log
Created attachment 886525 [details] File: limits
Created attachment 886526 [details] File: maps
Created attachment 886527 [details] File: open_fds
Created attachment 886528 [details] File: proc_pid_status
Created attachment 886529 [details] File: var_log_messages
The backtrace in attachment 886519 [details] indicates this is a duplicate of bug 977068, which was fixed for libreoffice-4.1.3.2-7.fc19 via upstream <http://cgit.freedesktop.org/libreoffice/core/commit/?id=13a34f4c6307d1bd2443cbf3fbd83bfdd8cdbafb> "Rewrite Qt4 based nested yield mutex locking." But part of that got later reverted (and is reverted in libreoffice-core-4.2.3.2-3.fc20) via upstream <http://cgit.freedesktop.org/libreoffice/core/commit/?id=daf011870efae282244c0298494820d9a0c6d3bc> "Revert 'Rewrite Qt4 based nested yield mutex locking,'" but unfortunately without any rationale. So it looks somewhat plausible that this got broken again (if it ever was actually truly fixed) with that revert.
*** Bug 1091667 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: This is a fully updated Fedora-20 host with a KDE desktop. The libreoffice-kde package is installed. Scenario: * Open existing document. * Save-As... another copy. * In the "Save-As" dialog box, type new name and click "Save" * Libre-Office crash reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib/libreoffice/program/soffice.bin --writer '/home/esti/My Documents/Enlace Jud\xc3\xado/Noticias-2014.04.29-1.odt' --splash-pipe=5 crash_function: QTransform::type executable: /usr/lib/libreoffice/program/soffice.bin kernel: 3.13.10-200.fc20.i686+PAE package: libreoffice-core-4.2.3.3-9.fc20 reason: soffice.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 502
Another user experienced a similar problem: It has occured when i wanted, through the save box, to delete a file who had a bad spelling name reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --calc --splash-pipe=5 crash_function: QTransform::type executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.14.7-200.fc20.x86_64 package: libreoffice-core-4.2.4.2-18.fc20 reason: soffice.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: This problem happens randomly, whenever using files in CIFS shares particularly. I believe it entails a network response failure or lag, which ends up in a crash. My CIFS shares were set up in /etc/fstab with a credentials file, and the following options: user,noauto,file_mode=0666,dir_mode=0776,sec=ntlm 0 0 The majority of the times I've had this problem is with files greater than 10MB in size. The one with the backtrace is 25.7MB in size and failed when I tried to save it to my ~ directory. I had this problem also in previous versions, particularly in all the 4.1 versions. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --calc '/home/gamaliel/Documents/ETSERVER2/rmoyano/Proyectos/Clustering para DMS/MASTER CENSUS BLOCK variables comparables 2012.xlsx' --splash-pipe=5 crash_function: QTransform::type executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.15.6-200.fc20.x86_64 package: libreoffice-core-4.2.5.2-10.fc20 reason: soffice.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: 1. Went to export a large doc >100 pages as PDF. 2. Found the right directory. 3. Deleted an old pdf file (with a different name). 4. Splat. 5. Would have done the export had the crash not happened. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --splash-pipe=5 crash_function: QTransform::type executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.17.8-200.fc20.x86_64 package: libreoffice-core-4.2.8.2-2.fc20 reason: soffice.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: Used the KDE dialogue to do a save as. En route, I asked it to delete a PDF file by right-mousing on the file and choosing 'Move to Trash' (or similar). File not deleted. LibreOffice crashed. Not v. repeatable but has happened more than once. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --splash-pipe=5 crash_function: QTransform::type executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.18.9-100.fc20.x86_64 package: libreoffice-core-4.2.8.2-6.fc20 reason: soffice.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.