akonadi_imap_resource crashed with SIGSEGV in ERR_get_state()

[Scott Kitterman]

Same crash, maybe it gets a better trace.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: kdepim-runtime 4:4.10.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
CrashCounter: 1
Date: Mon May 13 05:04:23 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/akonadi_imap_resource
InstallationDate: Installed on 2011-04-04 (774 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
MarkForUpload: True
ProcCmdline: /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_1
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0xb22f696d <ERR_get_state+13>: call 0xb2277240
 PC (0xb22f696d) ok
 source "0xb2277240" (0xb2277240) ok
 destination "(%esp)" (0xafa78ff0) in non-writable VMA region: 0xafa78000-0xafa79000 ---p [stack:4309]
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA [stack:4309]
Signal: 11
SourcePackage: kdepim-runtime
StacktraceTop:
 ERR_get_state () from /lib/i386-linux-gnu/libcrypto.so.1.0.0
 ERR_put_error () from /lib/i386-linux-gnu/libcrypto.so.1.0.0
 ?? () from /lib/i386-linux-gnu/libssl.so.1.0.0
 ?? () from /lib/i386-linux-gnu/libssl.so.1.0.0
 ?? () from /lib/i386-linux-gnu/libssl.so.1.0.0
Title: akonadi_imap_resource crashed with SIGSEGV in ERR_get_state()
UpgradeStatus: Upgraded to raring on 2013-04-24 (24 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare syslog wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1176464, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.