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 605518 - evolution hang randomly
evolution hang randomly
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Tasks
2.32.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 605590 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-12-27 01:14 UTC by Ruchir Brahmbhatt
Modified: 2011-09-30 06:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ruchir Brahmbhatt 2009-12-27 01:14:10 UTC
OS: opensuse 11.2
Evolution: 2.29.4

Reproducible: Once

Steps:
1. While doing normal operations, click new assigned task.

Backtrace:

Thread 2 (Thread 0x7f023467d910 (LWP 6285))

  • #0 __pthread_mutex_unlock_usercnt
    from /lib64/libpthread.so.0
  • #1 dbus_pending_call_get_completed
    from /lib64/libdbus-1.so.3
  • #2 ??
    from /lib64/libdbus-1.so.3
  • #3 gnome_keyring_item_info_free
    from /usr/lib64/libgnome-keyring.so.0
  • #4 gnome_keyring_is_available
    from /usr/lib64/libgnome-keyring.so.0
  • #5 e_passwords_init
    at e-passwords.c line 1273
  • #6 ep_msg_new
    at e-passwords.c line 480
  • #7 e_passwords_get_password
    at e-passwords.c line 1435
  • #8 get_password
    at mail-session.c line 201
  • #9 smtp_connect
    at camel-smtp-transport.c line 545
  • #10 camel_service_connect
    at camel-service.c line 364
  • #11 camel_session_get_service_connected
    at camel-session.c line 280
  • #12 mail_send_message
    at mail-ops.c line 556
  • #13 send_queue_exec
    at mail-ops.c line 781
  • #14 mail_msg_proxy
    at mail-mt.c line 466
  • #15 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #16 g_thread_create_proxy
    at gthread.c line 635
  • #17 start_thread
    from /lib64/libpthread.so.0
  • #18 clone
    from /lib64/libc.so.6
  • #19 ??

Thread 1 (Thread 0x7f024835e7f0 (LWP 6103))

  • #0 __lll_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_lock_941
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 e_passwords_init
    at e-passwords.c line 1257
  • #4 ep_msg_new
    at e-passwords.c line 480
  • #5 e_passwords_get_password
    at e-passwords.c line 1435
  • #6 addressbook_authenticate
    at e-book-auth-util.c line 165
  • #7 open_reply
    at e-book.c line 1650
  • #8 org_gnome_evolution_dataserver_addressbook_Book_open_async_callback
    at e-data-book-bindings.h line 43
  • #9 ??
    from /lib64/libdbus-1.so.3
  • #10 dbus_connection_dispatch
    from /lib64/libdbus-1.so.3
  • #11 ??
    from /usr/lib64/libdbus-glib-1.so.2
  • #12 g_main_dispatch
    at gmain.c line 1960
  • #13 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #14 g_main_context_iterate
    at gmain.c line 2591
  • #15 IA__g_main_loop_run
    at gmain.c line 2799
  • #16 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 main
    at main.c line 593

Comment 1 Ruchir Brahmbhatt 2009-12-28 09:33:50 UTC
*** Bug 605590 has been marked as a duplicate of this bug. ***
Comment 2 Ruchir Brahmbhatt 2009-12-28 09:55:00 UTC
This happens randomly. Once it happened while clicking reply all  as specified in #605590 and once it happened while clicking forward. It generates same backtrace every time.
Comment 3 Akhil Laddha 2010-03-12 03:57:20 UTC
bug 605654 and bug 606106 look duplicate of this bug
Comment 4 Akhil Laddha 2011-04-08 05:51:52 UTC
Can you please check again whether this issue still happens in Evolution 2.32.2 or 3.0 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.
Comment 5 Ruchir Brahmbhatt 2011-04-08 06:20:10 UTC
Sometimes its reproduced on 2.32.1. I don't have 2.32.2 or 3.0 from suse repos yet. I'll update this bug when I get newer packages.
Comment 6 Akhil Laddha 2011-09-30 06:00:50 UTC
is this bug still valid in Evolution 3.0.3 or 3.2 ?
Comment 7 Ruchir Brahmbhatt 2011-09-30 06:10:19 UTC
Haven't experienced since 3.0 so closing for now.