Version-Release number of selected component: mate-panel-1.5.5-1.fc18 Additional info: backtrace_rating: 3 cmdline: /usr/libexec/mate-panel/clock-applet executable: /usr/libexec/mate-panel/clock-applet kernel: 3.8.2-206.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 ?? #5 gtk_object_dispose at gtkobject.c:421 #7 _gtk_plug_send_delete_event at gtkplug.c:383 #8 _gtk_plug_windowing_filter_func at gtkplug-x11.c:280 #9 gdk_event_apply_filters at gdkevents-x11.c:356 #10 gdk_event_translate at gdkevents-x11.c:1052 #11 _gdk_events_queue at gdkevents-x11.c:2336 #17 gtk_main at gtkmain.c:1257 #18 mate_panel_applet_factory_main at mate-panel-applet.c:2126
Created attachment 711895 [details] File: backtrace
Created attachment 711896 [details] File: cgroup
Created attachment 711897 [details] File: core_backtrace
Created attachment 711898 [details] File: dso_list
Created attachment 711900 [details] File: environ
Created attachment 711901 [details] File: limits
Created attachment 711902 [details] File: maps
Created attachment 711903 [details] File: open_fds
Created attachment 711904 [details] File: proc_pid_status
Created attachment 711905 [details] File: var_log_messages
Hi, can you provide a description of the issue? What did you do before the crash?
mate-panel-1.5.6-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-panel-1.5.6-1.fc18
Package mate-panel-1.5.6-1.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 mate-panel-1.5.6-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4453/mate-panel-1.5.6-1.fc18 then log in and leave karma (feedback).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
mate-panel-1.5.6-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.