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 635667 - [abrt] evolution-2.32.1-1.fc14: mail_tools_folder_to_url: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] evolution-2.32.1-1.fc14: mail_tools_folder_to_url: Process /usr/bin/ev...
Status: RESOLVED DUPLICATE of bug 634072
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2010-11-24 07:47 UTC by E. Kastelijn
Modified: 2010-11-24 10:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Backtrace (48.74 KB, text/plain)
2010-11-24 07:47 UTC, E. Kastelijn 		Details

Description E. Kastelijn 2010-11-24 07:47:27 UTC 
Created attachment 175143 [details]
Backtrace

abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/evolution
comment: This is 100% reproducible
component: evolution
crash_function: mail_tools_folder_to_url
executable: /usr/bin/evolution
kernel: 2.6.34.7-61.fc13.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1290582815
uid: 500

How to reproduce
-----
1. Start Evolution (with configured MAPI account) with correct working ethernet
connection to the Exchange server
2. Use Evolution in the normal way
3. Shutdown laptop
4. Connect the laptop in a network where the Exchange server is unreachable
5. Startup laptop
6. Start Evolution 
7. Press Escape when evolution asks for the password of the MAPI account
8. Crash

See also: https://bugzilla.redhat.com/show_bug.cgi?id=656803
Comment 1 Milan Crha 2010-11-24 10:16:19 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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