Version: (using KDE Devel) Installed from: Compiled sources OS: Linux When a thread contains two different messages with identical Message-ID's, any operation within the folder containing that thread results in a SIGSEGV. In addition, the thread containing the offending messages does not appear in the message list. The folder status also indicates an unread message which, of course, cannot be seen. Manually removing the unread dupe resolves the issue. Backtrace follows: (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)...[New Thread 1024 (LWP 7451)] (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)...0x4135b099 in wait4 () from /lib/libc.so.6 #0 0x4135b099 in wait4 () from /lib/libc.so.6 #1 0x413d5bd8 in __DTOR_END__ () from /lib/libc.so.6 #2 0x41233072 in waitpid () from /lib/libpthread.so.0 #3 0x40a430de in KCrash::defaultCrashHandler () from /opt/kde3/lib/libkdecore.so.4 #4 0x41230a74 in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x080d4923 in KDialog::marginHint () #7 0xbfffe858 in ?? () #8 0x080e0750 in KDialog::marginHint () #9 0x40d443c7 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #10 0x080fe533 in KDialog::marginHint () #11 0x080fba96 in KDialog::marginHint () #12 0x0818eb65 in KDialog::marginHint () #13 0x0818c862 in KDialog::marginHint () #14 0x080fbe9e in KDialog::marginHint () #15 0x080d8e1a in KDialog::marginHint () #16 0x080d5abc in KDialog::marginHint () #17 0x0808d0f5 in KDialog::marginHint () #18 0x0808676b in KDialog::marginHint () #19 0x40d443c7 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #20 0x40d44313 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0x40846df0 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4 #22 0x40839b62 in KAction::slotActivated () from /opt/kde3/lib/libkdeui.so.4 #23 0x40846ff2 in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 #24 0x40d44429 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #25 0x40d44313 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #26 0x40f81de3 in QButton::clicked () from /usr/lib/libqt-mt.so.3 #27 0x40da7546 in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #28 0x40d6d5c1 in QWidget::event () from /usr/lib/libqt-mt.so.3 #29 0x40d04ed6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #30 0x40d04836 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #31 0x409bba55 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #32 0x40cb05fc in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #33 0x40cadb78 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #34 0x40cacaec in QApplication::processNextEvent () from /usr/lib/libqt-mt.so.3 #35 0x40d06385 in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3 #36 0x40caca56 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #37 0x081a43b1 in KDialog::marginHint () #38 0x412d09ed in __libc_start_main () from /lib/libc.so.6 Scott
Packages are from pre-compiled SuSE RPM's.
Subject: Re: New: Duplicate Message-ID's in a thread cause SIGSEGV I often have dupes (only a couple of hours ago I had the last one) and KMail never crashed because of this. Moreover the backtrace you provided is completely useless since the precompiled binaries are missing all useful debug information. Unless you can compile KMail yourself and provide a meaningful backtrace I will have to close this bug report. Alternatively please provide a folder in mbox format which can be used to reproduce the problem.
The folder is about 5MB, so I can't upload it. I've put it up for download at http://scott.exti.net/files/51200folder.tar.bz2 . Let me know if you have any problems in getting it.
Ingo, Scott wasn't the only one. See the thread given on the url below for the massive amount of people that had all the same problem. http://lists.suse.com/archive/suse-linux-e/2002-Nov/3694.html It should be possible to find the root cause and to prevent the problem. I my case; kmail crashed if I deleted the message (though I don't know which one it actually was).
The problem seems to be caused by a message with these headers: Message-ID: <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> References: <D0BE8C2BA20FFD4983B66331766009F86AD893@letterman.3mts.com> <97c85d994b.john@xl-cambridge.com> <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> In-Reply-To: <20021123T205545.GAdc6e4.pat@wahoo.no-ip.org> User-Agent: Mutt/1.4i For some reason Message-ID == In-Reply-To. KMail probably doesn't handle this case (which should never happen) correctly.
Any guess on when this might be fixed?
Subject: Re: Duplicate Message-ID's in a thread cause SIGSEGV On Tuesday 26 November 2002 20:21, Scott Jones wrote: > Any guess on when this might be fixed? Not before KDE 3.1.1 (unless you use the cvs version).
*** Bug 51597 has been marked as a duplicate of this bug. ***
I am unable to reproduce problems with Message-ID == In-Reply-To with the current development version of kmail anymore. I'm closing this bug report, if it is still an issue with kmail 1.5.3 from kde 3.1.3 please reopen it.