Bug 193501 - Kontact crash using IMAP
Summary: Kontact crash using IMAP
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-21 14:38 UTC by Nicolas Schirrer
Modified: 2009-10-23 10:42 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 Nicolas Schirrer 2009-05-21 14:38:09 UTC
Application that crashed: kontact
Version of the application: 4.3.0 pre
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-5-generic i686
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
Crash browsing email in Gmail inbox, in IMAP mode.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb517d98e in ?? () from /usr/lib/libkmailprivate.so.4
#7  0xb4e15ec2 in ?? () from /usr/lib/libkmailprivate.so.4
#8  0xb514f516 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb5153e7f in ?? () from /usr/lib/libkmailprivate.so.4
#10 0x003e6d78 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0x003e7a12 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0x009f4873 in KJob::result () from /usr/lib/libkdecore.so.5
#13 0x009f4cf9 in KJob::emitResult () from /usr/lib/libkdecore.so.5
#14 0x03181600 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.5
#15 0x03181b1a in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.5
#16 0x0317f2a3 in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5
#17 0x003e6d78 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0x003e7a12 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0x0324c7a7 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.5
#20 0x0325061d in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#21 0x0324cc63 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#22 0x0323ea2a in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#23 0x03240e7b in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#24 0x003e6d78 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0x003e7a12 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#26 0x03148417 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#27 0x0314a22e in ?? () from /usr/lib/libkio.so.5
#28 0x0314a366 in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#29 0x003df7fb in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#30 0x003e0eee in QObject::event () from /usr/lib/libQtCore.so.4
#31 0x00f2bc1c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#32 0x00f333f4 in QApplication::notify () from /usr/lib/libQtGui.so.4
#33 0x006d450a in KApplication::notify () from /usr/lib/libkdeui.so.5
#34 0x003d0b1b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#35 0x003d15e8 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#36 0x003d17bd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#37 0x003fc36f in ?? () from /usr/lib/libQtCore.so.4
#38 0x055dbf68 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#39 0x055df578 in ?? () from /usr/lib/libglib-2.0.so.0
#40 0x055df6ea in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#41 0x003fbf9c in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#42 0x00fcd975 in ?? () from /usr/lib/libQtGui.so.4
#43 0x003cf0a9 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#44 0x003cf4f2 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#45 0x003d187f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#46 0x00f2ba97 in QApplication::exec () from /usr/lib/libQtGui.so.4
#47 0x0804b4da in _start ()

This bug may be a duplicate of or related to bug 186063
Comment 1 Dario Andres 2009-05-22 03:54:25 UTC
Mh, the backtrace doesn't contain a lot of information. If you experience this regularly, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You need to install the "kdepim-dbg" package
Thanks
Comment 2 Dario Andres 2009-06-26 15:57:38 UTC
Marking as NEEDSINFO
Comment 3 Christophe Marin 2009-10-23 10:42:28 UTC
Closing the old crash reports which don't have a useful backtrace. Thanks.