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 677843 - [abrt] Crash in camel_imapx_server_authenticate()
[abrt] Crash in camel_imapx_server_authenticate()
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.4.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imapx]
Depends on:
Blocks:
 
 
Reported: 2012-06-11 09:18 UTC by Milan Crha
Modified: 2013-08-22 17:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2012-06-11 09:18:04 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=830491

libreport version: 2.0.10
abrt_version:   2.0.10
backtrace_rating: 4
cmdline:        evolution
crash_function: camel_imapx_server_authenticate
executable:     /usr/bin/evolution
kernel:         3.4.0-1.fc17.i686
time:           Sun 10 Jun 2012 09:15:47 AM CEST

comment:
:Reproduce:
:Select one e-mail to make Evolution download it.
:Quickly select other e-mails so that multiple e-mails are downloaded.
:=> Crash
:
:I successfully reproduced it (consider large mails with attachments)

:(evolution:18511): camel-WARNING **: Error message was: SSL peer reports incorrect Message Authentication Code.
:(evolution:18511): camel-WARNING **: CamelStreamFs::close() set its GError but then reported success
:(evolution:18511): camel-WARNING **: Error message was: SSL peer reports incorrect Message Authentication Code.
:(evolution:18511): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.

+ Trace 230342

Thread 1 (Thread 0xb2cfdb40 (LWP 5910))

  • #0 camel_imapx_server_authenticate
    at camel-imapx-server.c line 2969
  • #1 imapx_authenticate_sync
    at camel-imapx-store.c line 255
  • #2 camel_service_authenticate_sync
    at camel-service.c line 1324
  • #3 mail_session_authenticate_sync
    at e-mail-session.c line 1411
  • #4 camel_session_authenticate_sync
    at camel-session.c line 1641
  • #5 imapx_reconnect
    at camel-imapx-server.c line 3086
  • #6 camel_imapx_server_connect
    at camel-imapx-server.c line 5561
  • #7 imapx_create_new_connection_unlocked
    at camel-imapx-conn-manager.c line 589
  • #8 camel_imapx_conn_manager_get_connection
    at camel-imapx-conn-manager.c line 660
  • #9 camel_imapx_store_get_server
    at camel-imapx-store.c line 176
  • #10 imapx_get_message_sync
    at camel-imapx-folder.c line 534
  • #11 camel_folder_get_message_sync
    at camel-folder.c line 3573
  • #12 folder_get_message_thread
    at camel-folder.c line 1154
  • #13 run_in_thread
    at gsimpleasyncresult.c line 861
  • #14 io_job_thread
    at gioscheduler.c line 177
  • #15 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #16 g_thread_proxy
    at gthread.c line 801
  • #17 start_thread
    at pthread_create.c line 309
  • #18 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 133 






Comment 1


Milan Crha





          2012-06-12 13:00:50 UTC
        



Hrm, I tried to reproduce this, but with no luck. I see on console the warning about overwritten GError, which is harmless - though annoying, but I do not see the warnings about authentication, which seems to do "the trick". I think the server kicked connection from imapx, it tried to use the kicked connection, thus it received the error about SSL, and then it crashed.






Comment 2


Matthew Barnes





          2013-08-22 17:06:08 UTC
        



Closing as OBSOLETE since the stack trace(s) are too old to be useful at this point.