Evolution Client crashes with segmentation fault during startup

This document (7018854) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Desktop 12 Service Pack 1 (SLED 12 SP1)
SUSE Linux Enterprise Desktop 12 Service Pack 2 (SLED 12 SP2)


When Evolution Client is started, it crashes with a segmentation fault.
The coredump file read by gdb shows that the Evolution process is crashing with the following backtrace:

Thread 1 (Thread 0x7f16900d3a40 (LWP 2010)):
#0  0x0000000000000000 in ?? ()
#1  0x00007f1687d1e9db in ?? () from /usr/lib64/libsqlite3.so.0
#2  0x00007f1687d3496f in ?? () from /usr/lib64/libsqlite3.so.0
#3  0x00007f1687d34c1c in ?? () from /usr/lib64/libsqlite3.so.0
#4  0x00007f1687d7ee89 in ?? () from /usr/lib64/libsqlite3.so.0
#5  0x00007f1687d8159f in sqlite3_step () from /usr/lib64/libsqlite3.so.0
#6  0x00007f1687d8239a in sqlite3_exec () from /usr/lib64/libsqlite3.so.0
#7  0x00007f168eeae96a in ?? () from /usr/lib64/libcamel-1.2.so.45
#8  0x00007f168eeb040f in camel_db_select () from /usr/lib64/libcamel-1.2.so.45
#9  0x00007f168eeb0569 in camel_db_get_folder_uids ()
   from /usr/lib64/libcamel-1.2.so.45
#10 0x00007f168eec6280 in camel_folder_summary_load_from_db ()
   from /usr/lib64/libcamel-1.2.so.45
#11 0x00007f167814bab8 in ?? ()
   from /usr/lib64/evolution-data-server/camel-providers/libcamellocal.so
#12 0x00007f167813fa69 in camel_local_summary_load ()
   from /usr/lib64/evolution-data-server/camel-providers/libcamellocal.so
#13 0x00007f167813d66c in camel_local_folder_construct ()
   from /usr/lib64/evolution-data-server/camel-providers/libcamellocal.so
#14 0x00007f1678148ce6 in camel_maildir_folder_new ()
   from /usr/lib64/evolution-data-server/camel-providers/libcamellocal.so

This issue started to occur after a huge number of emails have been downloaded.


This segmentation fault bug is fixed in SLED12 SP1/SP2 sqlite3 version


This issue is caused by a bug inside sqlite3 packages.

Additional Information

SLED12 SP1/SP2 sqlite3 version Release Notes:

- Avoid calling sqlite3OsFetch() on a file-handle for which the xFetch method is NULL.
  This prevents a potential segmentation fault. (bsc#1025034)


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7018854
  • Creation Date: 02-May-2017
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Desktop

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center