Bug 1076699 - [abrt] dia: table_dialog_free(): dia killed by SIGABRT
Summary: [abrt] dia: table_dialog_free(): dia killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dia
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Huzaifa S. Sidhpurwala
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b62485b911ef7841e242ed71812...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-14 20:48 UTC by liuyuqi.crh
Modified: 2015-06-29 19:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:28:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (27.28 KB, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: cgroup (159 bytes, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: core_backtrace (15.50 KB, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: dso_list (10.24 KB, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: environ (1.60 KB, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: limits (1.29 KB, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: maps (33.42 KB, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: open_fds (436 bytes, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: proc_pid_status (783 bytes, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details
File: var_log_messages (1.89 KB, text/plain)
2014-03-14 20:48 UTC, liuyuqi.crh
no flags Details

Description liuyuqi.crh 2014-03-14 20:48:28 UTC
Description of problem:
I used dia to draw a database diagram. When I created a table object, I went into its property window to change the font size of its name. I gave an arbitary value "1.0" or "0.9" (which I cannot remember clearly), and all the windows belongs to dia just disappeared.

Version-Release number of selected component:
dia-0.97.2-7.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        dia
crash_function: table_dialog_free
executable:     /usr/bin/dia
kernel:         3.12.5-302.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #7 table_dialog_free at table_dialog.c:86
 #8 table_destroy at table.c:495
 #9 destroy_object_list at object.c:338
 #10 delete_objects_free at undo.c:685
 #11 undo_delete_lowest_transaction at undo.c:154
 #12 undo_set_transactionpoint at undo.c:184
 #13 properties_respond at properties-dialog.c:155
 #14 g_cclosure_marshal_VOID__INTv at gmarshal.c:410
 #15 _g_closure_invoke_va at gclosure.c:840
 #18 gtk_dialog_response at gtkdialog.c:932

Comment 1 liuyuqi.crh 2014-03-14 20:48:33 UTC
Created attachment 874626 [details]
File: backtrace

Comment 2 liuyuqi.crh 2014-03-14 20:48:35 UTC
Created attachment 874627 [details]
File: cgroup

Comment 3 liuyuqi.crh 2014-03-14 20:48:37 UTC
Created attachment 874628 [details]
File: core_backtrace

Comment 4 liuyuqi.crh 2014-03-14 20:48:38 UTC
Created attachment 874629 [details]
File: dso_list

Comment 5 liuyuqi.crh 2014-03-14 20:48:41 UTC
Created attachment 874630 [details]
File: environ

Comment 6 liuyuqi.crh 2014-03-14 20:48:43 UTC
Created attachment 874631 [details]
File: limits

Comment 7 liuyuqi.crh 2014-03-14 20:48:48 UTC
Created attachment 874632 [details]
File: maps

Comment 8 liuyuqi.crh 2014-03-14 20:48:50 UTC
Created attachment 874633 [details]
File: open_fds

Comment 9 liuyuqi.crh 2014-03-14 20:48:52 UTC
Created attachment 874634 [details]
File: proc_pid_status

Comment 10 liuyuqi.crh 2014-03-14 20:48:54 UTC
Created attachment 874635 [details]
File: var_log_messages

Comment 11 liuyuqi.crh 2014-03-14 22:12:12 UTC
Another user experienced a similar problem:

I wanted to delete an object in dia, so I typed <del>, instead of deleting the object, the program exited.

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        dia
crash_function: table_dialog_free
executable:     /usr/bin/dia
kernel:         3.12.5-302.fc20.i686
package:        dia-0.97.2-7.fc20
reason:         dia killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 12 Fedora End Of Life 2015-05-29 11:15:23 UTC
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.

Comment 13 Fedora End Of Life 2015-06-29 19:28:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.