Bug 240401 - kmail crash after suspend to disk re-awakening and error message concerning dIMAP connection
Summary: kmail crash after suspend to disk re-awakening and error message concerning d...
Status: RESOLVED DUPLICATE of bug 191589
Alias: None
Product: kmail
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: 2010-06-02 00:25 UTC by Bruno Labadia
Modified: 2010-06-06 23:30 UTC (History)
0 users

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 Bruno Labadia 2010-06-02 00:25:51 UTC
Application that crashed: kmail
Version of the application: 1.12.4
KDE Version: 4.3.5 (KDE 4.3.5) "release 4"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.2-default i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
Crash occurs each time I check a dIMAP email account after restarting the laptop after suspend to disk. 
When checking the dIMAP email account immediately after re-awakening the system and immediately cancelling the process of checking the dIMAP server, no crash occurs.
 
A second attempt to check the dIMAP server is successful then.

Only when forgetting to check and cancel the check of my dIMAP account immediately after re-awakening then after about 5 minutes the message about the inability to connect to the dIMAP server pops up.
When closing the pop-up message, kmail crashes.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0xb4a3821d in KIO::Slave::deref() () from /usr/lib/libkio.so.5
#7  0xb4a38a71 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#8  0xb4a3b0d4 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#9  0xb67d4864 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#10 0xb67d5585 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0xb49384e5 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#12 0xb493a3ca in ?? () from /usr/lib/libkio.so.5
#13 0xb493a517 in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#14 0xb67cd04a in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#15 0xb67ce796 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0xb5e048fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb5e0c34e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb75c6521 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0xb67be32e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0xb67befdc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0xb67bf19c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#22 0xb67ea4dd in ?? () from /usr/lib/libQtCore.so.4
#23 0xb3ddc4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb3ddfd98 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb3ddfebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb67ea011 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb5ea629a in ?? () from /usr/lib/libQtGui.so.4
#28 0xb67bc98d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0xb67bcdd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0xb67bf270 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0xb5e04774 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0x0804a732 in _start ()

This bug may be a duplicate of or related to bug 219091

Reported using DrKonqi
Comment 1 Christophe Marin 2010-06-06 23:30:04 UTC

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