Red Hat Bugzilla – Bug 1253374
[abrt] libreoffice-core: ImpEditView::RemoveDragAndDropListeners(): soffice.bin killed by SIGSEGV
Last modified: 2015-12-02 13:16:07 EST
Version-Release number of selected component:
cmdline: /usr/lib64/libreoffice/program/soffice.bin GRASS_geostat_muenster_2012_intro.odp --splash-pipe=5
runlevel: N 5
Thread no. 1 (10 frames)
#0 ImpEditView::RemoveDragAndDropListeners at /usr/src/debug/libreoffice-184.108.40.206/editeng/source/editeng/impedit.cxx:1986
#1 EditEngine::RemoveView at /usr/src/debug/libreoffice-220.127.116.11/editeng/source/editeng/editeng.cxx:344
#2 Outliner::RemoveView at /usr/src/debug/libreoffice-18.104.22.168/editeng/source/outliner/outliner.cxx:1354
#3 sd::Outliner::EndSpelling at /usr/src/debug/libreoffice-22.214.171.124/sd/source/ui/view/Outliner.cxx:342
#4 sd::FuSearch::~FuSearch at /usr/src/debug/libreoffice-126.96.36.199/sd/source/ui/func/fusearch.cxx:97
#6 sd::DrawController::dispose at /usr/src/debug/libreoffice-188.8.131.52/sd/source/ui/unoidl/DrawController.cxx:164
#7 (anonymous namespace)::Frame::setComponent at /usr/src/debug/libreoffice-184.108.40.206/framework/source/services/frame.cxx:1552
#8 (anonymous namespace)::Frame::close at /usr/src/debug/libreoffice-220.127.116.11/framework/source/services/frame.cxx:1783
#9 framework::pattern::frame::closeIt at /usr/src/debug/libreoffice-18.104.22.168/framework/source/inc/pattern/frame.hxx:80
#10 framework::CloseDispatcher::implts_closeFrame at /usr/src/debug/libreoffice-22.214.171.124/framework/source/dispatch/closedispatcher.cxx:491
Potential duplicate: bug 958615
Created attachment 1062671 [details]
Created attachment 1062672 [details]
Created attachment 1062673 [details]
Created attachment 1062674 [details]
Created attachment 1062675 [details]
Created attachment 1062676 [details]
Created attachment 1062677 [details]
Created attachment 1062678 [details]
Created attachment 1062679 [details]
Created attachment 1062680 [details]
Is there a way to reproduce this crash?
It happened to me again today while having the indicated file and another one open at the same time. I was doing copy-pasting of text entries in the presentation.
Still no step-by-step to trigger the crash found...
*** Bug 958615 has been marked as a duplicate of this bug. ***
From the duplicate this is an ancient bug which we weren't able to reproduce the last time it happened, so I don't hold much hope unless there is a reproducible scenario :-(
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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'
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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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
Thank you for reporting this bug and we are sorry it could not be fixed.