Created attachment 584219 [details]
backtrace for evolution

Created attachment 584220 [details]
backtrace for evolution-alarm-notify

Thanks for a bug report. Both processes are trying to authenticate to your EWS server, with no luck. I created an evolution-ews-3.4.2 update for Fedora 17 few minutes ago, which contains fix which may help here. Could you try to update to that version (when it'll be available in updates-testing) and report back whether it helps, please?

I guess, if it'll work, then you'll be asked to enter your password, because the calendar seems to be unable to connect to your server with previously saved password.

Could this cause killing process gnome-system-monitor?

Last time, often after long periods of inactivity, when I come to work, I find my computer hanging. When I look htop I see that gnome-system-monitor eating the whole processor. Today, after his killing, I noticed that the evolution has started to consume the entire CPU and wrote this bug report.

Here more details about problem with gnome-system-monitor: https://bugzilla.redhat.com/show_bug.cgi?id=811902

(In reply to comment #4)
> Could this cause killing process gnome-system-monitor?

I think it's a coincidence, though it's just a guess.

Created attachment 585992 [details]
backtrace for evolution-alarm-notify

Created attachment 585993 [details]
backtrace for evolution-addressbook-factory

Today it occured again

Created attachment 586013 [details]
backtrace evolution-addressbook-factory

Created attachment 586024 [details]
backtrace evolution-addressbook-factory from another machine

Comment #6: It seems to be either stuck or witing in the password prompt:
Thread 1 (Thread 0xb77c58c0 (LWP 1302)):
#0  0x4fb9a552 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0
#1  0x42cf9271 in g_mutex_unlock () from /lib/libglib-2.0.so.0
#2  0x42cb7a95 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#3  0x42cb820f in ?? () from /lib/libglib-2.0.so.0
#4  0x42cb8472 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x416231c4 in ep_msg_send (msg=msg@entry=0x9b09090) at e-passwords.c:386

comment #7, comment #9, comment #10: it's just like yours bug #821228

Strange is that it seems like the ews book backend already got the passwords, it looks like it is waiting for a response from the server.

Created attachment 586615 [details]
htop

Created attachment 586616 [details]
backtrace for evolution-addressbook-factory

Thanks for the update. I see this is different from comment #6, but it's the same issue, multiple threads in ews addressbook authentication, but the same for comment #7 and those others.

Let's move this under bug #821228.

*** This bug has been marked as a duplicate of bug 821228 ***