Red Hat Bugzilla – Bug 973462
[abrt] gnome-abrt-0.2.12-2.fc18: ci_get_name: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Last modified: 2016-11-30 19:44:30 EST
Description of problem:
I was trying to convince abrt to report a problem with mythtv-frontend.
After about the 3rd attempt without relaunching abrt in between, abrt just up and died.
Version-Release number of selected component:
cmdline: python /usr/bin/gnome-abrt
runlevel: N 5
var_log_messages: Jun 11 18:06:05 mythtv abrt: Saved core dump of pid 29452 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-06-11-18:06:01-29452 (62263296 bytes)
Thread no. 1 (10 frames)
#0 ci_get_name at config_item_info.c:77
#1 ec_get_name at event_config.c:64
#2 libreport_load_single_event_config_data_from_user_storage at secrets.c:1516
#3 load_single_event_config_foreach at workflow_config_dialog.c:119
#4 g_list_foreach at glist.c:942
#5 load_events_foreach_workflow at workflow_config_dialog.c:124
#6 g_hash_table_foreach at ghash.c:1524
#7 load_workflow_config_data_from_user_storage at workflow_config_dialog.c:129
#8 show_config_list_dialog at config_dialog.c:348
#9 p_show_events_list_dialog at configure.c:31
Created attachment 759897 [details]
Created attachment 759898 [details]
Created attachment 759899 [details]
Created attachment 759900 [details]
Created attachment 759901 [details]
Created attachment 759902 [details]
Created attachment 759903 [details]
Created attachment 759904 [details]
Created attachment 759905 [details]
Thank you for the bug report. Could you please attach coredump? The file should be placed in /var/tmp/abrt/ccpp-2013-06-11-18:06:01-29452
At this point, all I have in that directory is "time", "uid", and a file called "not-reportable."
"time" and "uid" have the original timestamps, but "not-reportable" is timestamped August 6, which just so happens to match the install date of
("not-reportable" is only 15 minutes newer).
If it truly was "not-reportable," then maybe the core dump wouldn't have done any good, anyway. :-(
I'm okay with closing this because of insufficient data.
Thank you for your efforts in solving this bug.