Bug 1077713

Summary: [abrt] gnome-abrt: is_end(): python2.7 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Evan McNabb <emcnabb>
Component: gnome-abrtAssignee: Jakub Filak <jfilak>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: emcnabb, jberan, jfilak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8a02e358e3d762989425492fb096e423887666da
Whiteboard: abrt_hash:4a4f54f33d70453480fef1237e5ef38fdf0735ce
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-21 09:20:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Evan McNabb 2014-03-18 13:20:19 UTC 
Version-Release number of selected component:
gnome-abrt-0.3.6-1.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/gnome-abrt
crash_function: is_end
executable:     /usr/bin/python2.7
kernel:         3.13.6-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 is_end at gsequence.c:200
 #1 gtk_list_store_remove at gtkliststore.c:1233
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:522
 #4 g_callable_info_invoke at girepository/gicallableinfo.c:680
 #5 g_function_info_invoke at girepository/gifunctioninfo.c:274
 #6 _invoke_callable at pygi-invoke.c:64
 #7 pygi_callable_info_invoke at pygi-invoke.c:652
 #8 _wrap_g_callable_info_invoke at pygi-invoke.c:675
 #9 _callable_info_call at pygi-info.c:428
Comment 1 Evan McNabb 2014-03-18 13:20:28 UTC 
Created attachment 875927 [details]
File: backtrace
Comment 2 Evan McNabb 2014-03-18 13:20:31 UTC 
Created attachment 875928 [details]
File: cgroup
Comment 3 Evan McNabb 2014-03-18 13:20:33 UTC 
Created attachment 875929 [details]
File: core_backtrace
Comment 4 Evan McNabb 2014-03-18 13:20:35 UTC 
Created attachment 875930 [details]
File: dso_list
Comment 5 Evan McNabb 2014-03-18 13:20:37 UTC 
Created attachment 875931 [details]
File: environ
Comment 6 Evan McNabb 2014-03-18 13:20:42 UTC 
Created attachment 875933 [details]
File: exploitable
Comment 7 Evan McNabb 2014-03-18 13:20:43 UTC 
Created attachment 875934 [details]
File: limits
Comment 8 Evan McNabb 2014-03-18 13:20:45 UTC 
Created attachment 875935 [details]
File: maps
Comment 9 Evan McNabb 2014-03-18 13:20:48 UTC 
Created attachment 875936 [details]
File: open_fds
Comment 10 Evan McNabb 2014-03-18 13:20:50 UTC 
Created attachment 875937 [details]
File: proc_pid_status
Comment 11 Evan McNabb 2014-03-18 13:20:52 UTC 
Created attachment 875938 [details]
File: var_log_messages
Comment 12 Evan McNabb 2014-03-18 13:24:16 UTC 
abrt crashed when I tried to delete several of the listed crash reports.
Comment 13 Jakub Filak 2014-03-19 15:49:25 UTC 
(In reply to Evan McNabb from comment #12)
> abrt crashed when I tried to delete several of the listed crash reports.

Thank you for the report. I have a couple of questions :)

Did you try to delete several of the reports or all of them?
Do you remember how many problems did you selected?
Was the first problem selected?
Was the last problem selected?
Did you do any action before trying to delete the problems?
Comment 14 Evan McNabb 2014-03-19 17:13:29 UTC 
> Thank you for the report. I have a couple of questions :)

Sorry for the detail lacking bug report. :-)

> Did you try to delete several of the reports or all of them?
> Do you remember how many problems did you selected?
> Was the first problem selected?
> Was the last problem selected?

There were several reports that I wanted to delete, so I started with the first, clicked delete, and proceeded through the list. The crash happened towards the beginning of that process. I seem to recall (wasn't really paying attention) that abrt momentarily froze, so perhaps I pressed delete twice on one of the reports?

> Did you do any action before trying to delete the problems?

I had viewed several of the reports, but I don't recall exactly what I had done in the tool.

I know this is a vague bug, so if you can't reproduce feel free to close. :-)
Comment 15 Jakub Filak 2014-03-21 09:20:38 UTC 
> There were several reports that I wanted to delete, so I started with the
> first, clicked delete, and proceeded through the list. The crash happened
> towards the beginning of that process. I seem to recall (wasn't really
> paying attention) that abrt momentarily froze, so perhaps I pressed delete
> twice on one of the reports?

Thank you! I verified that the double deleting works fine.

> 
> I know this is a vague bug, so if you can't reproduce feel free to close. :-)

Gtk3 internally stores the list of problems in a binary tree. This crash happened due to a dangling pointer to a parent tree node of the deleted problem. I took a look at Gtk3' source codes but I didn't find anything suspicious. In order to be able to reproduce this crash, we would need to know the original tree and the sequence of the removed nodes.

Closing this bug report as INSUFFICIENT_DATA, but please feel free to report any further bugs you find.