Summary: | akonadi_imap_resource crash | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Paul Gideon Dann <pdgiddie+kde> |
Component: | IMAP resource | Assignee: | Christian Mollekopf <chrigi_1> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | dvratil, kdepim-bugs, l.mierzwa, mbriza, mollekopf, vkrause |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Paul Gideon Dann
2013-05-09 11:55:07 UTC
This bug is also reported for Fedora 18 on https://bugzilla.redhat.com/show_bug.cgi?id=891620 . The bug is appearing quite often, according to https://retrace.fedoraproject.org/faf/reports/43249/ it has hundreds of crash reports. Happens only on x86_64 version of the system. From what I have seen, it's caused by a SSL handshake error (which doesn't have its error code handled in KTcpSocket... as all the errors added with Qt4.3 and later) which then causes the infinite recursion that can be seen in the backtrace. (There are more readable ones in the linked report than from the original reporter here). *** Bug 319783 has been marked as a duplicate of this bug. *** Git commit ddc33b85e27ab18e84a0183dc35bec3dee3dc597 by Dawit Alemayehu. Committed on 08/06/2013 at 14:16. Pushed by adawit into branch 'KDE/4.10'. Added missing error mapping for SslHandshakeFailedError. REVIEW: 110894 M +2 -0 kdecore/network/ktcpsocket.cpp M +2 -1 kdecore/network/ktcpsocket.h http://commits.kde.org/kdelibs/ddc33b85e27ab18e84a0183dc35bec3dee3dc597 I'm afraid this commit doesn't fix my crash. I applied it to kdebase, compiled + installed, logged out and back in (for good measure), but the crashes are still occurring, with the same backtrace. Yes, it doesn't fix that, it needs handling in the KIMAP library, too. This is basically preparation to do that. Note that there is a similar bug 316840 which does not crash, but causes an endless loop of connects and disconnects. I can reproduce it on my machine and it's caused by the same SSL issue. The IMAP resource has a new maintainer, reassigning to him. I'm pretty sure this has been fixed in c3d8ea0 (4.11.3). If not, please reopen. |