Bug 307197 - Akonadi IMAP crashed after login
Summary: Akonadi IMAP crashed after login
Status: RESOLVED DUPLICATE of bug 302459
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kevin Ottens
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-22 10:22 UTC by Dennis Schridde
Modified: 2012-09-22 11:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2012-09-22 10:22:05 UTC
Application: akonadi_imap_resource (4.8)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-31-generic i686
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

I logged into KDE, was asked for my KWallet password, later Akonadi asked for confirmation of a SSL certificate, I accepted, when I come back to my computer, Akonadi IMAP has crashed.

-- Backtrace:
Application: Kynes vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb7717980 (LWP 1838))]

Thread 2 (Thread 0xb5663b40 (LWP 2246)):
#0  0x00141416 in __kernel_vsyscall ()
#1  0x05836380 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x023aba7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0239e0ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x0239e201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x009898e7 in QEventDispatcherGlib::processEvents (this=0xb4dfcdd8, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x0095550d in QEventLoop::processEvents (this=0xb5663250, flags=...) at kernel/qeventloop.cpp:149
#7  0x009557a9 in QEventLoop::exec (this=0xb5663250, flags=...) at kernel/qeventloop.cpp:204
#8  0x0083e94c in QThread::exec (this=0x9a72758) at thread/qthread.cpp:501
#9  0x00178269 in KIMAP::SessionThread::run (this=0x9a72758) at ../../kimap/sessionthread.cpp:181
#10 0x00841de0 in QThreadPrivate::start (arg=0x9a72758) at thread/qthread_unix.cpp:298
#11 0x00451d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x05844ace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb7717980 (LWP 1838)):
[KCrash Handler]
#7  0x00000000 in ?? ()
#8  0x00961c01 in QMetaObject::invokeMethod (obj=0x9853d60, member=0x196241 "sslErrorHandlerResponse", type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166
#9  0x00174510 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
#10 KIMAP::SessionPrivate::handleSslError (this=0x9853c20, errorData=...) at ../../kimap/session.cpp:121
#11 0x001770d2 in qt_static_metacall (_a=0xb4d1fd50, _id=12, _o=0x9853bc0, _c=<optimized out>) at ./session.moc:96
#12 KIMAP::Session::qt_static_metacall (_o=0x9853bc0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xb4d1fd50) at ./session.moc:78
#13 0x00968c01 in QMetaCallEvent::placeMetaCall (this=0xb4dfcb18, object=0x9853bc0) at kernel/qobject.cpp:525
#14 0x00971c7b in QObject::event (this=0x9853bc0, e=0xb4dfcb18) at kernel/qobject.cpp:1195
#15 0x00e01ed4 in notify_helper (e=0xb4dfcb18, receiver=0x9853bc0, this=0x96e25b0) at kernel/qapplication.cpp:4559
#16 QApplicationPrivate::notify_helper (this=0x96e25b0, receiver=0x9853bc0, e=0xb4dfcb18) at kernel/qapplication.cpp:4531
#17 0x00e0730d in QApplication::notify (this=0xb4dfcb18, receiver=0x9853bc0, e=0xb4dfcb18) at kernel/qapplication.cpp:4288
#18 0x06a72e01 in KApplication::notify (this=0xbfce3ed0, receiver=0x9853bc0, event=0xb4dfcb18) at ../../kdeui/kernel/kapplication.cpp:311
#19 0x0095697e in QCoreApplication::notifyInternal (this=0xbfce3ed0, receiver=0x9853bc0, event=0xb4dfcb18) at kernel/qcoreapplication.cpp:876
#20 0x0095aad8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x96beaf0) at kernel/qcoreapplication.cpp:1500
#22 0x0095ae0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393
#23 0x00989494 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#24 postEventSourceDispatch (s=0x96da038) at kernel/qeventdispatcher_glib.cpp:279
#25 0x0239dd86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#26 0x0239e125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#27 0x0239e201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0x00989887 in QEventDispatcherGlib::processEvents (this=0x96bf838, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#29 0x00ebaaaa in QGuiEventDispatcherGlib::processEvents (this=0x96bf838, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x0095550d in QEventLoop::processEvents (this=0xbfce3e34, flags=...) at kernel/qeventloop.cpp:149
#31 0x009557a9 in QEventLoop::exec (this=0xbfce3e34, flags=...) at kernel/qeventloop.cpp:204
#32 0x0095aeba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#33 0x00dffa74 in QApplication::exec () at kernel/qapplication.cpp:3820
#34 0x005bf281 in Akonadi::ResourceBase::init (r=0x980eef8) at ../../akonadi/resourcebase.cpp:412
#35 0x0805e3e7 in Akonadi::ResourceBase::init<ImapResource> (argc=3, argv=0xbfce3fa4) at /usr/include/akonadi/resourcebase.h:188
#36 0x080586ab in main (argc=3, argv=0xbfce3fa4) at ../../../resources/imap/imapresource.cpp:607

This bug may be a duplicate of or related to bug 302459.

Possible duplicates by query: bug 302459, bug 296856.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-09-22 11:13:19 UTC

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