Bug 283838

Summary:	Akonadi Crash after Certificate Failure
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Joachim <kde-bugtracker>
Component:	IMAP resource	Assignee:	Kevin Ottens <ervin>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	johan.erlands, kdepim-bugs, vkrause
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Joachim 2011-10-12 06:42:23 UTC

Application: akonadi_imap_resource (4.7)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.4
Operating System: Linux 3.0-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was fetching mails with kmail2 from an imap account with a self-signed certificate. Akonadi informed me that this certificate is not valid while I was away. And when I was back I choose accept permanently and got the crash.
I would assume due to the delay between asking about the certificate and accepting it, some session timed out or something. Though I have no clue of the architecture of akonadi.

- Unusual behavior I noticed:
Akonadi asks me about this certificate every time I start my pc. For every account. Always. no matter how often I choose Accept Permanently.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Akonadi Resource (akonadi_imap_resource), signal: Bus error
[KCrash Handler]
#6  0x00007f392b457c08 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /usr/lib/libQtCore.so.4
#7  0x00007f392a0fb147 in KIMAP::SessionPrivate::handleSslError(KSslErrorUiData const&) () from /usr/lib/libkimap.so.4
#8  0x00007f392a0fda52 in KIMAP::Session::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkimap.so.4
#9  0x00007f392b46518e in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#10 0x00007f392a824ae4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#11 0x00007f392a829951 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#12 0x00007f3928968c96 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#13 0x00007f392b44e89c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#14 0x00007f392b451c2f in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#15 0x00007f392b4791a3 in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007f392662d29d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007f392662da78 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007f392662dd09 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0x00007f392b479606 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#20 0x00007f392a8c7eee in ?? () from /usr/lib/libQtGui.so.4
#21 0x00007f392b44da92 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0x00007f392b44dc97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0x00007f392b451eab in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#24 0x00007f392bb43a56 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4
#25 0x000000000041aad6 in int Akonadi::ResourceBase::init<ImapResource>(int, char**) ()
#26 0x00007f39279db13d in __libc_start_main () from /lib/libc.so.6
#27 0x00000000004155c5 in _start ()

This bug may be a duplicate of or related to bug 282722, bug 279113.

Possible duplicates by query: bug 282722, bug 279113.

Reported using DrKonqi

Comment 1 Johan Erlands 2011-11-15 08:28:53 UTC

Created attachment 65691 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:
Checking mail. The exchange server that I am connected to uses a self signed certificate.
Got a questions about the certificate. 

- Unusual behavior
The question about the certificate always comes back.  In the previous version (from kubuntu) i got one per time I started the program. In this version it always asks. It is more likely to crash if it has sent up more than one question.

-- Backtrace (Reduced):
#7  0x00007fe100978567 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=<optimized out>, obj=<optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:426
#8  KIMAP::SessionPrivate::handleSslError (this=0x17fc0c0, errorData=<optimized out>) at ../../kimap/session.cpp:121
#9  0x00007fe10097ae72 in KIMAP::Session::qt_metacall (this=0x166daf0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fe0e4002ec0) at ./session.moc:117
#10 0x00007fe101d53a5e in QObject::event (this=0x166daf0, e=<optimized out>) at kernel/qobject.cpp:1217
#11 0x00007fe1010ed424 in notify_helper (e=0x7fe0e4002d80, receiver=0x166daf0, this=0x14826d0) at kernel/qapplication.cpp:4486

Comment 2 Christophe Marin 2011-11-18 00:06:46 UTC


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