crash while search messages

Bug #196926 reported by LimCore
4
Affects Status Importance Assigned to Milestone
KDE PIM
Unknown
High
kdepim (Ubuntu)
Invalid
Low
Unassigned

Bug Description

crash while searching messages.
I have both pop3 and imap account (and search was in both of them... I would guess crash was while searching imap.. or not)

ubuntu 7.10 amd64 4:3.5.7enterpr

or was the bug when search was done and program was about to show results?

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46945417149344 (LWP 1728)]
[New Thread 1107310928 (LWP 1732)]
[New Thread 1098918224 (LWP 1731)]
[New Thread 1090525520 (LWP 1730)]
[New Thread 1082132816 (LWP 1729)]
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5 0x00002ab249761b3e in KMMessage::codec () from /usr/lib/libkmailprivate.so
#6 0x00002ab249761c7b in KMMessage::bodyToUnicode ()
   from /usr/lib/libkmailprivate.so
#7 0x00002ab24986c693 in KMSearchRuleString::matches ()
   from /usr/lib/libkmailprivate.so
#8 0x00002ab24986857a in KMSearchPattern::matches ()
   from /usr/lib/libkmailprivate.so
#9 0x00002ab249868720 in KMSearchPattern::matches ()
   from /usr/lib/libkmailprivate.so
#10 0x00002ab24982dcdf in FolderStorage::slotProcessNextSearchBatch ()
   from /usr/lib/libkmailprivate.so
#11 0x00002ab24997be34 in KMSearch::slotProcessNextBatch ()
   from /usr/lib/libkmailprivate.so
#12 0x00002ab24997beee in KMSearch::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#13 0x00002ab25061ad76 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002ab25061b910 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#15 0x00002ab25098a9a2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#16 0x00002ab250641257 in QTimer::event () from /usr/lib/libqt-mt.so.3
#17 0x00002ab2505b62a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#18 0x00002ab2505b8031 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#19 0x00002ab24f226308 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#20 0x00002ab250548d12 in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#21 0x00002ab2505a955c in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#22 0x00002ab25055d443 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#23 0x00002ab2505cf7e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#24 0x00002ab2505cf5ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#25 0x00002ab2505b7d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#26 0x0000000000402eb4 in ?? ()
#27 0x00002ab254327b44 in __libc_start_main () from /lib/libc.so.6
#28 0x0000000000402c29 in ?? ()
#29 0x00007fff617e91b8 in ?? ()
#30 0x0000000000000000 in ?? ()

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thanks for submitting this report.

I am not sure why this was submitted against kdepim. It looks like you talk about an e-mail client. Which e-mail client does this report refer to?

Could you also list all the steps necessary to reproduce this problem.

Thanks

Changed in kdepim:
assignee: nobody → txwikinger
status: New → Incomplete
Revision history for this message
LimCore (limcore) wrote :

it's a kmail problem.

Revision history for this message
LimCore (limcore) wrote :

I can confirm:

ubuntu 7.10 amd64 kmail ii kmail 4:3.5.7enterpr

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[...]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47661926755232 (LWP 2890)]
[New Thread 1107310928 (LWP 2895)]
[New Thread 1098918224 (LWP 2894)]
[New Thread 1090525520 (LWP 2893)]
[New Thread 1082132816 (LWP 2891)]
(no debugging symbols found)
[...]
(no debugging symbols found)
[KCrash handler]
#5 0x00002b591cc30b3e in KMMessage::codec () from /usr/lib/libkmailprivate.so
#6 0x00002b591cc30c7b in KMMessage::bodyToUnicode ()
   from /usr/lib/libkmailprivate.so
#7 0x00002b591cd3b693 in KMSearchRuleString::matches ()
   from /usr/lib/libkmailprivate.so
#8 0x00002b591cd3750f in KMSearchPattern::matches ()
   from /usr/lib/libkmailprivate.so
#9 0x00002b591cd37720 in KMSearchPattern::matches ()
   from /usr/lib/libkmailprivate.so
#10 0x00002b591ccfccdf in FolderStorage::slotProcessNextSearchBatch ()
   from /usr/lib/libkmailprivate.so
#11 0x00002b591ce4ae34 in KMSearch::slotProcessNextBatch ()
   from /usr/lib/libkmailprivate.so
#12 0x00002b591ce4aeee in KMSearch::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#13 0x00002b5923ae9d76 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002b5923aea910 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#15 0x00002b5923e599a2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#16 0x00002b5923b10257 in QTimer::event () from /usr/lib/libqt-mt.so.3
#17 0x00002b5923a852a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#18 0x00002b5923a87031 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#19 0x00002b59226f5308 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#20 0x00002b5923a17d12 in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#21 0x00002b5923a7855c in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#22 0x00002b5923a2c443 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#23 0x00002b5923a9e7e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#24 0x00002b5923a9e5ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#25 0x00002b5923a86d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#26 0x0000000000402eb4 in ?? ()
#27 0x00002b59277f6b44 in __libc_start_main () from /lib/libc.so.6
#28 0x0000000000402c29 in ?? ()
#29 0x00007fff8e317998 in ?? ()
#30 0x0000000000000000 in ?? ()

While doing a serach on local folders (on all local folders, doing search only on say Inbox/ is ok)

Changed in kdepim:
status: Incomplete → Confirmed
Revision history for this message
LimCore (limcore) wrote :

perhaps this may help:

Program exited normally.
(gdb) kmail: WARNING: FolderStorage::getMsg, message has no sernum, index: 1
*** KMail got signal 11 (Crashing)
KCrash: Application 'kmail' crashing...

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thanks for your information.

According to our procedures, reports should not be confirmed by the reporter.

Changed in kdepim:
status: Confirmed → Incomplete
Revision history for this message
Ralph Janke (txwikinger) wrote :

Confirmed report since there is an independent report submitted in the KDE bugtracker.

Changed in kdepim:
status: Incomplete → Confirmed
importance: Undecided → Medium
Ralph Janke (txwikinger)
Changed in kdepim:
assignee: txwikinger → nobody
Changed in kdepim:
status: Unknown → New
Revision history for this message
LimCore (limcore) wrote :
Download full text (6.9 KiB)

And again, this time crashes always, when I search messages (S) with condition that <body> contains given text (say "illusion")

gdb krafal@desktop:~$ gdb kmail
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) r
Starting program: /usr/bin/kmail
[Thread debugging using libthread_db enabled]
[New Thread 47196055366560 (LWP 27920)]
kmail: WARNING: Can not find parent folder
WeaverThreadLogger: thread (ID: 1) suspended.
WeaverThreadLogger: thread (ID: 2) suspended.
WeaverThreadLogger: thread (ID: 3) suspended.
WeaverThreadLogger: thread (ID: 4) suspended.
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa20a00 ): KAccel object already contains an action name "move_message_to_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa20a00 ): KAccel object already contains an action name "copy_message_to_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa20a00 ): KAccel object already contains an action name "jump_to_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa20a00 ): KAccel object already contains an action name "jump_to_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa20a00 ): KAccel object already contains an action name "cancel"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0xa20a00 ): KAccel object ...

Read more...

Changed in kdepim:
status: New → Invalid
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

The upstream report says that these are not the same bug. Is this crash still reproducible in Intrepid? If so what version of KDE/KMail are you currently using?

Changed in kdepim:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdepim:
importance: Medium → Low
status: Incomplete → Invalid
Changed in kdepim:
status: Invalid → Unknown
Changed in kdepim:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.