Red Hat Bugzilla – Bug 993063
[abrt] dia-0.97.2-5.fc19: destroy_object_list: Process /usr/bin/dia was killed by signal 6 (SIGABRT)
Last modified: 2015-02-18 09:04:19 EST
Description of problem:
This error occurs after editing+saving+closing a diagram. The diagram contains only elements from the 'Database' sheet: tables and references.
Version-Release number of selected component:
cmdline: dia /home/philipp/repos/teacherapp/model.dia
runlevel: N 5
Thread no. 1 (10 frames)
#6 destroy_object_list at object.c:338
#7 layer_destroy at diagramdata.c:229
#8 diagram_data_finalize at diagramdata.c:140
#10 ddisplay_really_destroy at display.c:1361
#15 gtk_object_dispose at gtkobject.c:421
#17 ddisp_destroy at display.c:1200
#18 ddisplay_close at display.c:1253
#19 ddisplay_delete at disp_callbacks.c:981
#20 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#25 gtk_widget_event_internal at gtkwidget.c:5017
Potential duplicate: bug 893167
Created attachment 782851 [details]
Created attachment 782852 [details]
Created attachment 782853 [details]
Created attachment 782854 [details]
Created attachment 782855 [details]
Created attachment 782856 [details]
Created attachment 782857 [details]
Created attachment 782858 [details]
Created attachment 782859 [details]
Created attachment 782860 [details]
(In reply to tastybug from comment #0)
> Potential duplicate: bug 893167
Yes, the same backtrace occurs in bug #893167 and bug #893167.
Pity it's not reproducible on demand.
It seems to crash every time for me. Ill try to strip down my dia file to the bare necessary content (that still causes crashes) and attach it.
Created attachment 786939 [details]
DIA model that causes crashes
I can reproduce the crash on my machine doing the following steps:
1. Open the attached dia file
2. double click one of the entities, say "student"
3. add an attribute, just provide some name
4. save the file
5. close the window associated with that dia file -> crash
That does the trick. Thanks !
I can't reproduce it with upstream git snapshot, so it probably has already been fixed upstream, but I haven't been able to locate the commit, so we'll probably need to wait for next release.
*** Bug 998124 has been marked as a duplicate of this bug. ***
*** Bug 1045145 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem:
reason: dia killed by SIGABRT
runlevel: N 5
dia-0.97.3-1.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 dia-0.97.3-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
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.
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.