Version-Release number of selected component: libreoffice-core-4.2.4.2-8.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --impress --splash-pipe=5 crash_function: outputStream::print_cr(char const*, ...) executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 outputStream::print_cr(char const*, ...) at /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64/server/libjvm.so #7 VMError::report(outputStream*) at /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64/server/libjvm.so #8 VMError::report_and_die() at /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64/server/libjvm.so #9 JVM_handle_linux_signal at /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64/server/libjvm.so #10 signalHandler(int, siginfo_t*, void*) at /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.5.x86_64/jre/lib/amd64/server/libjvm.so #12 ?? #13 release at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:146 #14 ~shared_count at /usr/include/boost/smart_ptr/detail/shared_count.hpp:371 #15 ~shared_ptr at /usr/include/boost/smart_ptr/shared_ptr.hpp:328 #16 reset at /usr/include/boost/smart_ptr/shared_ptr.hpp:619
Created attachment 899875 [details] File: backtrace
Created attachment 899876 [details] File: cgroup
Created attachment 899877 [details] File: core_backtrace
Created attachment 899878 [details] File: dso_list
Created attachment 899879 [details] File: environ
Created attachment 899880 [details] File: limits
Created attachment 899881 [details] File: maps
Created attachment 899882 [details] File: open_fds
Created attachment 899883 [details] File: proc_pid_status
Created attachment 899884 [details] File: var_log_messages
crash frame has "TimerScheduler::run" in it. Are you able to reproduce this crash ?
Looks like sdext::presenter::(anonymous namespace)::TimerScheduler thread is still running during exit. (And from a quick glance at the code, any logic to reliably join it well before exit is non-obvious, at least.)
Hi, I was able to reproduce it easily with a file I have but hte problem is that this file is under NDA... I am trying to modify this file to only one slide, then I will be able to send it. In any case, I load the ppsx file which automatically starts on a présentation mode, then I use the [Esc] button and after some time I have ABRT which pops-up.
*** Bug 1079678 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Just closed an impress (Powerpoint) presentation. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/lib64/libreoffice/program/soffice.bin --impress file:///tmp/insolite%202.pps --splash-pipe=5 executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.14.9-200.fc20.x86_64 package: libreoffice-core-4.2.6.2-1.fc20 reason: soffice.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.