Version: 1.9.5 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-3 (4.0)) Compiler: Target: x86_64-linux-gnu OS: Linux (x86_64) release 2.6.18.2 Initially I tryed searching all folders for a specific From: entry, but accidently selected the blank field (where I could have selected From:) and added a email address to the right. note: I have a lot of emails, but I don't think the search went very far though them all. To repeat: start Kontact (and so Kmail) click search button (Find Messages) click folder icon next to "Search only in:" and change to "Local Folders" (at top) Select "Match all of the following" (was default) Change Match drop down from "Subject" to blank Add an email address as search parameter (but probably anything would do) When I clicking [Search] I got (eventualy) this backtrace bellow. I tryed twice in a row, and got same result. I suspect many more configurations would trigger crash, but I have not tryed more. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47187025365664 (LWP 13452)] [New Thread 1107310944 (LWP 13616)] [New Thread 1098918240 (LWP 13615)] [New Thread 1090525536 (LWP 13614)] [New Thread 1082132832 (LWP 13613)] [KCrash handler] #5 KMail::SearchWindow::slotAddMsg (this=0xea59e0, idx=1183) at /build/buildd/kdepim-3.5.5.dfsg.1/./kmail/kmmsgbase.h:146 #6 0x00002aea988a6a78 in KMail::SearchWindow::qt_invoke (this=0xea59e0, _id=111, _o=0x7fff1af38d10) at ./searchwindow.moc:199 #7 0x00002aea91924ca3 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #8 0x00002aea91925563 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x00002aea988087db in FolderStorage::emitMsgAddedSignals (this=0x10258f0, idx=1183) at /build/buildd/kdepim-3.5.5.dfsg.1/./kmail/folderstorage.cpp:275 #10 0x00002aea9880897e in KMFolderSearch::addSerNum (this=0x10258f0, serNum=0) at /build/buildd/kdepim-3.5.5.dfsg.1/./kmail/kmfoldersearch.cpp:457 #11 0x00002aea9889d71d in KMFolderSearch::qt_invoke (this=0x10258f0, _id=17, _o=0x7fff1af38ed0) at ./kmfoldersearch.moc:293 #12 0x00002aea91924b7a in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #13 0x00002aea986e500c in KMSearch::found (this=<value optimized out>, t0=0) at ./kmfoldersearch.moc:114 #14 0x00002aea98758bd2 in KMSearch::slotSearchFolderResult (this=0x14c3f60, folder=0x9f3970, serNums=@0x7fff1af38fa0, pattern=<value optimized out>, complete=false) at /build/buildd/kdepim-3.5.5.dfsg.1/./kmail/kmfoldersearch.cpp:276 #15 0x00002aea98758f7a in KMSearch::qt_invoke (this=0x14c3f60, _id=4, _o=0x7fff1af39060) at ./kmfoldersearch.moc:128 #16 0x00002aea91924b7a in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #17 0x00002aea986e9396 in FolderStorage::searchResult ( this=<value optimized out>, t0=<value optimized out>, t1=@0x7fff1af39160, t2=0x148b720, t3=false) at ./folderstorage.moc:431 #18 0x00002aea98807f66 in FolderStorage::slotProcessNextSearchBatch ( this=0x9f3d70) at /build/buildd/kdepim-3.5.5.dfsg.1/./kmail/folderstorage.cpp:1095 #19 0x00002aea98808090 in FolderStorage::qt_invoke (this=0x9f3d70, _id=7, _o=0x7fff1af392c0) at ./folderstorage.moc:458 #20 0x00002aea9880816d in KMFolderIndex::qt_invoke (this=0x9f3d70, _id=7, _o=0x7fff1af392c0) at ./kmfolderindex.moc:87 #21 0x00002aea98808189 in KMFolderMaildir::qt_invoke (this=0x9bc640, _id=7744, _o=0x52b018) at ./kmfoldermaildir.moc:77 #22 0x00002aea91924b7a in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #23 0x00002aea91c91edc in QSignal::signal () from /usr/lib/libqt-mt.so.3 #24 0x00002aea91943c4b in QSignal::activate () from /usr/lib/libqt-mt.so.3 #25 0x00002aea9194ac0a in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #26 0x00002aea918c0212 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #27 0x00002aea918c1fbc in QApplication::notify () from /usr/lib/libqt-mt.so.3 #28 0x00002aea9121a8de in KApplication::notify (this=0x7fff1af39b90, receiver=0x664670, event=0x7fff1af397b0) at /build/buildd/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550 #29 0x00002aea918537b2 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #30 0x00002aea918b352c in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #31 0x00002aea91867534 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #32 0x00002aea918d979e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #33 0x00002aea918d95a7 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #34 0x00002aea918c1cf0 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #35 0x000000000041730b in main (argc=<value optimized out>, argv=0x7fff1af39f88) at /build/buildd/kdepim-3.5.5.dfsg.1/./kontact/src/main.cpp:161 #36 0x00002aea90e184ca in __libc_start_main () from /lib/libc.so.6 #37 0x0000000000414b3a in _start () at ../sysdeps/x86_64/elf/start.S:113
*** Bug 126686 has been marked as a duplicate of this bug. ***
*** Bug 137841 has been marked as a duplicate of this bug. ***
Does anyone still see this crash in 3.5.6?
is 3.5.6 still to reach etch before release ? or will it stay in unstable (where I assume 3.5.6 currently is) ? I'm asking as I don't really want to run anything unstable, but if needed I will upgrade. Ernest ter Kuile.
*** Bug 158136 has been marked as a duplicate of this bug. ***
*** Bug 165477 has been marked as a duplicate of this bug. ***
This appears to happen only on 64 bit systems, as the reporter and all duplicates seem to have a 64 bit machine.
I just can't find anyone who has this crash anymore with the version coming in KDE 4.1. I even found a person using a 64bit PPC processor, and they couldn't make it crash when searching. I'd like to close. Is anyone still having this problem?
As the reporter, I don't mind if you close it, but I can't confirm anything is resolved since I don't have yet KDE 4.1 running (and won't until it appears in Debian test)
I'm using the openSUSE BuildService repository (http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.0/) and the searching works well approximately from the last week. My current environment is: Qt: 4.4.0 KDE: 4.00.85 (KDE 4.0.85 (KDE 4.1 >= 20080703) "release 3.3" Kontact: 1.3 openSUSE 11 64-bit
I sadly experience this bug with KDE4.1 rc1, Kubuntu Hardy x86, with latest updates installed. Just tried to connect to Google Mail via IMAP, and I reproducably get this message (yes my folders are large, but that's what GMail is for;): "Error while retrieving messages. The process for the imaps://imap.gmail.com protocol died unexpectedly." Crashdump: Unexpected Program Termination Unexpected Program Termination The program on your computer which provides access to the imaps://imap.gmail.com protocol has unexpectedly terminated. Details of the request: URL: (unknown) Date and time: Thursday 24 July 2008 21:10 Additional information: imaps://imap.gmail.com Possible causes: This is most likely to be caused by a bug in the program. Please consider submitting a full bug report as detailed below. Possible solutions: Update your software to the latest version. Your distribution should provide tools to update your software. When all else fails, please consider helping the KDE team or the third party maintainer of this software by submitting a high quality bug report. If the software is provided by a third party, please contact them directly. Otherwise, first look to see if the same bug has been submitted by someone else by searching at the KDE bug reporting website. If not, take note of the details given above, and include them in your bug report, along with as many other details as you think might help.
It successfully downloaded exactly 2472 messages (of 21046 in total, since 2005). Moving, deleting and viewing works, albeit a bit slowly.
What's about KDE 4.3?
Closing, this report is no longer relevant in recent kdepim versions where searching is done by querying the Nepomuk database.