Description of problem: When Evolution is left opened for some time, it freezes and killevo has to be used. Version-Release number of selected component (if applicable): evolution-2.21.4-1.fc9.x86_64 gnome-keyring-2.21.4-1.fc9.x86_64 How reproducible: pretty often (when evo is left around lying long enough -- like an hour or so -- it is almost 100% on this computer) Steps to Reproduce: 1.start Evolution 2.do something 3.let it be opened on different desktop 4.return to it after some time Actual results: evolution is just a grey rectangle and no matter what I do it it won't revive itself. Expected results: ready and purring waiting for my orders Additional info:
Created attachment 290990 [details] backtrace
It appears to be stuck in the main thread waiting on gnome-keyring: Thread 1 (Thread 0x2aaaaaaf15a0 (LWP 29617)): #0 0x000000378960d7bb in read () from /lib64/libpthread.so.0 #1 0x000000379c204deb in ?? () from /usr/lib64/libgnome-keyring.so.0 #2 0x000000379c206168 in ?? () from /usr/lib64/libgnome-keyring.so.0 #3 0x000000379c2065d2 in gnome_keyring_find_items_sync () ---Type <return> to continue, or q <return> to quit--- from /usr/lib64/libgnome-keyring.so.0 #4 0x000000379421c600 in ep_get_password (msg=<value optimized out>) at e-passwords.c:702 #5 0x000000379421c212 in ep_idle_dispatch (data=<value optimized out>) at e-passwords.c:237 A backtrace with gnome-keyring-debuginfo installed might be helpful.
Created attachment 290991 [details] new backtrace with gnome-keyring-debuginfo installed Is this better?
Yes, thanks.
This thread may help. It suggests destroying your default keyring and rebooting. Seems like overkill, but other users have reported it works. I would really like to know what caused gnome-keyring to break so badly. http://www.mail-archive.com/evolution-hackers@gnome.org/msg02087.html Setting status to NEEDINFO until you have a chance to try it.
I don’t remember when this happened to me last time (probably couple of weeks already), but I will try to use this (pretty bad) fix when it happens next time. Do we have upstream bug for this (so you can close this as UPSTREAM)? BTW, IMHO, gnome-keyring would need to get some really good dose of code review love. It is worrisome how something which is supposed to be a central piece of security in Gnome is breaking all the time.
Seahorse to the rescue, right? :) I'll hunt for an appropriate upstream gnome-keyring bug for this.
I got lost in these two again -- isn't seahorse just for PGP? And besides, it crashes even more often than gnome-keyring... :-(
You might be right. I was thinking seahorse was poised to eventually supersede gnome-keyring, but I haven't been paying close attention.
This looks close: http://bugzilla.gnome.org/show_bug.cgi?id=502603 A race condition was causing the deadlock and is supposedly fixed upstream now, though I'm not sure if it's found its way into Rawhide yet.