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 634072 - [abrt] evolution-2.32.0-2.fc14: mail_tools_folder_to_url: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] evolution-2.32.0-2.fc14: mail_tools_folder_to_url: Process /usr/bin/ev...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 635667 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-11-05 11:20 UTC by Milan Crha
Modified: 2012-09-04 18:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2010-11-05 11:20:56 UTC 
Moving from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=649876

abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: When I open evolution MAPI it will ask for credentials, even with the
correct credentials it will ask again, if you cancel Evolution will crash
component: evolution
crash_function: mail_tools_folder_to_url
executable: /usr/bin/evolution
kernel: 2.6.34.7-56.fc13.x86_64
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288888360
uid: 500

How to reproduce
-----
1.Open Evolution
2.Try to access your current MAPI account
3.Evolution will ask for credentials
4.Cancel the Credentials prompt

Program terminated with signal 11, Segmentation fault.

+ Trace 224504

Thread 1 (Thread 3268)

  • #0 mail_tools_folder_to_url
    at mail-tools.c line 422
  • #1 mail_folder_cache_get_folder_info_flags
    at mail-folder-cache.c line 1320
  • #2 mail_backend_folder_changed_cb
    at e-mail-backend.c line 339
  • #3 e_marshal_VOID__OBJECT_STRING_STRING_INT_STRING_STRING_STRING
    at e-marshal.c line 1874
  • #4 g_closure_invoke
    at gclosure.c line 766
  • #5 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #6 g_signal_emit_valist
    at gsignal.c line 2983
  • #7 g_signal_emit
    at gsignal.c line 3040
  • #8 real_flush_updates
    at mail-folder-cache.c line 184
  • #9 do_async_event
    at mail-mt.c line 621
  • #10 mail_msg_idle_cb
    at mail-mt.c line 442
  • #11 g_main_dispatch
    at gmain.c line 2149
  • #12 g_main_context_dispatch
    at gmain.c line 2702
  • #13 g_main_context_iterate
    at gmain.c line 2780
  • #14 g_main_loop_run
    at gmain.c line 2988
  • #15 IA__gtk_main
    at gtkmain.c line 1237
  • #16 main
    at main.c line 671 






Comment 1


Akhil Laddha





          2010-11-06 04:53:26 UTC
        



bug 604773 and 606850 look related






Comment 2


Milan Crha





          2010-11-24 10:16:19 UTC
        



*** Bug 635667 has been marked as a duplicate of this bug. ***






Comment 3


Milan Crha





          2010-11-24 10:16:44 UTC
        



nice steps in the above bug






Comment 4


Peter Robinson





          2011-05-10 13:40:08 UTC
        



I'm seeing this same crash when I have an expired password with a mapi account. Can provide a complete crash dump if necessary.






Comment 5


Peter Robinson





          2011-05-10 13:41:41 UTC
        



I'm seeing this same crash when I have an expired password with a mapi account. Can provide a complete crash dump if necessary.






Comment 6


Milan Crha





          2012-09-04 18:56:52 UTC
        



Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.