Description of problem:
At the time of crash, I had opened one or two spreadsheets. But the application was "idle" from user point of view - I was working elsewhere and no user action has been performed in past few hours in soffice.
Version-Release number of selected component:
cmdline: /usr/lib64/libreoffice/program/soffice.bin --splash-pipe=5
runlevel: N 5
Thread no. 1 (10 frames)
#0 sd::SdExternalToolEdit::Update at /usr/src/debug/libreoffice-184.108.40.206/sd/source/ui/view/drviews2.cxx:192
#1 ExternalToolEdit::HandleCloseEvent at /usr/src/debug/libreoffice-220.127.116.11/svx/source/core/extedit.cxx:51
#2 operator() at /usr/include/boost/function/function_template.hpp:767
#3 FileChangedChecker::TimerHandler at /usr/src/debug/libreoffice-18.104.22.168/svtools/source/misc/filechangedchecker.cxx:85
#4 Timer::ImplTimerCallbackProc at /usr/src/debug/libreoffice-22.214.171.124/vcl/source/app/timer.cxx:133
#5 CallCallback at /usr/src/debug/libreoffice-126.96.36.199/vcl/inc/saltimer.hxx:53
#6 sal_gtk_timeout_dispatch at /usr/src/debug/libreoffice-188.8.131.52/vcl/unx/gtk/app/gtkdata.cxx:832
#10 g_main_context_iteration at gmain.c:3762
#11 GtkData::Yield at /usr/src/debug/libreoffice-184.108.40.206/vcl/unx/gtk/app/gtkdata.cxx:577
#12 ImplYield at /usr/src/debug/libreoffice-220.127.116.11/vcl/source/app/svapp.cxx:422
Created attachment 933350 [details]
Created attachment 933351 [details]
Created attachment 933352 [details]
Created attachment 933353 [details]
Created attachment 933354 [details]
Created attachment 933355 [details]
Created attachment 933356 [details]
Created attachment 933357 [details]
Created attachment 933358 [details]
Created attachment 933359 [details]
Created attachment 933360 [details]
This seems to be related to perhaps right clicking on an image and edit with external tool. Does that ring any bells, anything like that happen around the time of crash.
(In reply to Caolan McNamara from comment #12)
> This seems to be related to perhaps right clicking on an image and edit with
> external tool. Does that ring any bells, anything like that happen around
> the time of crash.
Partially. Some time ago (while having some .ods file still opened until the crash), I was preparing an .odp presentation with pictures. I did with pictures:
- copy&paste from another presentation
- save picture to the disk
- launch gimp (_not_ from libreoffice, i.e. _no_ right_click -> Edit with External Tool) and edit the picture
- deleting picture from .odp and inserting from the disk
- manipulating with the picture (size, alignment)
I probably deleted the files from the disk after inserting them to the presentation.
The .odp presentation was closed, while libre-office was running due to still open .ods file (had been edited since then, but no pictures). Some days later on, with some activity like reading mails (dont recall details but nothing common with the .odp or .ods or pictures), libre-office crashed.
I can provide the presentation if it can be helpful.
( trying to understand backtrace, my understanding is that some timer was fired to close some (file?) handler of picture, but the handler has been gone (m_pObj=null) )
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
the implementation of this ExternalToolEdit thing starts a timer whose handler restarts it every 3 seconds, and nothing ever stops it....
when the file *does* eventually change, the timer will call up into the document and modify the drawing object which may be long gone at that time.
fixed in upstream master commit 5f6bdce0c0ac687f418821ce328f2987bf340cda
fixed on upstream libreoffice-4-4 branch for 4.4.1 release: commit
fixed on upstream libreoffice-4-3 branch for 4.3.7 release: commit
added patch to F21 package
libreoffice-18.104.22.168-12.fc21 has been submitted as an update for Fedora 21.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreoffice-22.214.171.124-12.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libreoffice-126.96.36.199-1.fc21 has been submitted as an update for Fedora 21.
libreoffice-188.8.131.52-2.fc21 has been submitted as an update for Fedora 21.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.
libreoffice-184.108.40.206-3.fc21 has been submitted as an update for Fedora 21.
libreoffice-220.127.116.11-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.