Description of problem: Emptied the "Trash;" ane the message popped. Version-Release number of selected component: mate-panel-1.9.4-1.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/mate-panel/notification-area-applet crash_function: gtk_widget_destroy executable: /usr/libexec/mate-panel/notification-area-applet kernel: 3.20.0-0.rc0.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 gtk_widget_destroy at gtkwidget.c:3187 #1 na_tray_manager_handle_dock_request at na-tray-manager.c:302 #2 na_tray_manager_window_filter at na-tray-manager.c:524 #3 gdk_event_apply_filters at gdkevents-x11.c:356 #4 gdk_event_translate at gdkevents-x11.c:1052 #5 _gdk_events_queue at gdkevents-x11.c:2336 #11 gtk_main at gtkmain.c:1257 #12 mate_panel_applet_factory_main at mate-panel-applet.c:2585
Created attachment 991760 [details] File: backtrace
Created attachment 991761 [details] File: cgroup
Created attachment 991762 [details] File: core_backtrace
Created attachment 991763 [details] File: dso_list
Created attachment 991764 [details] File: environ
Created attachment 991765 [details] File: exploitable
Created attachment 991766 [details] File: limits
Created attachment 991767 [details] File: maps
Created attachment 991768 [details] File: open_fds
Created attachment 991769 [details] File: proc_pid_status
Created attachment 991770 [details] File: var_log_messages
It seems that the abrt report was in queue for some reason. Backtrace shows that the issue ocours when you dock your notebook, right? Thread 1 (Thread 0x7f6294d30980 (LWP 3503)): #0 0x0000003320e76356 in IA__gtk_widget_destroy (widget=0x25a73f0) at gtkwidget.c:3187 __inst = 0x25a73f0 __t = 38516224 __r = <optimized out> __FUNCTION__ = "IA__gtk_widget_destroy" #1 0x000000000040879a in na_tray_manager_handle_dock_request (xevent=<optimized out>, manager=0x2521ad0) at na-tray-manager.c:302 icon_window = <optimized out> child = 0x25a73f0 #2 na_tray_manager_window_filter (xev=<optimized out>, event=<optimized out>, data=0x2521ad0) at na-tray-manager.c:524 event = <optimized out> data = 0x2521ad0 xev = <optimized out> xevent = <optimized out> manager = 0x2521ad0 #3 0x000000332145dab3 in gdk_event_apply_filters (filters=<optimized out>, event=0x254de70, xevent=0x7fff64e2c230) at gdkevents-x11.c:356 filter = <optimized out> tmp_list = 0x0 result = <optimized out> #4 gdk_event_translate (display=display@entry=0x24ab020, event=event@entry=0x254de70, xevent=xevent@entry=0x7fff64e2c230, return_exposes=return_exposes@entry=0) at gdkevents-x11.c:1052 I think it crashed at 'gdk_event_apply_filters'. This is fixed in gtk2 upstream now. I'm pretty it will never happen again with next gtk2 release, see https://bugzilla.redhat.com/show_bug.cgi?id=1192722
O.K., I haven't seen this again. (Although I have no notebook, nor a dock thereof, so, no, I was not docking a notebook when this happened.) In any case, feel free to close it with a "upstream" flag if you feel it's appropriate.
Is the problem still exists with mate-panel-1.9.90-1.fc22 ?
Today, i noticed the crash for myself. Forward to upstream. https://github.com/mate-desktop/mate-panel/issues/224
mate-panel-1.9.90-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/mate-panel-1.9.90-2.fc22
Package mate-panel-1.9.90-2.fc22: * should fix your issue, * was pushed to the Fedora 22 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.9.90-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4156/mate-panel-1.9.90-2.fc22 then log in and leave karma (feedback).
*** Bug 1203906 has been marked as a duplicate of this bug. ***
mate-panel-1.9.90-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.