Bug 1046521

Summary: [abrt] guestfs-browser-0.2.2-1.fc18: g_slice_free1: Process /usr/bin/guestfs-browser was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Robert Hill <rob_dav_hill>
Component: guestfs-browserAssignee: Richard W.M. Jones <rjones>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: rjones, rob_dav_hill, robt.d.hill
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/76b3e1d609e4d3f0f1bb92b4d7fde597d4b1beeb
Whiteboard: abrt_hash:539621b850f354260663efd7ed592584939169ac
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:37:03 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Robert Hill 2013-12-26 02:29:40 UTC 
Version-Release number of selected component:
guestfs-browser-0.2.2-1.fc18

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/guestfs-browser
crash_function: g_slice_free1
executable:     /usr/bin/guestfs-browser
kernel:         3.11.10-100.fc18.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 g_slice_free1 at gslice.c:1111
 #7 gtk_file_system_model_finalize at gtkfilesystemmodel.c:1003
 #9 stop_loading_and_clear_list_model at gtkfilechooserdefault.c:6516
 #10 gtk_file_chooser_default_finalize at gtkfilechooserdefault.c:858
 #12 gtk_box_forall at gtkbox.c:1251
 #13 gtk_container_destroy at gtkcontainer.c:1073
 #18 gtk_object_dispose at gtkobject.c:421
 #20 gtk_box_forall at gtkbox.c:1251
 #21 gtk_container_destroy at gtkcontainer.c:1073
 #26 gtk_object_dispose at gtkobject.c:421
Comment 1 Robert Hill 2013-12-26 02:29:45 UTC 
Created attachment 841698 [details]
File: backtrace
Comment 2 Robert Hill 2013-12-26 02:29:47 UTC 
Created attachment 841699 [details]
File: cgroup
Comment 3 Robert Hill 2013-12-26 02:29:49 UTC 
Created attachment 841700 [details]
File: core_backtrace
Comment 4 Robert Hill 2013-12-26 02:29:50 UTC 
Created attachment 841701 [details]
File: dso_list
Comment 5 Robert Hill 2013-12-26 02:29:54 UTC 
Created attachment 841702 [details]
File: environ
Comment 6 Robert Hill 2013-12-26 02:29:56 UTC 
Created attachment 841703 [details]
File: limits
Comment 7 Robert Hill 2013-12-26 02:29:57 UTC 
Created attachment 841704 [details]
File: maps
Comment 8 Robert Hill 2013-12-26 02:29:59 UTC 
Created attachment 841705 [details]
File: open_fds
Comment 9 Robert Hill 2013-12-26 02:30:02 UTC 
Created attachment 841706 [details]
File: proc_pid_status
Comment 10 Robert Hill 2013-12-26 02:30:04 UTC 
Created attachment 841707 [details]
File: var_log_messages
Comment 11 Richard W.M. Jones 2014-01-02 12:45:59 UTC 
Works for me in Fedora 20.  Do you know if you were doing any
particular operation at the time, eg. just opening guestfs-browser,
opening a disk image, etc?

There is no "smoking gun" in the stack trace except that it
crashed trying to free a gtk object.
Comment 12 Fedora End Of Life 2014-02-05 22:37:03 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
Comment 13 robt.d.hill 2015-12-28 14:05:36 UTC 
I don’t think I was doing anything in particular. Sorry for not replying in a timely manner. I don't think I had registered back then. This should be closed.