Bug 206763 - kontact after latest Fedora 11 updates now dies upon checking an IMAP account on a server which ceases to be contactable.
Summary: kontact after latest Fedora 11 updates now dies upon checking an IMAP account...
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: 2009-09-08 17:11 UTC by David Sainty
Modified: 2009-09-08 17:14 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 David Sainty 2009-09-08 17:11:58 UTC
Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.29.6-217.2.16.fc11.x86_64 x86_64
Distribution: "Fedora release 11 (Leonidas)"

What I was doing when the application crashed:
Everytime my IMAP service ceases to be contactable and kmail/kontact initiates a new IMAP connection, it bombs straight after notifying me that the IMAP connection cannot be established.  This is new ill-behaviour not seen until the most recently Fedora 11 updates (now kdepim-4.3.0-4.fc11.x86_64)


 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x0000003850b9e128 in KIO::Slave::deref() () from /usr/lib64/libkio.so.5
#6  0x0000003850b9eb19 in KIO::Slave::gotInput() () from /usr/lib64/libkio.so.5
#7  0x0000003850ba0c1c in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#8  0x000000384db547dc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#9  0x0000003850aba9a7 in ?? () from /usr/lib64/libkio.so.5
#10 0x0000003850abaabd in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#11 0x000000384db4eb51 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#12 0x000000384f38f69c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x000000384f3968fe in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x0000003850011296 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#15 0x000000384db3f59c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x000000384db401a2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#17 0x000000384db67cc3 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x000000356b837abe in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#19 0x000000356b83b278 in ?? () from /lib64/libglib-2.0.so.0
#20 0x000000356b83b3a0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#21 0x000000384db67936 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x000000384f421f8e in ?? () from /usr/lib64/libQtGui.so.4
#23 0x000000384db3ded2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x000000384db3e2a4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x000000384db40439 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#26 0x0000000000403d17 in _start ()

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

Reported using DrKonqi
Comment 1 Christophe Marin 2009-09-08 17:14:35 UTC

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