Bug 322181 - Crash of imap resource after resume from sleep
Summary: Crash of imap resource after resume from sleep
Status: RESOLVED DUPLICATE of bug 279113
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.10
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Kevin Ottens
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-07-10 07:40 UTC by Christian Mollekopf
Modified: 2013-09-03 08:11 UTC (History)
3 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 Christian Mollekopf 2013-07-10 07:40:51 UTC
Application: akonadi_imap_resource (4.10)
KDE Platform Version: 4.10.4 (Compiled from sources)
Qt Version: 4.8.4
Operating System: Linux 3.9.5-201.fc18.x86_64 x86_64
Distribution: "Fedora release 18 (Spherical Cow)"

-- Information about the crash:
- What I was doing when the application crashed:
Resumed from sleep.

This is the 4.10 branch compiled from sources.

-- Backtrace:
Application: VM of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7ff5d0418880 (LWP 8248))]

Thread 2 (Thread 0x7ff5bf433700 (LWP 8805)):
#0  0x0000003a51ee99ad in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000003a54a47d24 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
#2  0x0000003a54a47e44 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x0000003a5b3a5fa6 in QEventDispatcherGlib::processEvents (this=0x7ff5b8003ce0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x0000003a5b3765ef in QEventLoop::processEvents (this=this@entry=0x7ff5bf432d00, flags=...) at kernel/qeventloop.cpp:149
#5  0x0000003a5b376878 in QEventLoop::exec (this=0x7ff5bf432d00, flags=...) at kernel/qeventloop.cpp:204
#6  0x0000003a5b278980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#7  0x0000003a5b27b95c in QThreadPrivate::start (arg=0x1198f10) at thread/qthread_unix.cpp:338
#8  0x0000003a52207d15 in start_thread (arg=0x7ff5bf433700) at pthread_create.c:308
#9  0x0000003a51ef248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7ff5d0418880 (LWP 8248)):
[KCrash Handler]
#6  QMetaObject::invokeMethod (obj=0x20006900640061, member=<optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166
#7  0x00007ff5d14c4265 in KIMAP::Session::stateChanged (this=0x7ff5d14e1719, _t1=32767, _t2=4150832084) at /home/chrigi/devel/kde/build/kolab410/kdepimlibs/kimap/moc_session.cpp:161
#8  0x00007ff5d14c85e8 in KIMAP::SessionThread::encryptionNegotiationResult (this=0x0, _t1=false, _t2=0) at /home/chrigi/devel/kde/build/kolab410/kdepimlibs/kimap/moc_sessionthread_p.cpp:139
#9  0x00007ff5d14c1c4d in KIMAP::SessionPrivate::handleSslError (this=0x7ff5d14c85e8 <KIMAP::SessionThread::encryptionNegotiationResult(bool, KTcpSocket::SslVersion)+36>, errorData=...) at /home/chrigi/devel/kde/kdepimlibs/kimap/session.cpp:118
#10 0x00007ff5d14c3f14 in KIMAP::Session::qt_static_metacall (_o=0x13ccfb0, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0x7ff5c000bb60) at /home/chrigi/devel/kde/build/kolab410/kdepimlibs/kimap/moc_session.cpp:80
#11 0x0000003a5b38c24e in QObject::event (this=0x13ccfb0, e=<optimized out>) at kernel/qobject.cpp:1194
#12 0x000000335edca5cc in QApplicationPrivate::notify_helper (this=this@entry=0xda1430, receiver=receiver@entry=0x13ccfb0, e=e@entry=0x7ff5c0246d30) at kernel/qapplication.cpp:4562
#13 0x000000335edcea4a in QApplication::notify (this=0x7ffff768b670, receiver=0x13ccfb0, e=0x7ff5c0246d30) at kernel/qapplication.cpp:4423
#14 0x0000003360c46f16 in KApplication::notify (this=0x7ffff768b670, receiver=0x13ccfb0, event=0x7ff5c0246d30) at /usr/src/debug/kdelibs-4.10.4/kdeui/kernel/kapplication.cpp:311
#15 0x0000003a5b37793e in QCoreApplication::notifyInternal (this=0x7ffff768b670, receiver=receiver@entry=0x13ccfb0, event=event@entry=0x7ff5c0246d30) at kernel/qcoreapplication.cpp:949
#16 0x0000003a5b37b3f1 in sendEvent (event=0x7ff5c0246d30, receiver=0x13ccfb0) at kernel/qcoreapplication.h:231
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xd6f460) at kernel/qcoreapplication.cpp:1573
#18 0x0000003a5b3a5df3 in sendPostedEvents () at kernel/qcoreapplication.h:236
#19 postEventSourceDispatch (s=0xd9ef60) at kernel/qeventdispatcher_glib.cpp:279
#20 0x0000003a54a47a55 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#21 0x0000003a54a47d88 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
#22 0x0000003a54a47e44 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#23 0x0000003a5b3a5f86 in QEventDispatcherGlib::processEvents (this=0xd70d20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#24 0x000000335ee6a73e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#25 0x0000003a5b3765ef in QEventLoop::processEvents (this=this@entry=0x7ffff768b5e0, flags=...) at kernel/qeventloop.cpp:149
#26 0x0000003a5b376878 in QEventLoop::exec (this=0x7ffff768b5e0, flags=...) at kernel/qeventloop.cpp:204
#27 0x0000003a5b37b708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#28 0x00007ff5d18ab467 in Akonadi::ProgressSpinnerDelegate::initStyleOption (this=0x7ffff768b650, option=0xf59400, index=...) at /home/chrigi/devel/kde/kdepimlibs/akonadi/progressspinnerdelegate.cpp:106
#29 0x000000000041eb2d in Akonadi::ResourceBase::init<ImapResource> (argc=3, argv=0x7ffff768b7c8) at /opt/devel/kolab410/include/akonadi/resourcebase.h:192
#30 0x000000000041c85e in main (argc=3, argv=0x7ffff768b7c8) at /home/chrigi/devel/kde/kdepim-runtime/resources/imap/imapresource.cpp:703

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-09-03 08:11:32 UTC

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