Bug 896321

Summary: [abrt] xfce4-appfinder-4.10.0-3.fc18: g_type_check_instance_cast: Process /usr/bin/xfce4-appfinder was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: sm301
Component: xfce4-appfinderAssignee: Kevin Fenzi <kevin>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, andresleoon, antivir88, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:6f6d1b36b470c53ffd9937c9aa73ace58e09dd9c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-08 22:49:44 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 sm301 2013-01-17 02:50:18 UTC 
Version-Release number of selected component:
xfce4-appfinder-4.10.0-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        xfce4-appfinder
crash_function: g_type_check_instance_cast
executable:     /usr/bin/xfce4-appfinder
kernel:         3.6.10-4.fc18.i686
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_cast at gtype.c:3997
 #1 xfce_appfinder_window_icon_theme_changed at appfinder-window.c:1452
 #2 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
 #3 _g_closure_invoke_va at gclosure.c:840
 #6 do_theme_change at gtkicontheme.c:635
 #7 update_current_theme at gtkicontheme.c:439
 #8 g_cclosure_marshal_VOID__PARAM at gmarshal.c:1042
 #14 g_object_notify_by_spec_internal at gobject.c:1135
 #15 g_object_notify at gobject.c:1177
 #16 _gtk_settings_handle_event at gtksettings.c:1988

Potential duplicate: bug 832489
Comment 1 sm301 2013-01-17 02:50:21 UTC 
Created attachment 679978 [details]
File: backtrace
Comment 2 sm301 2013-01-17 02:50:23 UTC 
Created attachment 679979 [details]
File: cgroup
Comment 3 sm301 2013-01-17 02:50:25 UTC 
Created attachment 679980 [details]
File: core_backtrace
Comment 4 sm301 2013-01-17 02:50:27 UTC 
Created attachment 679981 [details]
File: dso_list
Comment 5 sm301 2013-01-17 02:50:29 UTC 
Created attachment 679982 [details]
File: environ
Comment 6 sm301 2013-01-17 02:50:31 UTC 
Created attachment 679983 [details]
File: limits
Comment 7 sm301 2013-01-17 02:50:34 UTC 
Created attachment 679984 [details]
File: maps
Comment 8 sm301 2013-01-17 02:50:36 UTC 
Created attachment 679985 [details]
File: open_fds
Comment 9 sm301 2013-01-17 02:50:38 UTC 
Created attachment 679986 [details]
File: proc_pid_status
Comment 10 sm301 2013-01-17 02:50:40 UTC 
Created attachment 679987 [details]
File: var_log_messages
Comment 11 jhon andres leon bernal 2013-01-28 03:50:37 UTC 
the video fail sometimes

backtrace_rating: 4
Package: xfce4-appfinder-4.10.0-3.fc18
OS Release: Fedora release 18 (Spherical Cow)
Comment 12 Fedora Update System 2013-03-30 03:28:05 UTC 
xfce4-appfinder-4.10.0-5.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/xfce4-appfinder-4.10.0-5.fc18
Comment 13 Fedora Update System 2013-04-01 03:23:04 UTC 
Package xfce4-appfinder-4.10.0-5.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xfce4-appfinder-4.10.0-5.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4601/xfce4-appfinder-4.10.0-5.fc18
then log in and leave karma (feedback).
Comment 14 Fedora Update System 2013-04-08 22:49:46 UTC 
xfce4-appfinder-4.10.0-5.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.