Bug 1096937

Summary: [abrt] mate-panel: g_object_notify_queue_freeze(): clock-applet killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ken Dubrick <kdubrick>
Component: mate-panelAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8aff8cb30270f0249d4fb4b5dfc5c998c09a4ec7
Whiteboard: abrt_hash:0615205537029c1efa0253c8736ccbb754ac69d8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-09 18:24:18 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 Ken Dubrick 2014-05-12 17:58:03 UTC 
Description of problem:
Changing the time

Version-Release number of selected component:
mate-panel-1.6.2-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/mate-panel/clock-applet
crash_function: g_object_notify_queue_freeze
executable:     /usr/libexec/mate-panel/clock-applet
kernel:         3.14.3-200.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_object_notify_queue_freeze at gobject.c:227
 #1 g_object_freeze_notify at gobject.c:1095
 #2 gtk_widget_unparent at gtkwidget.c:3105
 #3 gtk_bin_remove at gtkbin.c:122
 #4 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312
 #5 g_type_class_meta_marshalv at gclosure.c:997
 #6 _g_closure_invoke_va at gclosure.c:840
 #9 gtk_container_remove at gtkcontainer.c:1240
 #10 gtk_widget_dispose at gtkwidget.c:8792
 #12 gtk_object_destroy at gtkobject.c:406
Comment 1 Ken Dubrick 2014-05-12 17:58:12 UTC 
Created attachment 894834 [details]
File: backtrace
Comment 2 Ken Dubrick 2014-05-12 17:58:14 UTC 
Created attachment 894835 [details]
File: cgroup
Comment 3 Ken Dubrick 2014-05-12 17:58:16 UTC 
Created attachment 894836 [details]
File: core_backtrace
Comment 4 Ken Dubrick 2014-05-12 17:58:18 UTC 
Created attachment 894837 [details]
File: dso_list
Comment 5 Ken Dubrick 2014-05-12 17:58:23 UTC 
Created attachment 894838 [details]
File: environ
Comment 6 Ken Dubrick 2014-05-12 17:58:25 UTC 
Created attachment 894839 [details]
File: exploitable
Comment 7 Ken Dubrick 2014-05-12 17:58:26 UTC 
Created attachment 894840 [details]
File: limits
Comment 8 Ken Dubrick 2014-05-12 17:58:28 UTC 
Created attachment 894841 [details]
File: maps
Comment 9 Ken Dubrick 2014-05-12 17:58:30 UTC 
Created attachment 894842 [details]
File: open_fds
Comment 10 Ken Dubrick 2014-05-12 17:58:32 UTC 
Created attachment 894843 [details]
File: proc_pid_status
Comment 11 Ken Dubrick 2014-05-12 17:58:34 UTC 
Created attachment 894844 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-06-21 16:38:11 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Wolfgang Ulbrich 2014-07-09 18:24:18 UTC 
No answer from reporter!