Bug 231394 - kmail crash while fetching imap messages
Summary: kmail crash while fetching imap messages
Status: RESOLVED DUPLICATE of bug 191345
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-20 09:30 UTC by p92
Modified: 2010-09-19 21:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description p92 2010-03-20 09:30:25 UTC
Application: kontact (4.4.1)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.31-20-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
I added a new imap mailbox
when I click on the mailbox I see it has no inbox
I reconfigured the imap account to use TLS
I then sent an email to this account

when I clicked on fetch all new messages button  kmail crashed.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7717760 (LWP 14959))]

Thread 3 (Thread 0xb33cbb70 (LWP 13344)):
#0  0x00d73422 in __kernel_vsyscall ()
#1  0x00d52142 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0x00e7e8d4 in __pthread_cond_timedwait (cond=0xca1c5c0, mutex=0xca1c5a8, abstime=0xb33cb2d0) at forward.c:152
#3  0x041499ff in ?? () from /usr/lib/libxine.so.1
#4  0x00d4d80e in start_thread (arg=0xb33cbb70) at pthread_create.c:300
#5  0x00e718de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xaa398b70 (LWP 13350)):
#0  0x00d51144 in __pthread_mutex_unlock_usercnt (mutex=0x9b69fbc, decr=<value optimized out>) at pthread_mutex_unlock.c:52
#1  0x00e7ea86 in pthread_mutex_unlock (mutex=0x9b69fbc) at forward.c:184
#2  0x020ab5df in ?? () from /lib/libglib-2.0.so.0
#3  0x020ab863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0x0118b83f in QEventDispatcherGlib::processEvents (this=0xb677c78, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#5  0x0115e209 in QEventLoop::processEvents (this=0xaa398230, flags=) at kernel/qeventloop.cpp:149
#6  0x0115e65a in QEventLoop::exec (this=0xaa398230, flags=...) at kernel/qeventloop.cpp:201
#7  0x0105a5e8 in QThread::exec (this=0xc132648) at thread/qthread.cpp:487
#8  0x0403ca5a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#9  0x0105d36e in QThreadPrivate::start (arg=0xc132648) at thread/qthread_unix.cpp:248
#10 0x00d4d80e in start_thread (arg=0xaa398b70) at pthread_create.c:300
#11 0x00e718de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7717760 (LWP 14959)):
[KCrash Handler]
#6  0x003dac6a in KPIM::ProgressItem::removeChild(KPIM::ProgressItem*) () from /usr/lib/libkdepim.so.4
#7  0x003dadf9 in KPIM::ProgressItem::setComplete() () from /usr/lib/libkdepim.so.4
#8  0xb43e14ab in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb42e5042 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0xb42e59b7 in ?? () from /usr/lib/libkmailprivate.so.4
#11 0x01164e5a in QMetaObject::metacall (object=0xa421830, cl=221, idx=13, argv=0xbff3ab58) at kernel/qmetaobject.cpp:237
#12 0x011735f5 in QMetaObject::activate (sender=0x1142f638, m=0xce4c48, local_signal_index=3, argv=0xbff3ab58) at kernel/qobject.cpp:3293
#13 0x00b71fa3 in KJob::result (this=0x1142f638, _t1=0x1142f638) at ./kjob.moc:194
#14 0x00b72308 in KJob::emitResult (this=0x1142f638) at ../../kdecore/jobs/kjob.cpp:312
#15 0x0198f2f0 in KIO::SimpleJob::slotFinished (this=0x1142f638) at ../../kio/kio/job.cpp:486
#16 0x0198f45e in KIO::ListJob::slotFinished (this=0x1142f638) at ../../kio/kio/job.cpp:2505
#17 0x019930ae in KIO::ListJob::qt_metacall (this=0x1142f638, _c=QMetaObject::InvokeMetaMethod, _id=43, _a=0xbff3adbc) at ./jobclasses.moc:818
#18 0x01164e5a in QMetaObject::metacall (object=0x1142f638, cl=221, idx=43, argv=0xbff3adbc) at kernel/qmetaobject.cpp:237
#19 0x011735f5 in QMetaObject::activate (sender=0xa282bc0, m=0x1b3cf44, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3293
#20 0x01a59097 in KIO::SlaveInterface::finished (this=0xa282bc0) at ./slaveinterface.moc:171
#21 0x01a5c3bd in KIO::SlaveInterface::dispatch (this=0xa282bc0, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#22 0x01a59553 in KIO::SlaveInterface::dispatch (this=0xa282bc0) at ../../kio/kio/slaveinterface.cpp:91
#23 0x01a4c8f8 in KIO::Slave::gotInput (this=0xa282bc0) at ../../kio/kio/slave.cpp:324
#24 0x01a4cb03 in KIO::Slave::qt_metacall (this=0xa282bc0, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbff3b0cc) at ./slave.moc:82
#25 0x01164e5a in QMetaObject::metacall (object=0xa282bc0, cl=221, idx=30, argv=0xbff3b0cc) at kernel/qmetaobject.cpp:237
#26 0x011735f5 in QMetaObject::activate (sender=0xa100788, m=0x1b39820, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#27 0x01957d17 in KIO::Connection::readyRead (this=0xa100788) at ./connection.moc:92
#28 0x0195a0be in KIO::ConnectionPrivate::dequeue (this=0xa43a938) at ../../kio/kio/connection.cpp:82
#29 0x0195a1ee in KIO::Connection::qt_metacall (this=0xa100788, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xf4bddf0) at ./connection.moc:79
#30 0x01164e5a in QMetaObject::metacall (object=0xa100788, cl=221, idx=5, argv=0xf4bddf0) at kernel/qmetaobject.cpp:237
#31 0x0116f516 in QMetaCallEvent::placeMetaCall (this=0x10172408, object=0xa100788) at kernel/qobject.cpp:561
#32 0x0117063e in QObject::event (this=0xa100788, e=0x10172408) at kernel/qobject.cpp:1248
#33 0x02ff73cc in QApplicationPrivate::notify_helper (this=0x9b71380, receiver=0xa100788, e=0x10172408) at kernel/qapplication.cpp:4300
#34 0x02ffe01e in QApplication::notify (this=0xbff3ba24, receiver=0xa100788, e=0x10172408) at kernel/qapplication.cpp:3704
#35 0x0067342a in KApplication::notify (this=0xbff3ba24, receiver=0xa100788, event=0x10172408) at ../../kdeui/kernel/kapplication.cpp:302
#36 0x0115fbeb in QCoreApplication::notifyInternal (this=0xbff3ba24, receiver=0xa100788, event=0x10172408) at kernel/qcoreapplication.cpp:704
#37 0x01162623 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9b4ab68) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#38 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9b4ab68) at kernel/qcoreapplication.cpp:1345
#39 0x0116278d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238
#40 0x0118bd0f in QCoreApplication::sendPostedEvents (s=0x9b76a90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#41 postEventSourceDispatch (s=0x9b76a90) at kernel/qeventdispatcher_glib.cpp:276
#42 0x020a7e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#43 0x020ab730 in ?? () from /lib/libglib-2.0.so.0
#44 0x020ab863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#45 0x0118b805 in QEventDispatcherGlib::processEvents (this=0x9b4a700, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#46 0x030b6b35 in QGuiEventDispatcherGlib::processEvents (this=0x9b4a700, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#47 0x0115e209 in QEventLoop::processEvents (this=0xbff3b984, flags=) at kernel/qeventloop.cpp:149
#48 0x0115e65a in QEventLoop::exec (this=0xbff3b984, flags=...) at kernel/qeventloop.cpp:201
#49 0x0116284f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#50 0x02ff7467 in QApplication::exec () at kernel/qapplication.cpp:3579
#51 0x0804b4c2 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-03-20 19:50:44 UTC
This could be related to bug 191345.
- If you can reproduce the crash at will (or you experience this regularly), can you install the "kdepim-dbg" package and post a complete backtrace here? (you can get more information at http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting ) Thanks
Comment 2 p92 2010-03-20 21:41:51 UTC
additionnally : I found later that I entered an unknown user in the imap account
Comment 3 Christophe Marin 2010-09-19 21:46:22 UTC

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