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
Created attachment 875927 [details] File: backtrace
Created attachment 875928 [details] File: cgroup
Created attachment 875929 [details] File: core_backtrace
Created attachment 875930 [details] File: dso_list
Created attachment 875931 [details] File: environ
Created attachment 875933 [details] File: exploitable
Created attachment 875934 [details] File: limits
Created attachment 875935 [details] File: maps
Created attachment 875936 [details] File: open_fds
Created attachment 875937 [details] File: proc_pid_status
Created attachment 875938 [details] File: var_log_messages
abrt crashed when I tried to delete several of the listed crash reports.
(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?
> 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. :-)
> 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.