Bug 207641 - kmail crashed after closing alert about timeouted mailserver
Summary: kmail crashed after closing alert about timeouted mailserver
Status: RESOLVED DUPLICATE of bug 191589
Alias: None
Product: kmail
Classification: Unmaintained
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-16 23:47 UTC by Jan Matějka
Modified: 2009-09-17 09:02 UTC (History)
0 users

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 Jan Matějka 2009-09-16 23:47:22 UTC
Application that crashed: kmail
Version of the application: 1.12.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-0.slh.1-sidux-686 i686
Distribution: Debian GNU/Linux 5.0.3 (lenny)

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  KIO::Slave::deref (this=0x9046e88) at ../../kio/kio/slave.cpp:242
#7  0xb53f990c in KIO::Slave::gotInput (this=0x9046e88) at ../../kio/kio/slave.cpp:335
#8  0xb53fbde3 in KIO::Slave::qt_metacall (this=0x9046e88, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf8dfa18) at ./slave.moc:76
#9  0xb70dcb33 in QMetaObject::activate (sender=0x904c408, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#10 0xb70dd782 in QMetaObject::activate (sender=0x904c408, m=0xb54e54c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#11 0xb5305937 in KIO::Connection::readyRead (this=0x904c408) at ./connection.moc:86
#12 0xb5307243 in KIO::ConnectionPrivate::dequeue (this=0x904c418) at ../../kio/kio/connection.cpp:82
#13 0xb5307626 in KIO::Connection::qt_metacall (this=0x904c408, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x93adf50) at ./connection.moc:73
#14 0xb70d633b in QMetaCallEvent::placeMetaCall (this=0xaf89258, object=0x904c408) at kernel/qobject.cpp:477
#15 0xb70d7e10 in QObject::event (this=0x904c408, e=0xaf89258) at kernel/qobject.cpp:1110
#16 0xb6707814 in QApplicationPrivate::notify_helper (this=0x8413260, receiver=0x904c408, e=0xaf89258) at kernel/qapplication.cpp:4056
#17 0xb670f97e in QApplication::notify (this=0xbf8e0248, receiver=0x904c408, e=0xaf89258) at kernel/qapplication.cpp:3603
#18 0xb7e6b4ad in KApplication::notify (this=0xbf8e0248, receiver=0x904c408, event=0xaf89258) at ../../kdeui/kernel/kapplication.cpp:302
#19 0xb70c79cb in QCoreApplication::notifyInternal (this=0xbf8e0248, receiver=0x904c408, event=0xaf89258) at kernel/qcoreapplication.cpp:610
#20 0xb70c860e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x83ecb80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x83ecb80) at kernel/qcoreapplication.cpp:1247
#22 0xb70c87ed in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#23 0xb70f2c0f in QCoreApplication::sendPostedEvents (s=0x8415510) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#24 postEventSourceDispatch (s=0x8415510) at kernel/qeventdispatcher_glib.cpp:210
#25 0xb47f44b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb47f7a13 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb47f7b98 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb70f2858 in QEventDispatcherGlib::processEvents (this=0x83ec8d0, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#29 0xb67a6fd5 in QGuiEventDispatcherGlib::processEvents (this=0x83ec8d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0xb70c601a in QEventLoop::processEvents (this=0xbf8e0150, flags=...) at kernel/qeventloop.cpp:149
#31 0xb70c6462 in QEventLoop::exec (this=0xbf8e0150, flags=...) at kernel/qeventloop.cpp:201
#32 0xb70c88b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0xb6707697 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x0804a6d0 in _start ()

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

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

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