Description of problem: evolution-alarm-notify ate 100% cpu, I killed its for creating this report. Here is a strace log: [pid 1502] poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=11, events=POLLIN}], 5, 0) = 0 (Timeout) [pid 1502] recvfrom(3, 0x25792f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) [pid 1502] poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=11, events=POLLIN}], 5, 0) = 0 (Timeout) [pid 1502] recvfrom(3, 0x25792f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) [pid 1502] poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=11, events=POLLIN}], 5, 0) = 0 (Timeout) [pid 1502] recvfrom(3, 0x25792f4, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) [pid 1502] poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=11, events=POLLIN}], 5, 0) = 0 (Timeout) I see this bug very often. Probably it's reproduced after suspend/resume. Version-Release number of selected component: evolution-3.4.4-1.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: /usr/libexec/evolution/3.4/evolution-alarm-notify crash_function: __libc_recv kernel: 3.5.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 __libc_recv at ../sysdeps/unix/sysv/linux/x86_64/recv.c : #1 recv at /usr/include/bits/socket2.h : #2 _xcb_in_read at xcb_in.c : #3 poll_for_next_event at xcb_in.c : #4 xcb_poll_for_event at xcb_in.c : #5 poll_for_event at xcb_io.c : #6 poll_for_response at xcb_io.c : #7 _XEventsQueued at xcb_io.c : #8 XPending at Pending.c : #9 gdk_check_xpending at gdkeventsource.c
Created attachment 615788 [details] File: core_backtrace
Created attachment 615789 [details] File: environ
Created attachment 615790 [details] File: limits
Created attachment 615791 [details] File: backtrace
Created attachment 615792 [details] File: cgroup
Created attachment 615793 [details] File: maps
Created attachment 615794 [details] File: dso_list
Created attachment 615795 [details] File: var_log_messages
Created attachment 615796 [details] File: open_fds
Thanks for a bug report. I see it's caused by a password prompt, it has some trouble showing the password prompt dialog. The evolution 3.6.x has done password prompts differently, with many other things around password asking being improved, thus I'm closing this in favour of the 3.6.x.