Bug 1122172

Summary: [abrt] gobby05: gtk_tree_row_ref_deleted(): gobby-0.5 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: lobocode
Component: gobby05Assignee: Till Maas <opensource>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: opensource
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/31954356081e5e263bc1f04d13382033a3fb9071
Whiteboard: abrt_hash:b7de00ac284f3f364ca8842e3b7b32628c5872a7
Fixed In Version: gtk3-3.14.6-1.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-15 04:27:50 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 lobocode 2014-07-22 17:14:46 UTC 
Version-Release number of selected component:
gobby05-0.4.94-5.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/gobby-0.5
crash_function: gtk_tree_row_ref_deleted
executable:     /usr/bin/gobby-0.5
kernel:         3.15.5-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_tree_row_ref_deleted at gtktreemodel.c:2130
 #1 gtk_tree_row_reference_deleted at gtktreemodel.c:2509
 #2 gtk_tree_view_row_deleted at gtktreeview.c:9057
 #7 gtk_tree_model_row_deleted at gtktreemodel.c:1867
 #8 emit_row_deleted_for_row at gtkfilesystemmodel.c:331
 #9 remove_file at gtkfilesystemmodel.c:1912
 #10 gtk_file_system_model_monitor_change at gtkfilesystemmodel.c:1257
 #11 ffi_call_unix64 at ../src/x86/unix64.S:76
 #12 ffi_call at ../src/x86/ffi64.c:522
 #13 g_cclosure_marshal_generic_va at gclosure.c:1550
Comment 1 lobocode 2014-07-22 17:14:50 UTC 
Created attachment 919979 [details]
File: backtrace
Comment 2 lobocode 2014-07-22 17:14:51 UTC 
Created attachment 919980 [details]
File: cgroup
Comment 3 lobocode 2014-07-22 17:14:52 UTC 
Created attachment 919981 [details]
File: core_backtrace
Comment 4 lobocode 2014-07-22 17:14:53 UTC 
Created attachment 919982 [details]
File: dso_list
Comment 5 lobocode 2014-07-22 17:14:54 UTC 
Created attachment 919983 [details]
File: environ
Comment 6 lobocode 2014-07-22 17:14:56 UTC 
Created attachment 919984 [details]
File: exploitable
Comment 7 lobocode 2014-07-22 17:14:57 UTC 
Created attachment 919985 [details]
File: limits
Comment 8 lobocode 2014-07-22 17:14:58 UTC 
Created attachment 919986 [details]
File: maps
Comment 9 lobocode 2014-07-22 17:15:00 UTC 
Created attachment 919987 [details]
File: open_fds
Comment 10 lobocode 2014-07-22 17:15:01 UTC 
Created attachment 919988 [details]
File: proc_pid_status
Comment 11 lobocode 2014-07-22 17:15:02 UTC 
Created attachment 919989 [details]
File: var_log_messages
Comment 12 Fedora Update System 2014-12-12 04:53:01 UTC 
gtk3-3.14.6-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/gtk3-3.14.6-1.fc21
Comment 13 Fedora Update System 2014-12-13 09:45:59 UTC 
Package gtk3-3.14.6-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gtk3-3.14.6-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-16867/gtk3-3.14.6-1.fc21
then log in and leave karma (feedback).
Comment 14 Fedora Update System 2014-12-15 04:27:50 UTC 
gtk3-3.14.6-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.