Bug 234372 - Segmentation fault in kontact/kmail after unexpectedly closed / timed out connection to dimap server (probably duplicate of Bug 191589)
Summary: Segmentation fault in kontact/kmail after unexpectedly closed / timed out con...
Status: RESOLVED DUPLICATE of bug 191589
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: 2010-04-14 19:00 UTC by Sallin
Modified: 2010-06-07 00:22 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 Sallin 2010-04-14 19:00:43 UTC
Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-3-686-bigmem i686
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
After 1 or 2 hours kmail gives the following error message:
"The connection to the server was unexpectedly closed or timed out. It will be re-established automatically if possible."
and then kmail crashes. It shows the same behavior on my laptop and both only related to the disconnected imap account.

I assume it's a duplicate of Bug 191589, which should be fixed in KDE 4.4. Since I'm relatively new to bug reporting, I wonder is it any use to report this one or am I only generating extra work?

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x4ab30b2d in KIO::Slave::deref() () from /usr/lib/libkio.so.5
#7  0x4ab316d6 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#8  0x4ab33ac3 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#9  0x4b8b6963 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x4b8b75a2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x4aa3afc7 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#12 0x4aa3cd8e in ?? () from /usr/lib/libkio.so.5
#13 0x4aa3cebe in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#14 0x4b8b016b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#15 0x4b8b1c40 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x4bb14a34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x4bb1cb8e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x4a6fde2a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x4b8a184b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x4b8a248e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0x4b8a266d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#22 0x4b8ccb2f in ?? () from /usr/lib/libQtCore.so.4
#23 0x4b3502e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x4b354000 in ?? () from /lib/libglib-2.0.so.0
#25 0x4b354198 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x4b8cc6a1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0x4bbb42a5 in ?? () from /usr/lib/libQtGui.so.4
#28 0x4b89fe9a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x4b8a02e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x4b8a2739 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0x4bb148b7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0x0804b4c6 in _start ()

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

Reported using DrKonqi
Comment 1 Christophe Marin 2010-06-07 00:22:33 UTC

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