Version-Release number of selected component: libreoffice-core-4.2.3.3-9.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib/libreoffice/program/soffice.bin --impress --splash-pipe=5 crash_function: __kernel_vsyscall executable: /usr/lib/libreoffice/program/soffice.bin kernel: 3.13.10-200.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: [New LWP 9981] [New LWP 9982] [New LWP 9985] [New LWP 9984] [New LWP 9986] [New LWP 9988] [New LWP 9989] [New LWP 9999] [New LWP 9987] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". warning: the debug information found in "/var/cache/abrt-di/usr/lib/debug/usr/lib/libkrb5.so.3.3.debug" does not match "/lib/libkrb5.so.3" (CRC mismatch). warning: the debug information found in "/var/cache/abrt-di/usr/lib/debug//usr/lib/libkrb5.so.3.3.debug" does not match "/lib/libkrb5.so.3" (CRC mismatch). warning: the debug information found in "/var/cache/abrt-di/usr/lib/debug/usr/lib//libkrb5.so.3.3.debug" does not match "/lib/libkrb5.so.3" (CRC mismatch). Core was generated by `/usr/lib/libreoffice/program/soffice.bin --impress --splash-pipe=5'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x44fd008e in setCachedRendering (this=<optimized out>, rendering=0x0) at /usr/src/debug/kdelibs-4.12.4/kio/kio/delegateanimationhandler_p.h:76 76 /usr/src/debug/kdelibs-4.12.4/kio/kio/delegateanimationhandler_p.h: No such file or directory. Thread 9 (Thread 0xb1e71b40 (LWP 9987)): #0 0xb7759424 in __kernel_vsyscall () No symbol table info available. #1 0x4602cd68 in accept () at ../sysdeps/unix/sysv/linux/i386/socket.S:95 Timeout exceeded: 240 seconds, killing gdb. Looks like gdb hung while generating backtrace. This may be a bug in gdb. Consider submitting a bug report to gdb developers. Please attach coredump from this crash to the bug report if you do.
Created attachment 891680 [details] File: backtrace
Created attachment 891681 [details] File: cgroup
Created attachment 891682 [details] File: core_backtrace
Created attachment 891683 [details] File: dso_list
Created attachment 891684 [details] File: environ
Created attachment 891685 [details] File: exploitable
Created attachment 891686 [details] File: limits
Created attachment 891687 [details] File: maps
Created attachment 891688 [details] File: open_fds
Created attachment 891689 [details] File: proc_pid_status
Created attachment 891690 [details] File: var_log_messages
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.