GNOME Bugzilla – Bug 532771
gnome_keyring_find_items_sync() does not return
Last modified: 2010-04-01 12:16:01 UTC
Steps to reproduce: 1. Start evolution 2. Pick a mail and reply to it, or create a new one 3. Wait a few seconds, evolution will always freeze Stack trace: (gdb) thread apply all bt full
+ Trace 197540
Thread 4 (Thread 0xb61a5b90 (LWP 9098))
Other information: Evolution freezes but doesn't hog the CPU. This happens with all 2.22 versions of evolution but not with any of the 2.12 versions. This also doesn't seem to happen with evolution 2.23.1, but I'm not sure as a lot of the exchange stuff is broken for me in that new version (contacts, tasks and calendar), so the error may simply not be triggered. Note that I have removed the .evolution and .gconf/apps/evolution directories before installing evolution 2.22, to make sure this wasn't the issue.
Gentoo should apply the gnome-keyring patch in bug #502603 comment #27. *** This bug has been marked as a duplicate of 502603 ***
(In reply to comment #1) > Gentoo should apply the gnome-keyring patch in bug #502603 comment #27. > > *** This bug has been marked as a duplicate of 502603 *** Thanks for your help. Gentoo has gnome-keyring 2.22.1 which has this fix, and I'm using it. Denis.
*** This bug has been marked as a duplicate of 502603 ***
Sorry, but mistake did it
(In reply to comment #0) > Other information: > This also doesn't seem to > happen with evolution 2.23.1, but I'm not sure as a lot of the exchange stuff > is broken for me in that new version (contacts, tasks and calendar), so the > error may simply not be triggered. I have just installed evolution-data-server-2.23.2, evolution-2.23.2 and evolution-exchange-2.23.2 which work much better with the OWA server I use. Unfortunately, this allows me to confirm that the issue I'm experimenting in 2.22 is still present in 2.23. That's with gnome-keyring-2.22.2 in case that matters. I don't really know how evolution works, but it could be an issue with GAL. The sysadmin at work has never been able to tell me the address of his GAL server. So I tried a few things but I could never make it work. It never bothered me though, because in evolution-2.12 and earlier I would simply click cancel whenever evolution would ask me for my GAL password. What I have noticed is that evolution-2.22 doesn't bother me with a GAL password all the time, which always happened when composing a new mail in evolution 2.12 and is the moment when evolution-2.22 freezes. Could evolution-2.22 be failing silently when connecting to the GAL server ? I'm saying this because there are references to GAL in my stack trace above. Is there anything I can do to help ? Denis.
I have the same problem. Just click New... button, Evolution will open a new message window and freeze. My system is: recently installed Ubuntu 8.10 Evolution 2.22.2 I never experienced this bug on older versions of Evolution.
I have the same problem and it appears that Denis is correct - it is the GAL server not prompting for a password any more. I confirmed this by giving it a "GAL server" (a valid ldap server name* which happens to be the same machine that Exchange runs on - my sysadmin has no clue what a GAL server is and neither do I). Now I can compose and reply to emails. When this field is empty, it locks up but does not hog CPU. This started happening when I upgraded to Fedora 9. The really annoying thing about this problem is that I like to use Evolution as my Web-based email client, and how will it see the GAL server without the nuisance logging in with a VPN? * Ideally, the use of the GAL server should be optional because I have never been able to make it work and I have tried hard in every version of Fedora from FC1. $ rpm -qa|egrep "evolution|keyring" |sort evolution-2.22.2-2.fc9.x86_64 evolution-data-server-2.22.2-1.fc9.i386 evolution-data-server-2.22.2-1.fc9.x86_64 evolution-exchange-2.22.2-1.fc9.x86_64 evolution-help-2.22.2-2.fc9.x86_64 evolution-webcal-2.21.92-1.fc9.x86_64 gnome-keyring-2.22.1-1.fc9.i386 gnome-keyring-2.22.1-1.fc9.x86_64 gnome-keyring-devel-2.22.1-1.fc9.x86_64 gnome-keyring-manager-2.20.0-2.fc9.x86_64 gnome-keyring-pam-2.22.1-1.fc9.x86_64 gnome-python2-gnomekeyring-2.22.0-2.fc9.x86_64
More info ... This appears to be an x86_64 issue. It works great on my 386 laptop over the Web, I can compose and reply to email without a lockup and I am no longer nagged by the GAL password dialogue window (a big bonus!). I still see repeated messages in /var/log/messages as is observed by another person having the same problem on an x86_64 machine: http://linux.derkeiler.com/Mailing-Lists/Fedora/2008-06/msg00389.html Below is my 386 info. Note that is is slightly behind my x86_64 because I upgraded from the Fedora unreleased testing repos in an effort to debug this issue. $ rpm -qa|egrep "evolution|keyring" | sort evolution-2.22.2-2.fc9.i386 evolution-data-server-2.22.1-2.fc9.i386 evolution-data-server-devel-2.22.1-2.fc9.i386 evolution-data-server-doc-2.22.1-2.fc9.i386 evolution-exchange-2.22.1-1.fc9.i386 evolution-webcal-2.21.92-1.fc9.i386 gnome-keyring-2.22.1-1.fc9.i386 gnome-keyring-devel-2.22.1-1.fc9.i386 gnome-keyring-manager-2.20.0-2.fc9.i386 gnome-keyring-pam-2.22.1-1.fc9.i386 mail-notification-evolution-plugin-5.4-1.fc9.i386 pam_keyring-0.0.9-2.fc9.i386 syncevolution-0.7-3.fc9.i386
(In reply to comment #8) > This appears to be an x86_64 issue. The bug I reported was on x86, not x86_64. So I don't think it's an x86_64 issue. Denis.
Some more info ... Yes, it is indeed a problem in x86 too. Although I can compose and reply to email on my x86 laptop, instead of locking up, it endlessly writes the following message to /var/log/messages: Jun 15 09:11:55 localhost gnome-keyring-daemon[2607]: couldn't read 4 bytes from client: Also, the CPU is busy with about 50% for user and 50% for system activity. If I kill the evolution, the CPU utilization goes back to normal.
Update ... I updated x36 Fedora 9 laptop using yum and evolution is now at 2.22.2. The CPU issues have gone away, I can send/reply to email without a lockup, but it still continuously writes the message above in /var/log/messages. To stop this, I have to stop/start the evolution client after sending email or eventually my disk will fill up. The nice thing is that evolution isn't nagging me about the GAL field in the preferences being empty so it is functioning OK as a Web email client. evolution-2.22.2-2.fc9.i386 evolution-data-server-2.22.2-1.fc9.i386 evolution-data-server-devel-2.22.2-1.fc9.i386 evolution-data-server-doc-2.22.2-1.fc9.i386 evolution-devel-2.22.2-2.fc9.i386 evolution-exchange-2.22.2-1.fc9.i386 evolution-help-2.22.2-2.fc9.i386 evolution-python-0.0.4-3.fc9.i386 evolution-webcal-2.21.92-1.fc9.i386
*** Bug 540112 has been marked as a duplicate of this bug. ***
I'm still trying to nail this when I get bored, and compiling evolution-data-server with --disable-gnome-keyring seems to solve the issue. I will try and confirm that when I have more time. Denis.
OK. I am getting hit by this every so often (sometimes during the day, almost always during the night -- system up & running, and evo hangs). AMD64, Evo compiled from trunk (last hang, as of this morning, with trunk up-to-date as of 2008-07-13 14:00 Z. This is a backtrace from the offending thread:
+ Trace 202787
*** Bug 543084 has been marked as a duplicate of this bug. ***
(In reply to comment #13) > I'm still trying to nail this when I get bored, and compiling > evolution-data-server with --disable-gnome-keyring seems to solve the issue. I > will try and confirm that when I have more time. Well, that will cause E-D-S to fall back to the older password file approach (~/.gnome2_private/Evolution), which we're trying to migrate _away_ from. This still sounds like a gnome-keyring issue to me, but I'll have yet another look at our password storage logic and see if anything pops out at me that I missed before. I personally am not seeing this hang at all anymore using Fedora 9 on an i386.
Follow-up ... I have my x386 IBM T42 laptop and x86_64 AMD Desktop fully up-to-date and both are working great! I have not had any freezes nor is there continuous writing to /var/messages until I bounce Evolution, although it will infrequently write the same "couldn't read 4 bytes ..." message when I send mail, but this is not a problem. I've been traveling on business with my laptop and have been connecting to clients hardwired networks as well as various hotel wireless connections and I'm very pleased with Evolution as a Web-based email client. Thanks! $ rpm -qa | egrep 'evolution|keyring' | sort evolution-2.22.3.1-1.fc9.i386 evolution-data-server-2.22.3-2.fc9.i386 evolution-data-server-devel-2.22.3-2.fc9.i386 evolution-data-server-doc-2.22.3-2.fc9.i386 evolution-devel-2.22.3.1-1.fc9.i386 evolution-exchange-2.22.3-1.fc9.i386 evolution-help-2.22.3.1-1.fc9.i386 evolution-python-0.0.4-3.fc9.i386 evolution-webcal-2.21.92-1.fc9.i386 gnome-keyring-2.22.3-1.fc9.i386 gnome-keyring-devel-2.22.3-1.fc9.i386 gnome-keyring-manager-2.20.0-2.fc9.i386 gnome-keyring-pam-2.22.3-1.fc9.i386 mail-notification-evolution-plugin-5.4-1.fc9.i386 pam_keyring-0.0.9-2.fc9.i386 $ rpm -qa |egrep "evolution|keyring" | sort evolution-2.22.3.1-1.fc9.x86_64 evolution-data-server-2.22.3-2.fc9.i386 evolution-data-server-2.22.3-2.fc9.x86_64 evolution-exchange-2.22.3-1.fc9.x86_64 evolution-help-2.22.3.1-1.fc9.x86_64 evolution-webcal-2.21.92-1.fc9.x86_64 gnome-keyring-2.22.3-1.fc9.i386 gnome-keyring-2.22.3-1.fc9.x86_64 gnome-keyring-devel-2.22.3-1.fc9.x86_64 gnome-keyring-manager-2.20.0-2.fc9.x86_64 gnome-keyring-pam-2.22.3-1.fc9.x86_64 gnome-python2-gnomekeyring-2.22.0-4.fc9.x86_64
(In reply to comment #16) > Well, that will cause E-D-S to fall back to the older password file approach > (~/.gnome2_private/Evolution), which we're trying to migrate _away_ from. I forgot to give some feedback on this, sorry. So, email works for me when not using gnome-keyring, but I then lose the exchange calendar and contacts. I had no time to try and debug this. Since then I have uninstalled evolution and I'm using OWA again, because frankly evolution isn't working for my everyday job. I will retry it when I have more time. Denis.
*** Bug 539210 has been marked as a duplicate of this bug. ***
This is same as bug 544998. But after discussion with hggdh in IRC, we want to keep this open until resolution from g-kr as a safety net.
I just tried Ubuntu intrepid alpha 6 and whatever it was it's now fixed. So you may close this now. Thanks for your effort. Denis.
*** Bug 537359 has been marked as a duplicate of this bug. ***
*** Bug 568474 has been marked as a duplicate of this bug. ***
Matt, patch attached in bug 544998 should solve this.
For what it worth -- I ran with this patch for a while and, when gonme-keyring 2.25 was put available, I cut back to upstream (and am now running g-kr 2.25.4.1). I have not had this issue anymore. I remember I had a look at the g-kr source when I moved back to pristine upstream, and found the patch did not fully apply (there were some rejects). bug 544998 has not had any input from development since I commented back on my results with the patch, so I do not know if it was integrated/modified into 2.25. But I know I do not experience the issue anymore.
bug 590303 could be a dupe which is filed against 2.26.x
I am closing the bug as per comment#25.