Version: (using KDE 4.1.2) OS: Linux Installed from: Ubuntu Packages After experiencing bug 174756, I reconfigured my disconnected IMAP servers. After closing the configuration box with "OK", kmail tried to connect to the two servers, but authentication failed for one of them. Kmail asked for a new password but I hit cancel. The result was an assort(): #6 0xb7f0c410 in __kernel_vsyscall () #7 0xb6372880 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb6374248 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb6ef5795 in qt_message_output () from /usr/lib/libQtCore.so.4 #10 0xb6ef5872 in qFatal () from /usr/lib/libQtCore.so.4 #11 0xb6ef5915 in qt_assert () from /usr/lib/libQtCore.so.4 #12 0xb7a01e4f in ?? () from /usr/lib/libkmailprivate.so.4 #13 0xb7a023e2 in ?? () from /usr/lib/libkmailprivate.so.4 #14 0xb7831660 in ?? () from /usr/lib/libkmailprivate.so.4 #15 0xb78316d5 in ?? () from /usr/lib/libkmailprivate.so.4 #16 0xb7002a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb70037e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #18 0xb79e6209 in ?? () from /usr/lib/libkmailprivate.so.4 #19 0xb79f0608 in ?? () from /usr/lib/libkmailprivate.so.4 #20 0xb79f7c05 in ?? () from /usr/lib/libkmailprivate.so.4 #21 0xb7a00b9a in ?? () from /usr/lib/libkmailprivate.so.4 #22 0xb7002a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #23 0xb70037e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xb5583bdf in KIO::Scheduler::slaveError () from /usr/lib/libkio.so.5 #25 0xb5583e31 in ?? () from /usr/lib/libkio.so.5 #26 0xb558a876 in KIO::Scheduler::qt_metacall () from /usr/lib/libkio.so.5 #27 0xb7002a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #28 0xb70037e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #29 0xb559f879 in KIO::SlaveInterface::error () from /usr/lib/libkio.so.5 #30 0xb55a3547 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #31 0xb559ff67 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #32 0xb558ff8d in KIO::Slave::gotInput () from /usr/lib/libkio.so.5 #33 0xb55929d3 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5 #34 0xb7002a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #35 0xb70037e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #36 0xb54a0747 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5 #37 0xb54a2819 in ?? () from /usr/lib/libkio.so.5 #38 0xb54a29a6 in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5 #39 0xb6ffbbfb in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #40 0xb6ffd771 in QObject::event () from /usr/lib/libQtCore.so.4 #41 0xb66de8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #42 0xb66e676e in QApplication::notify () from /usr/lib/libQtGui.so.4 #43 0xb74bc72d in KApplication::notify () from /usr/lib/libkdeui.so.5 #44 0xb6fede61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #45 0xb6feeae5 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #46 0xb6feecdd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #47 0xb701882f in ?? () from /usr/lib/libQtCore.so.4 #48 0xb4a746f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #49 0xb4a77da3 in ?? () from /usr/lib/libglib-2.0.so.0 #50 0xb4a77f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #51 0xb7018478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #52 0xb6778ee5 in ?? () from /usr/lib/libQtGui.so.4 #53 0xb6fec52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #54 0xb6fec6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #55 0xb6feeda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #56 0xb66de767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #57 0x0804a6c0 in _start () #0 0xb7f0c410 in __kernel_vsyscall ()
You're backtrace is not useful without the debug packages installed. Please read the following page and try to get a better one : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Unfortunately, I'm unable to reproduce this bug, so if the backtrace isn't helpful there's no way to improve it.