Summary: | Crash in case of delayed acceptance of IMAP Server Certificate error | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Bjarne Juul Pasgaard <kdebjp> |
Component: | IMAP resource | Assignee: | Kevin Ottens <ervin> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | freekdekruijf, heri+kde, joshua, kde, kdepim-bugs, vamp898, vkrause |
Priority: | NOR | ||
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Bjarne Juul Pasgaard
2012-06-24 18:53:09 UTC
Created attachment 72404 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.8) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2
I was able to reproduce this without wanting it ;)
-- Backtrace (Reduced):
#7 0x00007f88d9e94847 in KIMAP::SessionPrivate::handleSslError(KSslErrorUiData const&) () from /usr/lib64/libkimap.so.4
#8 0x00007f88db29081e in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#9 0x00007f88da5faeb4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#10 0x00007f88da5ffb61 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007f88d869b8e8 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
*** Bug 307197 has been marked as a duplicate of this bug. *** Created attachment 74097 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.9) on KDE Platform 4.9.1 using Qt 4.8.3
- What I was doing when the application crashed:
I restarted my IMAP server with a new certiticate and immediately Akonadi/IMAP saw the server certificate change to something unknown and hence asked for confirmation. I quickly skimmed over the certificate details and then pressed accept/always. Right in that moment Akonadi/IMAP crashed.
-- Backtrace (Reduced):
#7 0x00007faf8709b0c7 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=0x7faf870bd177 "sslErrorHandlerResponse", obj=<optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:434
#8 KIMAP::SessionPrivate::handleSslError (this=0x138c600, errorData=...) at /var/tmp/portage/kde-base/kdepimlibs-4.9.1-r1/work/kdepimlibs-4.9.1/kimap/session.cpp:121
#9 0x00007faf884071e6 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007faf877d628c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007faf877da64a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
Created attachment 74436 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.9) on KDE Platform 4.9.2 "release 511" using Qt 4.8.3
This was basically the same situation as the original reporter, but I did not wait for a whole minute.
-- Backtrace (Reduced):
#7 0xb64ee350 in invokeMethod (val9=<optimized out>, val8=<optimized out>, val7=<optimized out>, val6=<optimized out>, val5=<optimized out>, val4=<optimized out>, val3=<optimized out>, val2=<optimized out>, val1=<optimized out>, val0=<optimized out>, member=<optimized out>, obj=<optimized out>) at /usr/include/QtCore/qobjectdefs.h:434
#8 KIMAP::SessionPrivate::handleSslError (this=0x84e7320, errorData=...) at /usr/src/debug/kdepimlibs-4.9.2/kimap/session.cpp:121
#9 0xb65098f2 in qt_static_metacall (_a=0xb2bf08d8, _id=12, _o=0x84e8b40, _c=<optimized out>) at /usr/src/debug/kdepimlibs-4.9.2/build/kimap/session.moc:96
#10 KIMAP::Session::qt_static_metacall (_o=0x84e8b40, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xb2bf08d8) at /usr/src/debug/kdepimlibs-4.9.2/build/kimap/session.moc:78
[...]
#12 0xb730236b in QObject::event (this=0x84e8b40, e=0xb2bcc5c0) at kernel/qobject.cpp:1204
*** Bug 304955 has been marked as a duplicate of this bug. *** *** Bug 309775 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 279113 *** |