| Summary: | Applications crash when losing network connection (KIO::Slave::deref, KIO::Slave::gotInput,..., KIO::ConnectionPrivate::dequeue) | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | ComputerDruid <ComputerDruid> |
| Component: | general | Assignee: | Andreas Hartmetz <ahartmetz> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | andresbajotierra, chapelhilllaptopshop, cobi_rules, MichaelDHall, spam |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi: --- Kontact still crahes on connection problems in 4.4beta2 (4.3.85) |
||
|
Description
ComputerDruid
2009-05-04 15:03:15 UTC
I used the new crash reporter to post this bug report, to test it out. It seems to do a pretty good job. CCing David Faure as it seems to be related to a KIO error. BTW: thanks for the comments about the new crash reporting tool. *** Bug 196862 has been marked as a duplicate of this bug. *** *** Bug 196914 has been marked as a duplicate of this bug. *** *** Bug 198738 has been marked as a duplicate of this bug. *** *** Bug 200589 has been marked as a duplicate of this bug. *** *** Bug 200511 has been marked as a duplicate of this bug. *** *** Bug 199601 has been marked as a duplicate of this bug. *** *** Bug 199358 has been marked as a duplicate of this bug. *** *** Bug 198542 has been marked as a duplicate of this bug. *** *** Bug 197134 has been marked as a duplicate of this bug. *** *** Bug 197090 has been marked as a duplicate of this bug. *** *** Bug 196318 has been marked as a duplicate of this bug. *** *** Bug 195831 has been marked as a duplicate of this bug. *** The problem here is that the Slave is deleted before deref() is called. The scheduler also calls deref() when it receives the slaveDied() signal, and that probably causes the deletion. I would think that the initial ref() prevents that, but apparently it doesn't. It probably only crashes when somewhere in the signalling some client code does event processing (usually some modal dialog, e.g. error msg). Then the deleteLater triggered in deref() kicks in and causes the slave to be deleted before the deref(). It would be easy to work around the crash by doing QPointer<QObject> that( this ); ... if ( that ) deref(); But that's only a workaround for the real bug (just broken refcounting? conceptual issue?). *** Bug 200788 has been marked as a duplicate of this bug. *** *** Bug 201133 has been marked as a duplicate of this bug. *** *** Bug 201203 has been marked as a duplicate of this bug. *** *** Bug 201566 has been marked as a duplicate of this bug. *** *** Bug 201594 has been marked as a duplicate of this bug. *** *** Bug 201595 has been marked as a duplicate of this bug. *** *** Bug 201758 has been marked as a duplicate of this bug. *** *** Bug 201722 has been marked as a duplicate of this bug. *** *** Bug 202082 has been marked as a duplicate of this bug. *** @Frank Osterfeld: which component is the fault causing this crash? We have both KMail and Dolphin bug reports with the same KIO functions; so I'm wondering if merging them (if it's a KIO bug); or leaving them alone (if it is an implementation error on the app side) Thanks *** Bug 202581 has been marked as a duplicate of this bug. *** *** Bug 202957 has been marked as a duplicate of this bug. *** *** Bug 203068 has been marked as a duplicate of this bug. *** *** Bug 203222 has been marked as a duplicate of this bug. *** *** Bug 203392 has been marked as a duplicate of this bug. *** *** Bug 203800 has been marked as a duplicate of this bug. *** Is there any chance this bug is going to be fixed in 4.3.1? Looks like many people are affected. Apart from Kopete Kmail is the only app which frequently crashes in KDE 4.3 @Dario: It seems to be a KIO bug, so I think you can mark all crashes like this as dupes. *** Bug 202615 has been marked as a duplicate of this bug. *** *** Bug 202555 has been marked as a duplicate of this bug. *** *** Bug 202451 has been marked as a duplicate of this bug. *** *** Bug 204301 has been marked as a duplicate of this bug. *** *** Bug 204403 has been marked as a duplicate of this bug. *** *** Bug 204464 has been marked as a duplicate of this bug. *** *** Bug 204564 has been marked as a duplicate of this bug. *** *** Bug 204654 has been marked as a duplicate of this bug. *** As this seems to be a major issue, here is the workaround I mentioned above.
It's not the "proper" fix, but should fix the crash and could be included as hotfix, for 4.3.1. Andreas?
diff --git a/kio/kio/slave.cpp b/kio/kio/slave.cpp
index 28c8417..13171d9 100644
--- a/kio/kio/slave.cpp
+++ b/kio/kio/slave.cpp
@@ -319,6 +319,10 @@ void Slave::gotInput()
{
Q_D(Slave);
ref();
+ //the following 'that' guard is a hotfix for bug 191589 (see comment #15 for some analysis)
+ //and should removed again as soon as someone knowing more about KIO than me looked into it
+ //and hopefully has a proper fix. -Frank Osterfeld
+ QPointer<QObject> that(this);
if (!dispatch())
{
d->connection->close();
@@ -332,7 +336,8 @@ void Slave::gotInput()
// Tell the scheduler about the problem.
emit slaveDied(this);
}
- deref();
+ if (that)
+ deref();
// Here we might be dead!!
}
(In reply to comment #42) > As this seems to be a major issue, here is the workaround I mentioned above. > It's not the "proper" fix, but should fix the crash and could be included as > hotfix, for 4.3.1. Andreas? Recompiling kdelibs now on the first machine... more after a few days. *** Bug 205179 has been marked as a duplicate of this bug. *** *** Bug 205329 has been marked as a duplicate of this bug. *** *** Bug 205393 has been marked as a duplicate of this bug. *** Thanks for testing, even I meant Andreas Hartmetz, the KIO guy I assigned the bug to (on his request). *** Bug 205269 has been marked as a duplicate of this bug. *** *** Bug 205353 has been marked as a duplicate of this bug. *** *** Bug 205773 has been marked as a duplicate of this bug. *** *** Bug 205799 has been marked as a duplicate of this bug. *** (In reply to comment #47) > Thanks for testing, even I meant Andreas Hartmetz, the KIO guy I assigned the > bug to (on his request). :) Sure. So far no problems, i.e. I could not provoke anything bad by pulling the network cable twice. Our mailserver is unusually stable at the moment, though. *** Bug 205789 has been marked as a duplicate of this bug. *** *** Bug 206010 has been marked as a duplicate of this bug. *** *** Bug 206045 has been marked as a duplicate of this bug. *** *** Bug 206147 has been marked as a duplicate of this bug. *** *** Bug 206140 has been marked as a duplicate of this bug. *** (In reply to comment #52) > (In reply to comment #47) > > Thanks for testing, even I meant Andreas Hartmetz, the KIO guy I assigned the > > bug to (on his request). > > :) Sure. So far no problems, i.e. I could not provoke anything bad by pulling > the network cable twice. Our mailserver is unusually stable at the moment, > though. It's not the good way for reproduce this problem. You must have your network cable connected but your internet gateway must be disconnect from internet. So on level of socket the connection is still active. And this in case refresh the imap cache several times. *** Bug 206193 has been marked as a duplicate of this bug. *** *** Bug 206221 has been marked as a duplicate of this bug. *** *** Bug 206355 has been marked as a duplicate of this bug. *** *** Bug 206513 has been marked as a duplicate of this bug. *** *** Bug 206539 has been marked as a duplicate of this bug. *** *** Bug 206571 has been marked as a duplicate of this bug. *** *** Bug 206673 has been marked as a duplicate of this bug. *** *** Bug 206707 has been marked as a duplicate of this bug. *** *** Bug 206763 has been marked as a duplicate of this bug. *** *** Bug 206800 has been marked as a duplicate of this bug. *** *** Bug 206883 has been marked as a duplicate of this bug. *** *** Bug 207017 has been marked as a duplicate of this bug. *** *** Bug 207210 has been marked as a duplicate of this bug. *** *** Bug 207641 has been marked as a duplicate of this bug. *** I have another crash with 4.3.1 (I think its related):
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 KIO::Slave::deref (this=0x8c8930) at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/kio/kio/slave.cpp:242
#6 0x00007faaeb72aaea in KIO::Slave::gotInput (this=0x8c8930) at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/kio/kio/slave.cpp:335
#7 0x00007faaeb72cde8 in KIO::Slave::qt_metacall (this=0x8c8930, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffa2797940)
at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1_build/kio/slave.moc:76
#8 0x00007faaed1f1fa6 in QMetaObject::activate (sender=0x17518e0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101
#9 0x00007faaeb64794f in KIO::ConnectionPrivate::dequeue (this=0x1533200) at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/kio/kio/connection.cpp:82
#10 0x00007faaeb647daa in KIO::Connection::qt_metacall (this=0x17518e0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x278fcb0)
at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1_build/kio/connection.moc:73
#11 0x00007faaed1eebd1 in QObject::event (this=0x17518e0, e=0x27cec30) at kernel/qobject.cpp:1099
#12 0x00007faaedad5a5d in QApplicationPrivate::notify_helper (this=0x63f9e0, receiver=0x17518e0, e=0x27cec30) at kernel/qapplication.cpp:4056
#13 0x00007faaedadd30a in QApplication::notify (this=0x7fffa27984a0, receiver=0x17518e0, e=0x27cec30) at kernel/qapplication.cpp:4021
#14 0x00007faaee621ebb in KApplication::notify (this=0x7fffa27984a0, receiver=0x17518e0, event=0x27cec30)
at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#15 0x00007faaed1e01db in QCoreApplication::notifyInternal (this=0x7fffa27984a0, receiver=0x17518e0, event=0x27cec30) at kernel/qcoreapplication.cpp:606
#16 0x00007faaed1e0b10 in QCoreApplicationPrivate::sendPostedEvents (receiver=<value optimized out>, event_type=0, data=0x60a860) at kernel/qcoreapplication.h:213
#17 0x00007faaed204f23 in postEventSourceDispatch (s=<value optimized out>) at kernel/qcoreapplication.h:218
#18 0x00007faae6a4e4b9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007faae6a51af8 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007faae6a51cac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007faaed204bbf in QEventDispatcherGlib::processEvents (this=0x60a490, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007faaedb5ac4f in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007faaed1debc2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1569094976}) at kernel/qeventloop.cpp:149
#24 0x00007faaed1ded5c in QEventLoop::exec (this=0x7fffa2798300, flags={i = -1569094896}) at kernel/qeventloop.cpp:197
#25 0x00007faaed1e0dac in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x00000000004049e9 in main (argc=1, argv=0x7fffa2798a78) at /var/tmp/portage/kde-base/kontact-4.3.1/work/kontact-4.3.1/kontact/src/main.cpp:218
Same here with clean (unpatched) 4.3.1 (gentoo amd64) after server-side connection break. Have to re-apply Frank's patch to keep testing...
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5 KIO::Slave::deref (this=0x12200e0) at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1/kio/kio/slave.cpp:242
#6 0x00007f2c6ad9420f in KIO::Slave::gotInput (this=0x12200e0) at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1/kio/kio/slave.cpp:335
#7 0x00007f2c6ad96468 in KIO::Slave::qt_metacall (this=0x12200e0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff8e42d2f0)
at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1_build/kio/slave.moc:76
#8 0x00007f2c68744e4d in QMetaObject::activate (sender=0x1227a90, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x2590d20) at kernel/qobject.cpp:3108
#9 0x00007f2c6acb170f in KIO::ConnectionPrivate::dequeue (this=0x12271b0) at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1/kio/kio/connection.cpp:82
#10 0x00007f2c6acb1b6a in KIO::Connection::qt_metacall (this=0x1227a90, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x1163ec0)
at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1_build/kio/connection.moc:73
#11 0x00007f2c687417e1 in QObject::event (this=0x1227a90, e=0xb782c0) at kernel/qobject.cpp:1106
#12 0x00007f2c694f065d in QApplicationPrivate::notify_helper (this=0x68e4b0, receiver=0x1227a90, e=0xb782c0) at kernel/qapplication.cpp:4057
#13 0x00007f2c694f904a in QApplication::notify (this=0x7fff8e42de40, receiver=0x1227a90, e=0xb782c0) at kernel/qapplication.cpp:4022
#14 0x00007f2c6a2bb8ab in KApplication::notify (this=0x7fff8e42de40, receiver=0x1227a90, event=0xb782c0)
at /var/tmp/portage/kde-base/kdelibs-4.3.1/work/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#15 0x00007f2c68732a1b in QCoreApplication::notifyInternal (this=0x7fff8e42de40, receiver=0x1227a90, event=0xb782c0) at kernel/qcoreapplication.cpp:606
#16 0x00007f2c6873335e in QCoreApplicationPrivate::sendPostedEvents (receiver=<value optimized out>, event_type=0, data=0x65e230) at kernel/qcoreapplication.h:213
#17 0x00007f2c687581f3 in postEventSourceDispatch (s=<value optimized out>) at kernel/qcoreapplication.h:218
#18 0x00007f2c63b59bf6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007f2c63b5cde5 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007f2c63b5cff7 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007f2c68757e8f in QEventDispatcherGlib::processEvents (this=0x685950, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#22 0x00007f2c6957681f in QGuiEventDispatcherGlib::processEvents (this=0x20a, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f2c687313d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1908220832}) at kernel/qeventloop.cpp:149
#24 0x00007f2c68731565 in QEventLoop::exec (this=0x7fff8e42dca0, flags={i = -1908220752}) at kernel/qeventloop.cpp:196
#25 0x00007f2c687335fc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000404b59 in main (argc=1, argv=0x7fff8e42e418) at /var/tmp/portage/kde-base/kontact-4.3.1/work/kontact-4.3.1/kontact/src/main.cpp:218
*** Bug 207722 has been marked as a duplicate of this bug. *** *** Bug 207801 has been marked as a duplicate of this bug. *** *** Bug 208053 has been marked as a duplicate of this bug. *** *** Bug 208223 has been marked as a duplicate of this bug. *** *** Bug 208253 has been marked as a duplicate of this bug. *** *** Bug 208370 has been marked as a duplicate of this bug. *** *** Bug 208357 has been marked as a duplicate of this bug. *** *** Bug 208335 has been marked as a duplicate of this bug. *** *** Bug 208515 has been marked as a duplicate of this bug. *** *** Bug 208607 has been marked as a duplicate of this bug. *** *** Bug 208819 has been marked as a duplicate of this bug. *** *** Bug 209088 has been marked as a duplicate of this bug. *** *** Bug 209138 has been marked as a duplicate of this bug. *** *** Bug 209167 has been marked as a duplicate of this bug. *** *** Bug 209870 has been marked as a duplicate of this bug. *** *** Bug 209947 has been marked as a duplicate of this bug. *** *** Bug 210087 has been marked as a duplicate of this bug. *** I tried to reproduce the crash by always going into the error path in gotInput() (s/!dispatch()/true), but to no avail. Seems like some more complex situation must occur for this to be triggered. *** Bug 210187 has been marked as a duplicate of this bug. *** *** Bug 210240 has been marked as a duplicate of this bug. *** *** Bug 210311 has been marked as a duplicate of this bug. *** *** Bug 210436 has been marked as a duplicate of this bug. *** *** Bug 210466 has been marked as a duplicate of this bug. *** *** Bug 210460 has been marked as a duplicate of this bug. *** *** Bug 210843 has been marked as a duplicate of this bug. *** *** Bug 210897 has been marked as a duplicate of this bug. *** *** Bug 211067 has been marked as a duplicate of this bug. *** *** Bug 211364 has been marked as a duplicate of this bug. *** *** Bug 211497 has been marked as a duplicate of this bug. *** Still happens on KDE 4.3.2 (Debian unstable packages). It happened to me after I clicked OK on "The connection to your mailbox got interrupted" or similar message.
Is there anything that can be helped with?
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6 KIO::Slave::deref (this=0xa0da238) at ../../kio/kio/slave.cpp:242
#7 0xb5479c3c in KIO::Slave::gotInput (this=0xa0da238) at ../../kio/kio/slave.cpp:335
#8 0xb547c113 in KIO::Slave::qt_metacall (this=0xa0da238, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf9e7f38) at ./slave.moc:76
#9 0xb715d303 in QMetaObject::activate (sender=0xa73c888, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#10 0xb715df42 in QMetaObject::activate (sender=0xa73c888, m=0xb55654c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#11 0xb5385d57 in KIO::Connection::readyRead (this=0xa73c888) at ./connection.moc:86
#12 0xb5387663 in KIO::ConnectionPrivate::dequeue (this=0x98d48b8) at ../../kio/kio/connection.cpp:82
#13 0xb5387a46 in KIO::Connection::qt_metacall (this=0xa73c888, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xa3009f8) at ./connection.moc:73
#14 0xb7156b0b in QMetaCallEvent::placeMetaCall (this=0xa865730, object=0xa73c888) at kernel/qobject.cpp:477
#15 0xb71585e0 in QObject::event (this=0xa73c888, e=0xa865730) at kernel/qobject.cpp:1110
#16 0xb6787a94 in QApplicationPrivate::notify_helper (this=0x9775060, receiver=0xa73c888, e=0xa865730) at kernel/qapplication.cpp:4065
#17 0xb678fbee in QApplication::notify (this=0xbf9e9a48, receiver=0xa73c888, e=0xa865730) at kernel/qapplication.cpp:3605
#18 0xb7eed0dd in KApplication::notify (this=0xbf9e9a48, receiver=0xa73c888, event=0xa865730) at ../../kdeui/kernel/kapplication.cpp:302
#19 0xb71481eb in QCoreApplication::notifyInternal (this=0xbf9e9a48, receiver=0xa73c888, event=0xa865730) at kernel/qcoreapplication.cpp:610
#20 0xb7148e2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x974eb80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x974eb80) at kernel/qcoreapplication.cpp:1247
#22 0xb714900d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#23 0xb71734cf in QCoreApplication::sendPostedEvents (s=0x9776990) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#24 postEventSourceDispatch (s=0x9776990) at kernel/qeventdispatcher_glib.cpp:276
#25 0xb4874e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0xb4878623 in ?? () from /lib/libglib-2.0.so.0
#27 0xb48787a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0xb7173041 in QEventDispatcherGlib::processEvents (this=0x974e8d0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#29 0xb6827305 in QGuiEventDispatcherGlib::processEvents (this=0x974e8d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0xb714683a in QEventLoop::processEvents (this=0xbf9e866c, flags=...) at kernel/qeventloop.cpp:149
#31 0xb7146c82 in QEventLoop::exec (this=0xbf9e866c, flags=...) at kernel/qeventloop.cpp:201
#32 0xb6c6a873 in QDialog::exec (this=0xa0d3738) at dialogs/qdialog.cpp:498
#33 0xb7e6992c in KMessageBox::createKMessageBox (dialog=0xa0d3738, icon=..., text=..., strlist=..., ask=..., checkboxReturn=0xbf9e89ab, options=..., details=..., notifyType=QMessageBox::Information)
at ../../kdeui/dialogs/kmessagebox.cpp:331
#34 0xb7e6ac41 in KMessageBox::createKMessageBox (dialog=0xa0d3738, icon=QMessageBox::Information, text=..., strlist=..., ask=..., checkboxReturn=0xbf9e89ab, options=..., details=...)
at ../../kdeui/dialogs/kmessagebox.cpp:151
#35 0xb7e6d16a in KMessageBox::informationListWId (parent_id=23068697, text=..., strlist=..., caption=..., dontShowAgainName=..., options=...) at ../../kdeui/dialogs/kmessagebox.cpp:1008
#36 0xb7e6d2d8 in KMessageBox::informationList (parent=0x976c058, text=..., strlist=..., caption=..., dontShowAgainName=..., options=...) at ../../kdeui/dialogs/kmessagebox.cpp:977
#37 0xb7e6d338 in KMessageBox::information (parent=0x976c058, text=..., caption=..., dontShowAgainName=..., options=...) at ../../kdeui/dialogs/kmessagebox.cpp:964
#38 0xb7591058 in KMail::ImapAccountBase::handleError (this=0x9925630, errorCode=149, errorMsg=..., job=0xa450bf0, context=..., abortSync=false) at ../../kmail/imapaccountbase.cpp:1047
#39 0xb7586b63 in KMail::ImapAccountBase::handleJobError (this=0x9925630, job=0xa450bf0, context=..., abortSync=false) at ../../kmail/imapaccountbase.cpp:374
#40 0xb758cbc8 in KMail::ImapAccountBase::slotSimpleResult (this=0x9925630, job=0xa450bf0) at ../../kmail/imapaccountbase.cpp:928
#41 0xb7591c3b in KMail::ImapAccountBase::qt_metacall (this=0x9925630, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbf9e8dac) at ./imapaccountbase.moc:138
#42 0xb759a78a in KMAcctCachedImap::qt_metacall (this=0x9925630, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbf9e8dac) at ./kmacctcachedimap.moc:78
#43 0xb715d303 in QMetaObject::activate (sender=0xa450bf0, from_signal_index=7, to_signal_index=7, argv=0xbf9e8dac) at kernel/qobject.cpp:3112
#44 0xb715df42 in QMetaObject::activate (sender=0xa450bf0, m=0xb7d14c48, local_signal_index=3, argv=0xbf9e8dac) at kernel/qobject.cpp:3186
#45 0xb7bb74e3 in KJob::result (this=0xa450bf0, _t1=0xa450bf0) at ./kjob.moc:188
#46 0xb7bb7989 in KJob::emitResult (this=0xa450bf0) at ../../kdecore/jobs/kjob.cpp:304
#47 0xb53c1bd5 in KIO::SimpleJob::slotFinished (this=0xa450bf0) at ../../kio/kio/job.cpp:477
#48 0xb53be693 in KIO::SimpleJob::slotError (this=0xa450bf0, err=149, errorText=...) at ../../kio/kio/job.cpp:489
#49 0xb53be883 in KIO::SimpleJob::qt_metacall (this=0xa450bf0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf9e8f88) at ./jobclasses.moc:158
#50 0xb715d303 in QMetaObject::activate (sender=0x9f1e568, from_signal_index=6, to_signal_index=6, argv=0xbf9e8f88) at kernel/qobject.cpp:3112
#51 0xb715df42 in QMetaObject::activate (sender=0x9f1e568, m=0xb5568b84, local_signal_index=2, argv=0xbf9e8f88) at kernel/qobject.cpp:3186
#52 0xb54877f9 in KIO::SlaveInterface::error (this=0x9f1e568, _t1=149, _t2=...) at ./slaveinterface.moc:153
#53 0xb548b607 in KIO::SlaveInterface::dispatch (this=0x9f1e568, _cmd=102, rawdata=...) at ../../kio/kio/slaveinterface.cpp:208
#54 0xb5487c47 in KIO::SlaveInterface::dispatch (this=0x9f1e568) at ../../kio/kio/slaveinterface.cpp:91
#55 0xb5479c2d in KIO::Slave::gotInput (this=0x9f1e568) at ../../kio/kio/slave.cpp:322
#56 0xb547c113 in KIO::Slave::qt_metacall (this=0x9f1e568, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf9e9218) at ./slave.moc:76
#57 0xb715d303 in QMetaObject::activate (sender=0xa27f028, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#58 0xb715df42 in QMetaObject::activate (sender=0xa27f028, m=0xb55654c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#59 0xb5385d57 in KIO::Connection::readyRead (this=0xa27f028) at ./connection.moc:86
#60 0xb5387663 in KIO::ConnectionPrivate::dequeue (this=0xa6b6488) at ../../kio/kio/connection.cpp:82
#61 0xb5387a46 in KIO::Connection::qt_metacall (this=0xa27f028, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x9e5bcd8) at ./connection.moc:73
#62 0xb7156b0b in QMetaCallEvent::placeMetaCall (this=0xa29b540, object=0xa27f028) at kernel/qobject.cpp:477
#63 0xb71585e0 in QObject::event (this=0xa27f028, e=0xa29b540) at kernel/qobject.cpp:1110
#64 0xb6787a94 in QApplicationPrivate::notify_helper (this=0x9775060, receiver=0xa27f028, e=0xa29b540) at kernel/qapplication.cpp:4065
#65 0xb678fbee in QApplication::notify (this=0xbf9e9a48, receiver=0xa27f028, e=0xa29b540) at kernel/qapplication.cpp:3605
#66 0xb7eed0dd in KApplication::notify (this=0xbf9e9a48, receiver=0xa27f028, event=0xa29b540) at ../../kdeui/kernel/kapplication.cpp:302
#67 0xb71481eb in QCoreApplication::notifyInternal (this=0xbf9e9a48, receiver=0xa27f028, event=0xa29b540) at kernel/qcoreapplication.cpp:610
#68 0xb7148e2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x974eb80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#69 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x974eb80) at kernel/qcoreapplication.cpp:1247
#70 0xb714900d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#71 0xb71734cf in QCoreApplication::sendPostedEvents (s=0x9776990) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#72 postEventSourceDispatch (s=0x9776990) at kernel/qeventdispatcher_glib.cpp:276
#73 0xb4874e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#74 0xb4878623 in ?? () from /lib/libglib-2.0.so.0
#75 0xb48787a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#76 0xb7173041 in QEventDispatcherGlib::processEvents (this=0x974e8d0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#77 0xb6827305 in QGuiEventDispatcherGlib::processEvents (this=0x974e8d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#78 0xb714683a in QEventLoop::processEvents (this=0xbf9e9950, flags=...) at kernel/qeventloop.cpp:149
#79 0xb7146c82 in QEventLoop::exec (this=0xbf9e9950, flags=...) at kernel/qeventloop.cpp:201
#80 0xb71490d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#81 0xb6787917 in QApplication::exec () at kernel/qapplication.cpp:3525
#82 0x0804a6d0 in main (argc=136, argv=0x29) at ../../kmail/main.cpp:146
*** Bug 211727 has been marked as a duplicate of this bug. *** *** Bug 212010 has been marked as a duplicate of this bug. *** *** Bug 212281 has been marked as a duplicate of this bug. *** *** Bug 212254 has been marked as a duplicate of this bug. *** *** Bug 212649 has been marked as a duplicate of this bug. *** *** Bug 212940 has been marked as a duplicate of this bug. *** *** Bug 213403 has been marked as a duplicate of this bug. *** *** Bug 213372 has been marked as a duplicate of this bug. *** *** Bug 213374 has been marked as a duplicate of this bug. *** Hmmm.. still crashing on 4.3.3. Kontact/Kmail is crashing several times a day here since 6 (!) months now. :-( Will this ever be fixed? Is it so hard to track the issue down? > Will this ever be fixed? Is it so hard to track the issue down?
Fixed? How dare you? What once was a bug, has now become a feature :-) All the members of this bug report are member of a secret society whose rhythm is defined by its crashes and constantly new members being initiated by experiencing this bug too and joining the club by marked as duplicates. :-)
Fixing this bug would throw the members of this society into into chaos, causing more problems then the bug itself. Therefor this "bug" has remain at least until KDE5.
;-)
SCNR
*** Bug 213613 has been marked as a duplicate of this bug. *** *** Bug 213688 has been marked as a duplicate of this bug. *** If this is the same crash as bug 199375, then a possible fix for it was committed a week ago -> fix will be in KDE 4.3.4 if there's one, otherwise in 4.4.0. *** Bug 213565 has been marked as a duplicate of this bug. *** *** Bug 213768 has been marked as a duplicate of this bug. *** *** Bug 213968 has been marked as a duplicate of this bug. *** *** Bug 214078 has been marked as a duplicate of this bug. *** *** Bug 214230 has been marked as a duplicate of this bug. *** *** Bug 214260 has been marked as a duplicate of this bug. *** *** Bug 214433 has been marked as a duplicate of this bug. *** *** Bug 214359 has been marked as a duplicate of this bug. *** *** Bug 214728 has been marked as a duplicate of this bug. *** Copy/paste from #214728: What I was doing when the application crashed: I tried to open a link in an email. Then, kmail opened a dialog and asked me to choose an application for opening the link. I choosed firefox from the menu and "firefox %u" appeared in the text field. After clicking the button to proceed, firefox showed up and kmail segfaults. I'd like to mention the link in the mail was set like: (Name of site, http://www.foo.bar/address/extension). Firefox shows in its address bar: http://www.foo.bar/address/extension). Thus, the site didn't show up because of ")." at the end. I was able to reproduce the crash several times. *** Bug 214737 has been marked as a duplicate of this bug. *** *** Bug 214910 has been marked as a duplicate of this bug. *** *** Bug 215024 has been marked as a duplicate of this bug. *** *** Bug 215199 has been marked as a duplicate of this bug. *** *** Bug 215399 has been marked as a duplicate of this bug. *** *** Bug 216078 has been marked as a duplicate of this bug. *** *** Bug 216142 has been marked as a duplicate of this bug. *** *** Bug 216303 has been marked as a duplicate of this bug. *** *** Bug 216271 has been marked as a duplicate of this bug. *** *** Bug 216140 has been marked as a duplicate of this bug. *** *** Bug 216266 has been marked as a duplicate of this bug. *** I'm unable to reproduce this bug with KMail. From the reports, it seems like the message box that says "The connection to the server %1 was unexpectedly closed or timed out. It will be re-established automatically if possible." causes the problem. That message box is shown when the connection times out or gets broken. So I lowered the network timeout settings in System Settings and pulled the network cable to get the message box. Clicking Ok however didn't make KMail crash. So I can't do much about this, I'm afraid. It seems like this bug is fixed in current Gentoo Linux. I have not had any crash for a very long time now, in spite of losing network connectivity. I dont know enough to narrow this down, though... FYI, regarding Bug #206045, I've avoided the problem that it was causing in Konqueror by checking the "don't ask again" option and then dismissing the "about to leave secure mode" dialog that Konqueror was giving me. Not the best solution, but it's prevented Konqueror from crashing in that situation any more. Good luck! SVN commit 1056317 by osterfeld: don't kill and emit slaveDied() again if already marked as dead. If clients show a dialog e.g. after error/slaveDied is emitted, the timeout might occur while the dialog is shown, causing slaveDied() to be emitted twice. That results in an extra deref(), which then causes the slave to be deleted while the dialog is shown. Return from dialog, local deref() (e.g. in gotInput() ) => crash Might fix 191589 CCBUG:191589 M +2 -1 slave.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1056317 Ok, looked into this one again. I can't reproduce it, which makes fixing the bug, uhm, harder. However, I found the following situation which might well be the reason for the crash: * error occurs in gotInput(), slaveDied/error are emitted. * client code shows modal dialog via exec(). Dialog stays open * timeout occurs: slaveDied emitted again * scheduler receives slaveDied signal and does deref() on the slave. slave is deleted * User closes dialog, control returned to gotInput() * gotInput calls deref() on "this", which is already deleted * Crash Please all test the patch from #143, and/or tell me how to reproduce the crash reliably, if you can. Would be good, if this patch could make it into 4.3.4, if not to late. Then it can be tested by more people. BTW: The amounts of crashes reduced already by moving from 4.3.2 to 4.3.3 SVN commit 1056324 by osterfeld: forwardport: SVN commit 1056317 by osterfeld: don't kill and emit slaveDied() again if already marked as dead. If clients show a dialog e.g. after error/slaveDied is emitted, the timeout might occur while the dialog is shown, causing slaveDied() to be emitted twice. That results in an extra deref(), which then causes the slave to be deleted while the dialog is shown. Return from dialog, local deref() (e.g. in gotInput() ) => crash Might fix 191589 CCBUG:191589 M +2 -0 slave.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1056324 *** Bug 216815 has been marked as a duplicate of this bug. *** Hi! Sorry, but I don't think my bugreport would be a duplicate of the one you sent me. In my case, network connection was perfect all the time. Only the "freemail.hu" POP3 server causes problems of this kind sometimes. The KMail displays an error message about the "LIST" command, so maybe the network connection is perfect, but the connection to the server itself is troubled in this case. KMail shows the message, and once I click "OK", the software crashes. Not until then. Well, thanks for all! Bye: Andor > https://bugs.kde.org/show_bug.cgi?id=191589 > > > Christophe Giboudeaux <cgiboudeaux@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |andorrr@gmail.com > > > > > --- Comment #147 from Christophe Giboudeaux <cgiboudeaux gmail com> 2009-11-30 16:32:44 --- > *** Bug 216815 has been marked as a duplicate of this bug. *** > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > *** Bug 216897 has been marked as a duplicate of this bug. *** *** Bug 217217 has been marked as a duplicate of this bug. *** *** Bug 217333 has been marked as a duplicate of this bug. *** *** Bug 216226 has been marked as a duplicate of this bug. *** *** Bug 216312 has been marked as a duplicate of this bug. *** *** Bug 218014 has been marked as a duplicate of this bug. *** *** Bug 218100 has been marked as a duplicate of this bug. *** (In reply to comment #141) > It seems like this bug is fixed in current Gentoo Linux. I have not had any > crash for a very long time now, in spite of losing network connectivity. I dont > know enough to narrow this down, though... Definitely not fixed in Gentoo, kde-base/kdelibs-4.3.4. See bug 218100. So far I can tell that the fix didn't make it in time for KDE SC 4.3.4: http://websvn.kde.org/?revision=1056317&view=revision vs http://websvn.kde.org/tags/KDE/4.3.4/kdelibs/kio/kio/slave.cpp?view=log May be the packages should be contacted to include it as a patch... *** Bug 217891 has been marked as a duplicate of this bug. *** *** Bug 217874 has been marked as a duplicate of this bug. *** *** Bug 218085 has been marked as a duplicate of this bug. *** *** Bug 216910 has been marked as a duplicate of this bug. *** @Frank: bug 218143 appeared on 4.4beta1(which includes your fix), so... it could be a different issue or your commit didn't fixed all the cases :( Created attachment 39017 [details]
New crash information added by DrKonqi
Mh, it seems the is still here... (information in comment 163) Updated backtrace: --- #5 KIO::Slave::deref (this=0x17c2030) at /var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kio/kio/slave.cpp:242 #6 0x00007fd1927c0809 in KIO::Slave::gotInput (this=0x17c2030) at /var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kio/kio/slave.cpp:335 #7 0x00007fd1927c0a0c in KIO::Slave::qt_metacall (this=0x17c2030, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff732ffb20) at /var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80_build/kio/slave.moc:82 #8 0x00007fd194e47c73 in QMetaObject::activate (sender=0xe858a0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x2068194) at kernel/qobject.cpp:3286 #9 0x00007fd1926dfd97 in KIO::ConnectionPrivate::dequeue (this=0x17c2060) at /var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80/kio/kio/connection.cpp:82 #10 0x00007fd1926dfebd in KIO::Connection::qt_metacall (this=0xe858a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2153a00) at /var/tmp/portage/kde-base/kdelibs-4.3.80/work/kdelibs-4.3.80_build/kio/connection.moc:79 *** Bug 218508 has been marked as a duplicate of this bug. *** *** Bug 218745 has been marked as a duplicate of this bug. *** *** Bug 219075 has been marked as a duplicate of this bug. *** *** Bug 219091 has been marked as a duplicate of this bug. *** *** Bug 219258 has been marked as a duplicate of this bug. *** *** Bug 219332 has been marked as a duplicate of this bug. *** Created attachment 39284 [details]
New crash information added by DrKonqi:
---
Kontact still crahes on connection problems in 4.4beta2 (4.3.85)
@Marc: the new backtrace is unrelated to this crash. *** Bug 220105 has been marked as a duplicate of this bug. *** SVN commit 1067053 by osterfeld: Next try to fix the event loop reentrancy issue: If we were already dead (timeout, for example) and thus slaveDied() was emitted (dead is only set to true before slaveDied() calls), don't try to act on input and potentially emit slaveDied() a second time (causing an unbalanced deref() and then crash). CCBUG:191589 M +3 -1 slave.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1067053 *** Bug 220486 has been marked as a duplicate of this bug. *** *** Bug 220573 has been marked as a duplicate of this bug. *** *** Bug 220603 has been marked as a duplicate of this bug. *** *** Bug 220783 has been marked as a duplicate of this bug. *** *** Bug 221032 has been marked as a duplicate of this bug. *** *** Bug 221133 has been marked as a duplicate of this bug. *** *** Bug 221266 has been marked as a duplicate of this bug. *** *** Bug 221452 has been marked as a duplicate of this bug. *** *** Bug 215328 has been marked as a duplicate of this bug. *** *** Bug 222952 has been marked as a duplicate of this bug. *** *** Bug 223254 has been marked as a duplicate of this bug. *** *** Bug 223274 has been marked as a duplicate of this bug. *** If I do: 1) update mail but before it times out 2) abort then 3) now it updates OK It acts as if the connection is left open, and only by aborting and restarting it will work. *** Bug 223367 has been marked as a duplicate of this bug. *** *** Bug 223485 has been marked as a duplicate of this bug. *** *** Bug 223844 has been marked as a duplicate of this bug. *** *** Bug 224090 has been marked as a duplicate of this bug. *** *** Bug 223945 has been marked as a duplicate of this bug. *** *** Bug 225109 has been marked as a duplicate of this bug. *** *** Bug 225402 has been marked as a duplicate of this bug. *** *** Bug 225410 has been marked as a duplicate of this bug. *** interesting ... this report is 9 months old, but I just started getting the crash recently - didn't some attempt to fix it make the situation worse, bringing crashes to those lucky who haven't experienced it earlier?
here's my trace, Fedora 12:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6 KIO::Slave::deref (this=0x9cb0628) at /usr/src/debug/kdelibs-4.3.5/kio/kio/slave.cpp:243
#7 0x05b01057 in KIO::Slave::gotInput (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/kio/kio/slave.cpp:336
#8 0x05b031b3 in KIO::Slave::qt_metacall (this=<value optimized out>, _c=<value optimized out>, _id=<value optimized out>, _a=<value optimized out>)
at /usr/src/debug/kdelibs-4.3.5/i686-redhat-linux-gnu/kio/slave.moc:76
#9 0x04720c0c in QMetaObject::activate (sender=<value optimized out>, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=<value optimized out>)
at kernel/qobject.cpp:3112
#10 0x04721843 in QMetaObject::activate (sender=<value optimized out>, m=<value optimized out>, local_signal_index=<value optimized out>, argv=<value optimized out>) at kernel/qobject.cpp:3186
#11 0x05a18438 in KIO::Connection::readyRead (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/i686-redhat-linux-gnu/kio/connection.moc:86
#12 0x05a19efe in KIO::ConnectionPrivate::dequeue (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/kio/kio/connection.cpp:82
#13 0x05a1a026 in KIO::Connection::qt_metacall (this=<value optimized out>, _c=<value optimized out>, _id=<value optimized out>, _a=<value optimized out>)
at /usr/src/debug/kdelibs-4.3.5/i686-redhat-linux-gnu/kio/connection.moc:73
#14 0x047197fc in QMetaCallEvent::placeMetaCall (this=<value optimized out>, object=<value optimized out>) at kernel/qobject.cpp:477
#15 0x0471af96 in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1110
#16 0x04caab24 in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:4065
#17 0x04cb2281 in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3605
#18 0x0571a8cb in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at /usr/src/debug/kdelibs-4.3.5/kdeui/kernel/kapplication.cpp:302
#19 0x0470ad73 in QCoreApplication::notifyInternal (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at kernel/qcoreapplication.cpp:610
#20 0x0470b972 in sendEvent (receiver=<value optimized out>, event_type=<value optimized out>, data=<value optimized out>) at kernel/qcoreapplication.h:213
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=<value optimized out>, event_type=<value optimized out>, data=<value optimized out>) at kernel/qcoreapplication.cpp:1247
#22 0x0470bb2e in QCoreApplication::sendPostedEvents (receiver=<value optimized out>, event_type=<value optimized out>) at kernel/qcoreapplication.cpp:1140
#23 0x04735f40 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:218
#24 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#25 0x014a8f88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x014ac8b8 in ?? () from /lib/libglib-2.0.so.0
#27 0x014ac9e4 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x04735b6d in QEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#29 0x04d4a356 in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x047092aa in QEventLoop::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:149
#31 0x0470970a in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:201
#32 0x0470bbf7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x04caa9a8 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x0804a59e in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.3.5/kmail/main.cpp:146
So far, the crashes seem to have stopped appearing on KDE SC 4.4 RC2+ (because a second fix was applied). I think no fixes were backported to KDE SC 4.3.x, so that shouldn't be the reason for the app to crash on 4.3.5.... Regards I'm confused. I have not had a Kontact crash for a few days with inconsistent network access which would normally cause an issue. However, I don't recall seeing an update recently which would impact this. Looking in /var/cache/apt/archive, I see nothing of interest in the last two updates done on 1/28 and 1/20. What!? Does this bug have some sort of lysine deficiency? Or am I in a blessed-state which won't last long? Kubuntu 9.10 Kontact 4.3.2 KMail 1.12.2 Wow, what timing... <crash> *** Bug 226433 has been marked as a duplicate of this bug. *** *** Bug 226443 has been marked as a duplicate of this bug. *** *** Bug 227086 has been marked as a duplicate of this bug. *** It would be interesting to know if this bug still occurs in trunk with the new KIO scheduler. I've also changed a few things that looked fishy in KIO::Slave or SlaveInterface, don't remember which. They didn't look very related to this though. *** Bug 227316 has been marked as a duplicate of this bug. *** So far there are no 4.4.0 (4.3.98+) crashes, so we could assume that the commits already mentioned (comment 143, comment 146, comment 147, comment 174) fixes the crash. + the new scheduler implementation on 4.5 trunk. Marking as FIXED. I will reopen if there is a 4.4 case. Cleaning CC list, removing 4.4.0-blocker keyword Please tell me these fixes will be backported to my current version of Kontact/Kmail/KDE (4.3.2) soon because I just decided this morning to switch to using Evolution. Yesterday several things hit me that were all caused by losing emails and losing calendar entries, I assume from all the crashing. Yesterday was a miserable day, and I'm barely digging out today. If I don't have much hope of seeing this in my current version of Kubuntu *very soon* I can't help but make the change. I cannot afford another yesterday, you only get one of those about every six months. I'm sorry about your problems :-\ You can ask Kubuntu to backport the changes to 4.3.2; but consider that 4.3.2 is a bit old (4.3.5 was released some time ago, and 4.4.0 is the new latest stable release) You can get KDE SC 4.4.0 for Kubuntu at http://www.kubuntu.org/news/kde-sc-4.4 Note that all the mails/events problem could not be related with this specific crash. (also note that I'm not a KMail/Kontact developer) Regards *** Bug 218143 has been marked as a duplicate of this bug. *** *** Bug 227924 has been marked as a duplicate of this bug. *** *** Bug 225836 has been marked as a duplicate of this bug. *** *** Bug 221842 has been marked as a duplicate of this bug. *** *** Bug 220674 has been marked as a duplicate of this bug. *** *** Bug 228342 has been marked as a duplicate of this bug. *** *** Bug 229193 has been marked as a duplicate of this bug. *** *** Bug 229608 has been marked as a duplicate of this bug. *** *** Bug 221427 has been marked as a duplicate of this bug. *** The latest samba fixes appears to have cured my particular problem, when copying a fairly (250 MB) large folder. Thanks, John ---------- Original Message ---------- From: Dario Andres <andresbajotierra@gmail.com> To: johnisfound@netzero.com Subject: [Bug 191589] Applications crash when losing network connection (KIO::Slave::deref, KIO::Slave::gotInput,..., KIO::ConnectionPrivate::dequeue) Date: Wed, 17 Mar 2010 23:36:28 +0100 (CET) https://bugs.kde.org/show_bug.cgi?id=191589 Dario Andres <andresbajotierra@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johnisfound@netzero.com --- Comment #216 from Dario Andres <andresbajotierra gmail com> 2010-03-17 23:36:24 --- *** Bug 221427 has been marked as a duplicate of this bug. *** *** Bug 230406 has been marked as a duplicate of this bug. *** *** Bug 230389 has been marked as a duplicate of this bug. *** *** Bug 232024 has been marked as a duplicate of this bug. *** *** Bug 232335 has been marked as a duplicate of this bug. *** *** Bug 232575 has been marked as a duplicate of this bug. *** *** Bug 232741 has been marked as a duplicate of this bug. *** *** Bug 233541 has been marked as a duplicate of this bug. *** *** Bug 236055 has been marked as a duplicate of this bug. *** *** Bug 238841 has been marked as a duplicate of this bug. *** *** Bug 240401 has been marked as a duplicate of this bug. *** *** Bug 236029 has been marked as a duplicate of this bug. *** *** Bug 234372 has been marked as a duplicate of this bug. *** *** Bug 234519 has been marked as a duplicate of this bug. *** *** Bug 222413 has been marked as a duplicate of this bug. *** *** Bug 247016 has been marked as a duplicate of this bug. *** *** Bug 247429 has been marked as a duplicate of this bug. *** *** Bug 261176 has been marked as a duplicate of this bug. *** *** Bug 262766 has been marked as a duplicate of this bug. *** *** Bug 266794 has been marked as a duplicate of this bug. *** *** Bug 275772 has been marked as a duplicate of this bug. *** Hi, I just got this bug on Centos 6.2 x64 Packet kdepim-4.3.4-5.el6.x86_64 Backtrace #0 0x0000003dfbc0f36b in raise () from /lib64/libpthread.so.0 #1 0x0000003dc8e55455 in KCrash::defaultCrashHandler(int) () from /usr/lib64/libkdeui.so.5 #2 <signal handler called> #3 0x0000003dc9390f78 in KIO::Slave::deref() () from /usr/lib64/libkio.so.5 #4 0x0000003dc9391639 in KIO::Slave::gotInput() () from /usr/lib64/libkio.so.5 #5 0x0000003dc939348c in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #6 0x0000003e0656a52f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #7 0x0000003dc92bb9d7 in ?? () from /usr/lib64/libkio.so.5 #8 0x0000003dc92bbaed in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #9 0x0000003e06566a01 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #10 0x0000003dc7baaa0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #11 0x0000003dc7bb09db in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #12 0x0000003dc8df8046 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #13 0x0000003e065579fc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #14 0x0000003e06558747 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #15 0x0000003e0657d793 in ?? () from /usr/lib64/libQtCore.so.4 #16 0x0000003dfcc38f0e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x0000003dfcc3c938 in ?? () from /lib64/libglib-2.0.so.0 #18 0x0000003dfcc3ca3a in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x0000003e0657d2d3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #20 0x0000003dc7c4990e in ?? () from /usr/lib64/libQtGui.so.4 #21 0x0000003e06556442 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #22 0x0000003e0655670c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #23 0x0000003e065589f9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #24 0x0000000000403d27 in _start () I can provide the whole abrt log |