Version-Release number of selected component: dia-0.97.2-7.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: dia crash_function: destroy_object_list executable: /usr/bin/dia kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: 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 899546 [details] File: backtrace
Created attachment 899547 [details] File: cgroup
Created attachment 899549 [details] File: core_backtrace
Created attachment 899551 [details] File: dso_list
Created attachment 899553 [details] File: environ
Created attachment 899555 [details] File: limits
Created attachment 899557 [details] File: maps
Created attachment 899558 [details] File: open_fds
Created attachment 899559 [details] File: proc_pid_status
Created attachment 899560 [details] File: var_log_messages
Another user experienced a similar problem: Colsing a dia window diagram reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: dia crash_function: destroy_object_list executable: /usr/bin/dia kernel: 3.15.10-201.fc20.x86_64 package: dia-0.97.2-7.fc20 reason: dia killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: opened and closed after some time .dia file - there was no change to data - only zoom out or scrooll to see diagram reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: dia doc/reports-batory.dia crash_function: destroy_object_list executable: /usr/bin/dia kernel: 3.18.6-100.fc20.x86_64 package: dia-0.97.2-7.fc20 reason: dia killed by SIGABRT 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.