Summary: | Renaming DIMAP folders crashes KMail | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Unknown <null> |
Component: | disconnected IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | Regnaron, ruchir.brahmbhatt |
Priority: | NOR | Keywords: | triaged |
Version: | 1.10.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Kmail crash - backtrace |
Description
Unknown
2008-08-15 13:41:19 UTC
Created attachment 26859 [details]
Kmail crash - backtrace
You can just post the backtrace directly in the comments field. This makes it easier to search for related bugs :) The original backtrace was: Alkalmazás: KMail (kmail), szignál: SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb48b86d0 (LWP 11761)] [New Thread 0xb167eb90 (LWP 11771)] [KCrash handler] #6 0xb7c35af6 in KMFolderCachedImap::findByUID (this=0x82c1db0, uid=99) at /usr/src/debug/kdepim-4.1.0/kmail/kmfoldercachedimap.cpp:586 #7 0xb7c45337 in KMFolderCachedImap::slotGetMessagesData (this=0x82c1db0, job=0x8320f28, data=@0xbf8b5e04) at /usr/src/debug/kdepim-4.1.0/kmail/kmfoldercachedimap.cpp:1705 #8 0xb7c4bc5e in KMFolderCachedImap::qt_metacall (this=0x82c1db0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf8b5b88) at /usr/src/debug/kdepim-4.1.0/build/kmail/kmfoldercachedimap.moc:195 #9 0xb62d4d7a in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb62d52f2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb6b2d6b9 in KIO::TransferJob::data () from /usr/lib/libkio.so.5 #12 0xb6b2dff2 in KIO::TransferJob::slotData () from /usr/lib/libkio.so.5 #13 0xb6b35715 in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5 #14 0xb62d4d7a in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb62d52f2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb6bdea33 in KIO::SlaveInterface::data () from /usr/lib/libkio.so.5 #17 0xb6be14f4 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #18 0xb6bdf1c7 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #19 0xb6bd1e40 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5 #20 0xb6bd21b3 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5 #21 0xb62d4d7a in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #22 0xb62d52f2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #23 0xb6b03a27 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5 #24 0xb6b05453 in ?? () from /usr/lib/libkio.so.5 #25 0xb6b05aa6 in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5 #26 0xb62cfc9b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #27 0xb62d1841 in QObject::event () from /usr/lib/libQtCore.so.4 #28 0xb54b92ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #29 0xb54bf70e in QApplication::notify () from /usr/lib/libQtGui.so.4 #30 0xb68c0b0d in KApplication::notify () from /usr/lib/libkdeui.so.5 #31 0xb62c34a1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #32 0xb62c3d61 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #33 0xb62ec00a in QEventDispatcherUNIX::processEvents () from /usr/lib/libQtCore.so.4 #34 0xb55438e2 in ?? () from /usr/lib/libQtGui.so.4 #35 0xb62c1bfa in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #36 0xb62c1dba in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #37 0xb62c3fbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #38 0xb54b9167 in QApplication::exec () from /usr/lib/libQtGui.so.4 #39 0x0804a880 in main (argc=135454104, argv=0x812b118) at /usr/src/debug/kdepim-4.1.0/kmail/main.cpp:146 #0 0xffffe430 in __kernel_vsyscall () This bug still occures in version 1.10.90 (KDE 4.1.71). Please, fix some crashes of KMail, I reported a lot. *** Bug 169934 has been marked as a duplicate of this bug. *** I tried to refresh account as well as newly renamed folder immediately after rename but kmail 1.11.2 doesn't crash in any case. *** This bug has been marked as a duplicate of bug 180373 *** |