Bug 181621 - KMail crashes when trying to display IMAP folder.
Summary: KMail crashes when trying to display IMAP folder.
Status: RESOLVED DUPLICATE of bug 179765
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-22 23:20 UTC by Peter Lewis
Modified: 2009-03-19 00:39 UTC (History)
1 user (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 Peter Lewis 2009-01-22 23:20:57 UTC
Version:           1.10.4 (KDE 4.1.4) (using Devel)
OS:                Linux
Installed from:    Compiled sources

Not sure what's caused this. It seems that a folder might have got corrupted such that KMail can no longer open it... All I did was to click on an IMAP (sub)folder with some new messages in it. Here's the backtrack:

Application: KMail (kmail), signal SIGSEGV

Thread 1 (Thread 0xb4370920 (LWP 21308)):
[KCrash Handler]
#6  0xb74932d4 in KMFolderImap::slotListFolderResult (this=0x875da08, job=0x9570048) at /home/jan/Dev/packages/kdemod-core/work/kdepim/src/kdepim-4.1.4/kmail/kmfolderimap.cpp:1364
#7  0xb7495704 in KMFolderImap::qt_metacall (this=0x875da08, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0xbfc1943c)
    at /home/jan/Dev/packages/kdemod-core/work/kdepim/src/kdepim-4.1.4/kmail/kmfolderimap.moc:181
#8  0xb7e6db03 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0xb7e6e063 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb7a31e84 in KJob::result () from /usr/lib/libkdecore.so.5
#11 0xb7a323c3 in KJob::emitResult () from /usr/lib/libkdecore.so.5
#12 0xb5ec7b1d in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.5
#13 0xb5ec970f in KIO::ListJob::slotFinished () from /usr/lib/libkio.so.5
#14 0xb5ecd5cb in KIO::ListJob::qt_metacall () from /usr/lib/libkio.so.5
#15 0xb7e6db03 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7e6e063 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb5f920a8 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.5
#18 0xb5f95d77 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#19 0xb5f9284c in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#20 0xb5f8262e in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#21 0xb5f850ab in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#22 0xb7e6db03 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb7e6e063 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb5e8dd88 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#25 0xb5e8fedd in KIO::ConnectionPrivate::dequeue () from /usr/lib/libkio.so.5
#26 0xb5e9005e in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#27 0xb7e6892b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4
#28 0xb7e6a4f9 in QObject::event () from /usr/lib/libQtCore.so.4
#29 0xb5123eac in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#30 0xb512a423 in QApplication::notify () from /usr/lib/libQtGui.so.4
#31 0xb5b1e4ce in KApplication::notify () from /usr/lib/libkdeui.so.5
#32 0xb7e5bf60 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#33 0xb7e5c8e0 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#34 0xb7e5ca7e in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#35 0xb7e83090 in ?? () from /usr/lib/libQtCore.so.4
#36 0x00000000 in ?? ()
Comment 1 Dario Andres 2009-01-23 00:22:43 UTC
The fix is in 4.2 :)

*** This bug has been marked as a duplicate of bug 179765 ***
Comment 2 Peter Lewis 2009-01-23 01:26:00 UTC
Nice to hear - thanks!