Version-Release number of selected component: mate-notification-daemon-1.6.1-2.fc19 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: gdk_screen_get_width executable: /usr/libexec/mate-notification-daemon kernel: 3.12.7-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Jan 18 17:41:45 bieszczady abrt-hook-ccpp[8146]: Saved core dump of pid 8135 (/usr/libexec/mate-notification-daemon) to /var/tmp/abrt/ccpp-2014-01-18-17:41:45-8135 (21663744 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 gdk_screen_get_width at gdkscreen-x11.c:133 #1 get_work_area at stack.c:74 #2 notify_stack_shift_notifications at stack.c:267 #3 notify_stack_remove_window at stack.c:373 #8 gtk_object_dispose at gtkobject.c:421 #10 _notify_timeout_destroy at daemon.c:149 #11 g_hash_table_foreach_remove_or_steal at ghash.c:1412 #12 g_hash_table_foreach_remove at ghash.c:1456 #13 _check_expiration at daemon.c:741 #19 gtk_main at gtkmain.c:1257
Created attachment 852169 [details] File: backtrace
Created attachment 852170 [details] File: cgroup
Created attachment 852171 [details] File: core_backtrace
Created attachment 852172 [details] File: dso_list
Created attachment 852173 [details] File: environ
Created attachment 852174 [details] File: exploitable
Created attachment 852175 [details] File: limits
Created attachment 852176 [details] File: maps
Created attachment 852177 [details] File: open_fds
Created attachment 852178 [details] File: proc_pid_status
Can you describe a little more detailed what happend? Did this issue occurs frequently ?
If I remember correctly, I was having this problem when I was using the "Invest" panel item. I have since removed it from my panel and I don't seem to be experiencing the issue at present.
My apologies! - comment 12 was another issue I had. I think this may have been when I was using dual displays - my laptop screen and a second that was attached to my docking station.
Ok, i will leave it open for a while. Feel free to post here if it happens again to have a good description. Without that i can't talk with or forward the issue to upstream.