After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 616146 - after fetching mail a few times evolution hangs
after fetching mail a few times evolution hangs
Status: RESOLVED DUPLICATE of bug 621063
Product: libgnome-keyring
Classification: Core
Component: General
2.30.x
Other Linux
: Normal major
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
evolution[pop] evolution[passwords]
Depends on:
Blocks:
 
 
Reported: 2010-04-19 02:52 UTC by Paonia
Modified: 2019-02-22 11:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paonia 2010-04-19 02:52:46 UTC
When I start evolution it fetches mail and then is able to a while long but after 10-20 minutes it hangs with fetching for all the accounts and just sits there. I have killed ev and restarted and gotten the same behavior.

Here are some error messages I get:
(evolution:8053): camel-local-provider-CRITICAL **: mbox_cmp_uids: assertion `a != NULL' failed

(evolution:8053): camel-local-provider-WARNING **: Didn't get the next message where I expected (49588) got 59901 instead

Happy to provide any information you need.
thanks
Comment 1 Akhil Laddha 2010-04-19 04:12:44 UTC
Which server type do you use IMAP / POP / Exchange ? 

When evolution hangs, could you please check whether evolution-data-server process is running or not, you can use command 'ps -ef | grep evolution-data-server' on terminal.

It will be helpful if you can provide gdb traces of evolution process when it hangs. Start evolution under gdb from terminal, when it hangs, do 'ctrl+c' then 'thread apply all bt' and paste the traces here.

see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details
about how to do this
Comment 2 Paonia 2010-04-19 06:22:14 UTC
pop
data server is still running
^C
Program received signal SIGINT, Interrupt.
0xffffe424 in __kernel_vsyscall ()
(gdb) thread apply all bt


Comment 3 Akhil Laddha 2010-04-19 06:35:19 UTC
Thanks.
Comment 4 Akhil Laddha 2010-06-21 10:11:04 UTC
could be similar to bug 616512
Comment 5 Sebastien Bacher 2010-06-21 16:25:20 UTC
reassigning to gnome-keyring, from IRC discussion "gnome_keyring_is_available()
is calling gkr_operation_unref() -followed by- gkr_operation_block()"

"gnome_keyring_is_available (void)
...
    gkr_operation_unref (op);
    return gkr_operation_block (op) == GNOME_KEYRING_RESULT_OK;
..."
Comment 6 Stef Walter 2010-06-21 17:26:48 UTC
Nope, this is almost certainly the same flaw in evolution's keyring access that comes up constantly. Please see duplicate bug #621063.

If you can provide a stack trace that shows this isn't the same issue, then please reopen.

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