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 601252 - evolution assert failure: camel:ERROR:camel-net-utils.c:516:cs_waitinfo: assertion failed: (reply == msg)
evolution assert failure: camel:ERROR:camel-net-utils.c:516:cs_waitinfo: asse...
Status: RESOLVED DUPLICATE of bug 600322
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-11-09 13:15 UTC by Pedro Villavicencio
Modified: 2009-12-22 12:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-11-09 13:15:42 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/475147

"While working with other programs, evolution ended itself and a crash report was issued. The crash was completely spontaneous, no action could be linked with it."

".

Thread 10 (process 7011)

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_949
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 g_static_rec_mutex_lock
    from /lib/libglib-2.0.so.0
  • #4 imap_sync
    at camel-imap-folder.c line 1407
  • #5 camel_folder_sync
    at camel-folder.c line 321
  • #6 refresh_folders_exec
    at mail-send-recv.c line 829
  • #7 mail_msg_proxy
    at mail-mt.c line 522
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #12 ??

Thread 8 (process 7009)

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_949
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 g_static_rec_mutex_lock
    from /lib/libglib-2.0.so.0
  • #4 camel_folder_sync
    at camel-folder.c line 318
  • #5 remove_cache
    at camel-folder-summary.c line 818
  • #6 session_thread_proxy
    at camel-session.c line 592
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 start_thread
    from /lib/libpthread.so.0
  • #10 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #11 ??

Thread 1 (process 7007)

  • #0 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #1 *__GI_abort
    at abort.c line 92
  • #2 g_assertion_message
    from /lib/libglib-2.0.so.0
  • #3 g_assertion_message_expr
    from /lib/libglib-2.0.so.0
  • #4 cs_waitinfo
    at camel-net-utils.c line 516
  • #5 camel_getaddrinfo
    at camel-net-utils.c line 700
  • #6 connect_to_server_wrapper
    at camel-imap-store.c line 975
  • #7 imap_connect
    at camel-imap-store.c line 1412
  • #8 camel_service_connect
    at camel-service.c line 364
  • #9 camel_imap_store_connected
    at camel-imap-store.c line 3009
  • #10 replay_offline_journal
    at camel-imap-folder.c line 249
  • #11 imap_sync
    at camel-imap-folder.c line 1410
  • #12 camel_folder_sync
    at camel-folder.c line 321
  • #13 refresh_folders_exec
    at mail-send-recv.c line 829
  • #14 mail_msg_proxy
    at mail-mt.c line 522
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 start_thread
    from /lib/libpthread.so.0
  • #18 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #19 ??

Comment 1 Milan Crha 2009-11-23 11:53:05 UTC
Downstream bug report about the same:
https://bugzilla.redhat.com/show_bug.cgi?id=540232
Comment 2 Brian J. Murrell 2009-12-05 12:36:05 UTC
I think this is a duplicate of bug 600322.
Comment 3 Milan Crha 2009-12-22 12:38:46 UTC
(In reply to comment #2)
> I think this is a duplicate of bug 600322.

Thanks, yes, I agree, I'm marking it as such.

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