| Summary: | Kmail crashes when highlighting multiple messages (4+), and apply filters. | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Dan Vande More <dvm> |
| Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 1.6 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Dan Vande More
2004-02-10 03:08:23 UTC
Could you try leaving out the final catch all move, and see if that makes a difference, please? Alternatively could you mail me directly the filter portion of your kmailrc file so I can try to match your filter? I'm unable to reproduce the crash here. Same problem here..I think :) My version info: Version: 1.6 (using KDE 3.2.0) Installed from: Gentoo Packages Compiler: gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7) OS: Linux I have a mailing list account I hadn't checked since rebuilding a box of mine. Downloaded about 3,500+ messages into one main folder. Added one or 2 filters at a time (mailing lists: bsd, nanog, bugtraq, php, etc..) and then would CTRL-A and CTRL-J. The first one ran fine, although slow, and then the filters for NANOG and PHP were added and then when I ran it it froze hard. After 5 minutes did a killall kmail and restarted. Did another CTRL-A and CTRL-J and this time crashed. Rinse and repeat 2 more times and on the last try it just deleted the whole 3,500 or so messages that were left. *POOF* . Not a big deal, but would have been if the mail was 'important' :) I am also getting random crashes even when not around, probably on auto-check. I do have TLS and PLAIN login turned on, but pipelining is off. Let me know if there is anymore info I can get for you guys/gals. Thanks! Confirmation: Kmail crashes whenever I "apply filters" on one or more messages marked, that belong to a thread (not with plain messages) - crash report below. When I restart kmail then, no threads are displayed anymore in the corresponding folder (don't know if I can reactivate a threaded view!). Regards Raga Eine korrekte Rückverfolgung ist nicht möglich. Wahrscheinlich sind die Dateien Ihres Systems in einer Weise erstellt worden, die eine solche Rückverfolgung (Backtrace) nicht erlaubt. Oder der so genannte "Stack Frame" für das Programm wurde durch den Absturz unbrauchbar gemacht. (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 16198)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x41b82be8 in waitpid () from /lib/libpthread.so.0 #0 0x41b82be8 in waitpid () from /lib/libpthread.so.0 #1 0x413d2b78 in ?? () from /usr/lib/libkdecore.so.4 #2 0x41301e20 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #3 0x41b81825 in __pthread_sighandler () from /lib/libpthread.so.0 #4 <signal handler called> #5 0x401d3b61 in KMHeaderItem::irefresh () from /usr/lib/libkmailprivate.so.0 #6 0x401cb6d8 in KMHeaders::highlightMessage () from /usr/lib/libkmailprivate.so.0 #7 0x401cc62c in KMHeaders::highlightMessage () from /usr/lib/libkmailprivate.so.0 #8 0x401d2a18 in KMHeaders::qt_invoke () from /usr/lib/libkmailprivate.so.0 #9 0x416d2d16 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #10 0x41a0238d in QListView::currentChanged () from /usr/lib/libqt-mt.so.3 #11 0x417b5ba5 in QListView::setCurrentItem () from /usr/lib/libqt-mt.so.3 #12 0x401c9744 in KMHeaders::applyFiltersOnMsg () from /usr/lib/libkmailprivate.so.0 #13 0x4033c55a in KMMainWidget::slotApplyFilters () from /usr/lib/libkmailprivate.so.0 #14 0x40334aa9 in KMMainWidget::qt_invoke () from /usr/lib/libkmailprivate.so.0 #15 0x416d2d9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #16 0x416d2bd4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #17 0x4104691b in KAction::activated () from /usr/lib/libkdeui.so.4 #18 0x410462ff in KAction::slotActivated () from /usr/lib/libkdeui.so.4 #19 0x41046b21 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4 #20 0x416d2d9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0x419f02ea in QSignal::signal () from /usr/lib/libqt-mt.so.3 #22 0x416ec866 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #23 0x417d3b20 in QPopupMenu::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #24 0x41707da7 in QWidget::event () from /usr/lib/libqt-mt.so.3 #25 0x4167747f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #26 0x41676b81 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #27 0x4127db29 in KApplication::notify () from /usr/lib/libkdecore.so.4 #28 0x4160eee1 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #29 0x4160ce12 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #30 0x41622f01 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #31 0x4168ace8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #32 0x41677731 in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3 #33 0x417d6693 in QPopupMenu::exec () from /usr/lib/libqt-mt.so.3 #34 0x401cc9fa in KMHeaders::slotRMB () from /usr/lib/libkmailprivate.so.0 #35 0x401cbb8f in KMHeaders::rightButtonPressed () from /usr/lib/libkmailprivate.so.0 #36 0x401d2cbc in KMHeaders::qt_invoke () from /usr/lib/libkmailprivate.so.0 #37 0x416d2d9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #38 0x41a02fa5 in QListView::contextMenuRequested () from /usr/lib/libqt-mt.so.3 #39 0x417b286e in QListView::contentsContextMenuEvent () from /usr/lib/libqt-mt.so.3 #40 0x417e2159 in QScrollView::viewportContextMenuEvent () from /usr/lib/libqt-mt.so.3 #41 0x417e16e0 in QScrollView::eventFilter () from /usr/lib/libqt-mt.so.3 #42 0x417b1448 in QListView::eventFilter () from /usr/lib/libqt-mt.so.3 #43 0x401c490f in KMHeaders::eventFilter () from /usr/lib/libkmailprivate.so.0 #44 0x416d092e in QObject::activate_filters () from /usr/lib/libqt-mt.so.3 #45 0x416d085c in QObject::event () from /usr/lib/libqt-mt.so.3 #46 0x41707d1f in QWidget::event () from /usr/lib/libqt-mt.so.3 #47 0x4167747f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #48 0x416770e1 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #49 0x4127db29 in KApplication::notify () from /usr/lib/libkdecore.so.4 #50 0x4160f2ca in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #51 0x4160ce12 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #52 0x41622f01 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #53 0x4168ace8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #54 0x4168ab98 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #55 0x416776d1 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #56 0x0804a457 in ?? () #57 0xbffffa30 in ?? () #58 0xbffff930 in ?? () #59 0x00000000 in ?? () #60 0x00000000 in ?? () #61 0x41af4fc0 in vtable for QGArray () from /usr/lib/libqt-mt.so.3 #62 0x080c2840 in ?? () #63 0x413a0676 in malloc () from /usr/lib/libkdecore.so.4 #64 0x41dabdc6 in __libc_start_main () from /lib/libc.so.6 #65 0x0804a181 in ?? () After crashing, the messages in the corresponding folder won't show as threads again but each message is presented one by one. In other folders, threads display as groups. I don't have a clue how to reactivate the grouping of messages - should I open another bug? ad comment #4: you can reactivate the grouping by choosing "show grouped" in the "folder" menu! This entry should also occur in the context menu of each folder. It could also be moved to the View menu. A global switch is desirable... I'm going to merge you to the central bugreport about this. We believe this ptoblem is fixed in the development version of KMail. If you have the possibility it would be nice if you could compile this version (CVS/HEAD) and see if the problem is solved. Please respond to bug 73999 if you can reproduce this bug then. Thanks for reporting! *** This bug has been marked as a duplicate of 73999 *** |