| Summary: | akonadi crash on ssl error | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Malcolm Lashley <kde-malc> |
| Component: | IMAP resource | Assignee: | Christian Mollekopf <chrigi_1> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | bosyber, chrigi_1, dvratil, florian.reinhard, forger, g, ggg_mail, heri+kde, johan.erlands, kde-bugreport, kde-bugtracker, kde, kde, kdebjp, kdepim-bugs, konold, krycom83, martin.kampas+kdebugs, martin.ruessler, mollekopf, pa_ubach, pbhj, pederick, tblu, valerymamonov, vkrause, zilti |
| Priority: | NOR | Keywords: | triaged |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| 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 New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Malcolm Lashley
2011-08-02 00:08:55 UTC
Looks like some sort of database corruption issue (in which case the ssl error would just be a trigger, the crash itself is in the collection fetch job). Reassigning to the server component. Created attachment 64733 [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
- Unusual behavior I noticed:
Once for a while a message pops out, stating that "There is currently no session to the IMAP server available" - sometimes it results in a crash and sometimes a SSL certificate dialog is shown.
Closing the dialog with 'remember forever' option doesn't work; the dialog keeps appearing on every subsequent connection attempt.
- Custom settings of the application:
This particular account is using a self-signed certificate.
-- Backtrace (Reduced):
#8 0x00007fa1a3378567 in KIMAP::SessionPrivate::handleSslError(KSslErrorUiData const&) () from /usr/lib/libkimap.so.4
#9 0x00007fa1a337ae72 in KIMAP::Session::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkimap.so.4
#10 0x00007fa1a4753a5e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007fa1a3aed424 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007fa1a3af2291 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
*** Bug 282722 has been marked as a duplicate of this bug. *** *** Bug 283838 has been marked as a duplicate of this bug. *** Created attachment 66341 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
After a SSL-Certificate Error popped up, I decided to go on. When I was asked if I wanted to permanently accept the certificate, it crashed.
-- Backtrace (Reduced):
#7 0x00007fccdfd451d7 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=<optimized out>, obj=<optimized out>) at /usr/include/QtCore/qobjectdefs.h:426
#8 KIMAP::SessionPrivate::handleSslError (this=0x8732c0, errorData=<optimized out>) at /usr/src/debug/kdepimlibs-4.7.2/kimap/session.cpp:121
#9 0x00007fccdfd5e732 in KIMAP::Session::qt_metacall (this=0x8c5150, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fcca000fcf0) at /usr/src/debug/kdepimlibs-4.7.2/build/kimap/session.moc:117
#10 0x00007fcce10d414a in QObject::event (this=0x8c5150, e=<optimized out>) at kernel/qobject.cpp:1226
#11 0x00007fcce048cbe4 in notify_helper (e=0x7fcca00196d0, receiver=0x8c5150, this=0x6afb00) at kernel/qapplication.cpp:4481
Created attachment 66808 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4
- What I was doing when the application crashed:
waiting for kmail to update my "LogistiQ" IMAP mail, I click on accept cetificate forever (does it never take hold?), crash.
- Custom settings of the application:
The certificate is from "banan.cz"; my email is found at imap.logist-iq.eu. But that's a site hosted by banan.cz (including email), without a separate certificate as of yet, and thus akonadi justly asks if it should be trusted, but it seems to fail to
accept to do that permanently.
-- Backtrace (Reduced):
#7 0x00007f966672d567 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=0x1ecb850, errorData=<optimized out>) at ../../kimap/session.cpp:121
#9 0x00007f966672fe72 in KIMAP::Session::qt_metacall (this=0x1f5e670, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7f96480233e0) at ./session.moc:117
#10 0x00007f9667b09a5e in QObject::event (this=0x1f5e670, e=<optimized out>) at kernel/qobject.cpp:1217
#11 0x00007f9666ea3424 in notify_helper (e=0x7f9648023390, receiver=0x1f5e670, this=0x1d84fe0) at kernel/qapplication.cpp:4486
*** Bug 289308 has been marked as a duplicate of this bug. *** from bug 289308 -- Information about the crash: - What I was doing when the application crashed: i was creating a new pop3 account, and identifying ssl type accepted automatically. -- from bug 283838 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. -- from bug 282722 * akonadi pops a message that there's an ssl certificate issue (wrong server address) * no from here you can do: continue, settings, cancel. choose settings * correct the server address * apply the new settings * now hit cancel and not continue * wait for akonadi to die I have had this problem until I got 4.7.3, very strange. Maybe it remembers the certificate (I have used the certificate with older versions without problem). Created attachment 67342 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
Whilst checking for new messages on an IMAP account in kmail an SSL cert error occurred. I elected to trust the cert forever and the crash followed.
-- Backtrace (Reduced):
#7 0x00007f4830be31d7 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=<optimized out>, obj=<optimized out>) at /usr/include/QtCore/qobjectdefs.h:426
#8 KIMAP::SessionPrivate::handleSslError (this=0xae16f0, errorData=<optimized out>) at /usr/src/debug/kdepimlibs-4.7.2/kimap/session.cpp:121
#9 0x00007f4830bfc732 in KIMAP::Session::qt_metacall (this=0x9c4380, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7f4810017370) at /usr/src/debug/kdepimlibs-4.7.2/build/kimap/session.moc:117
#10 0x00007f4831f7214a in QObject::event (this=0x9c4380, e=<optimized out>) at kernel/qobject.cpp:1226
#11 0x00007f483132ac34 in notify_helper (e=0x7f48100171b0, receiver=0x9c4380, this=0x6aa360) at kernel/qapplication.cpp:4481
Created attachment 67651 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4
- What I was doing when the application crashed:
...................................
-- Backtrace (Reduced):
#9 0x006ed9d0 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/qt4/QtCore/qobjectdefs.h:426
#10 KIMAP::SessionPrivate::handleSslError (this=0xb5410be8, errorData=...) at ../../kimap/session.cpp:121
#11 0x006f0496 in KIMAP::Session::qt_metacall (this=0xb5403618, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x9222100) at ./session.moc:117
#12 0x00d09b7d in metacall (argv=0x9222100, idx=15, cl=QMetaObject::InvokeMetaMethod, object=0xb5403618) at kernel/qmetaobject.cpp:237
[...]
#15 0x00d1bb52 in QObject::event (this=0xb5403618, e=0x95a3b38) at kernel/qobject.cpp:1217
*** Bug 292655 has been marked as a duplicate of this bug. *** *** Bug 296856 has been marked as a duplicate of this bug. *** *** Bug 294424 has been marked as a duplicate of this bug. *** *** Bug 296728 has been marked as a duplicate of this bug. *** Created attachment 71727 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.8) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1
- What I was doing when the application crashed:
The same scenario, though I attach my report as the most recent one is from KDE 4.7.x and the bug is still there and unconfirmed.
Akonadi popped up a message box with IMAP connection error - SSL verification has failed. The certificate expired just couple of hours before. Continue->Accept for current session only->Crash.
-- Backtrace (Reduced):
#8 0xb65a839a 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:434
#9 KIMAP::SessionPrivate::handleSslError (this=0x892b020, errorData=...) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2/kimap/session.cpp:121
#10 0xb65ab0a2 in KIMAP::Session::qt_static_metacall (_o=0x8ae6ca0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x6c6f6f62) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2_build/kimap/session.moc:96
[...]
#12 0xb730fef9 in QObject::event (this=0x8b294d8, e=0x8ae6ca0) at kernel/qobject.cpp:1195
#13 0xb686782a in QApplicationPrivate::notify_helper (this=0x88fc9e8, receiver=0x8b294d8, e=0x8932590) at kernel/qapplication.cpp:4554
*** Bug 301881 has been marked as a duplicate of this bug. *** *** Bug 304110 has been marked as a duplicate of this bug. *** *** Bug 309788 has been marked as a duplicate of this bug. *** *** Bug 310243 has been marked as a duplicate of this bug. *** *** Bug 302459 has been marked as a duplicate of this bug. *** *** Bug 311586 has been marked as a duplicate of this bug. *** Created attachment 77971 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.10) on KDE Platform 4.10.1 using Qt 4.8.4
- What I was doing when the application crashed:
I has detached from the network and then it reattached. Shortly after that imap part of Kmail crashed.
-- Backtrace (Reduced):
#7 0x00007fd42e9466a7 in KIMAP::SessionPrivate::handleSslError(KSslErrorUiData const&) () from /usr/lib/libkimap.so.4
#8 0x00007fd42fd015ae in QObject::event (this=0x210c9f0, e=<optimized out>) at kernel/qobject.cpp:1194
#9 0x00007fd42f08d8ec in QApplicationPrivate::notify_helper (this=this@entry=0x1ee9020, receiver=receiver@entry=0x210c9f0, e=e@entry=0x7fd40001f2f0) at kernel/qapplication.cpp:4567
#10 0x00007fd42f09025b in QApplication::notify (this=0x7fff4ae9db10, receiver=0x210c9f0, e=0x7fd40001f2f0) at kernel/qapplication.cpp:4428
#11 0x00007fd42d1feaf6 in KApplication::notify (this=0x7fff4ae9db10, receiver=0x210c9f0, event=0x7fd40001f2f0) at ../../kdeui/kernel/kapplication.cpp:311
*** Bug 317386 has been marked as a duplicate of this bug. *** *** Bug 324442 has been marked as a duplicate of this bug. *** *** Bug 322181 has been marked as a duplicate of this bug. *** The IMAP resource has a new maintainer, reassigning to him. Does this still apply to >=4.11.3? As for me, I can't reproduce the bug in Kmail 4.11.3 Sometimes i faced with expired server certificates, but accepted them with no problems. Don't know about other users, sorry. 2013/11/20 Christian Mollekopf <mollekopf@kolabsys.com> > https://bugs.kde.org/show_bug.cgi?id=279113 > > Christian Mollekopf <mollekopf@kolabsys.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|CONFIRMED |NEEDSINFO > CC| |mollekopf@kolabsys.com > Resolution|--- |WAITINGFORINFO > > --- Comment #28 from Christian Mollekopf <mollekopf@kolabsys.com> --- > Does this still apply to >=4.11.3? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > I cannot reproduce it either in kmail 4.11.3 Valery Mamonov <valerymamonov@gmail.com> ha scritto: >https://bugs.kde.org/show_bug.cgi?id=279113 > >--- Comment #29 from Valery Mamonov <valerymamonov@gmail.com> --- >As for me, I can't reproduce the bug in Kmail 4.11.3 >Sometimes i faced with expired server certificates, but accepted them >with >no problems. >Don't know about other users, sorry. > > >2013/11/20 Christian Mollekopf <mollekopf@kolabsys.com> > >> https://bugs.kde.org/show_bug.cgi?id=279113 >> >> Christian Mollekopf <mollekopf@kolabsys.com> changed: >> >> What |Removed |Added >> >> >---------------------------------------------------------------------------- >> Status|CONFIRMED |NEEDSINFO >> CC| >|mollekopf@kolabsys.com >> Resolution|--- |WAITINGFORINFO >> >> --- Comment #28 from Christian Mollekopf <mollekopf@kolabsys.com> --- >> Does this still apply to >=4.11.3? >> >> -- >> You are receiving this mail because: >> You are on the CC list for the bug. >> > >-- >You are receiving this mail because: >You are on the CC list for the bug. -- Inviato dal mio cellulare Android con K-9 Mail. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |