Version-Release number of selected component: mate-notification-daemon-1.6.1-2.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: g_return_if_fail_warning executable: /usr/libexec/mate-notification-daemon kernel: 3.15.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 5242 Truncated backtrace: Thread no. 1 (10 frames) #2 g_return_if_fail_warning at gmessages.c:1034 #3 gdk_screen_get_width at gdkscreen-x11.c:133 #4 get_work_area at stack.c:74 #5 notify_stack_shift_notifications at stack.c:267 #6 notify_stack_remove_window at stack.c:373 #11 gtk_object_dispose at gtkobject.c:421 #13 _notify_timeout_destroy at daemon.c:149 #14 g_hash_table_foreach_remove_or_steal at ghash.c:1412 #15 g_hash_table_foreach_remove at ghash.c:1456 #16 _check_expiration at daemon.c:741
Created attachment 923347 [details] File: backtrace
Created attachment 923348 [details] File: cgroup
Created attachment 923349 [details] File: core_backtrace
Created attachment 923350 [details] File: dso_list
Created attachment 923351 [details] File: environ
Created attachment 923352 [details] File: limits
Created attachment 923353 [details] File: maps
Created attachment 923354 [details] File: open_fds
Created attachment 923355 [details] File: proc_pid_status
Created attachment 923356 [details] File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ?
reporter doesn't play with me!
(In reply to Wolfgang Ulbrich from comment #11) > Can you describe a little more detailed what happend? > Did this issue occurs frequently ? Sorry, I missed this e-mail from bugzilla. This happened only once and I don't recall what I was doing when it happened. I'm ok with leaving this as closed, because it hasn't happened again.