Bug 117415

Summary: kontact crashed when searching by typing /svn
Product: [Unmaintained] kmail Reporter: Jos van den Oever <jos>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: arne.schmitz, envite, jeff.causey, kollix
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: the mail that can crash kmail

Description Jos van den Oever 2005-12-01 09:06:17 UTC
Version:           unknown (using KDE 3.4.2 Level "b" , SUSE 9.3 UNSUPPORTED)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.9-smp

In in an open Kontact mail window, select a mail. Then type '/svn' and Kontact will crash.

This a reproducable bug.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/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)
[Thread debugging using libthread_db enabled]
[New Thread 1105409760 (LWP 28941)]
(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)
[KCrash handler]
#7  0x087b38fd in ?? ()
#8  0x426edf43 in KMCommand::slotStart () from /opt/kde3/lib/libkmailprivate.so
#9  0x4272fbd4 in KMCommand::qt_invoke () from /opt/kde3/lib/libkmailprivate.so
#10 0x427304fb in KMShowMsgSrcCommand::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#11 0x410aa20e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x413fc182 in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x410c7763 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x410cf1b3 in QSingleShotTimer::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x41047a5f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x41049623 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x40d5dc81 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#18 0x4103c20c in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40ff4ff6 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x4105f9f1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x4105f836 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x410494ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x08063595 in ?? ()
#24 0xbfffe5e0 in ?? ()
#25 0x00000001 in ?? ()
#26 0x00000001 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000001 in ?? ()
#30 0x0806879c in typeinfo name for QPtrList<KParts::Part> ()
#31 0x00000000 in ?? ()
#32 0x08067971 in typeinfo name for QPtrList<KParts::Part> ()
#33 0x08067dc2 in typeinfo name for QPtrList<KParts::Part> ()
#34 0x08c777ef in ?? ()
#35 0x40f2b020 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x4000dbce in _dl_name_match_p () from /lib/ld-linux.so.2
#37 0x41602e80 in __libc_start_main () from /lib/tls/libc.so.6
#38 0x080583d1 in ?? ()
Comment 1 Thiago Macieira 2005-12-01 11:22:55 UTC
I cannot reproduce here, KMail 1.9 r477777.
Comment 2 Jos van den Oever 2005-12-01 12:07:37 UTC
The bug works in KMail and Kontact. I can only reproduce it on one email, in an Imap Trash folder, with the title:
SOURCEFORGE.NET UPDATE - 2005-11-30 EDITION

You have to type quickly to reproduce it.

Comment 3 Jos van den Oever 2005-12-01 12:08:22 UTC
Created attachment 13705 [details]
the mail that can crash kmail
Comment 4 Philip Rodrigues 2006-09-19 17:32:49 UTC
Jos, does this crash still occur for you with the KMail from KDE 3.5?
Comment 5 Jos van den Oever 2006-09-19 18:30:18 UTC
Yes, it happens in KMail (Kontact) from KDE 3.5.4 as packaged for SuSE 9.3.
Comment 6 Jos van den Oever 2006-09-19 18:31:16 UTC
Actually, I just tested on random mail and this caused the crash.
Comment 7 Thiago Macieira 2006-09-19 21:29:20 UTC
I still cannot reproduce the problem, r548000.
Comment 8 Thiago Macieira 2006-09-19 21:34:31 UTC
I reproduced this now. You mustn't be viewing the last message in a folder, as N would do nothing in that case.
Comment 9 Allen Winter 2006-09-19 22:26:47 UTC
I can reproduce as well.

The backtrace (below) shows a crash in the KMFolder storage stuff.  We have tons of those types of crashes.  kling is working on fixing these types of crashes, or we could do the old 'if(mStorage)..." trick.

[KCrash handler]
#6  0x0781b379 in KMFolder::open (this=)
    at /data/kde/branches/KDE/3.5/kdepim/kmail/kmfolder.cpp:473
#7  0x0796e0f0 in KMCommand::keepFolderOpen (this=)
    at /data/kde/branches/KDE/3.5/kdepim/kmail/kmcommands.cpp:442
#8  0x0796e2be in KMCommand::slotStart (this=)
    at /data/kde/branches/KDE/3.5/kdepim/kmail/kmcommands.cpp:244
#9  0x0796e756 in KMCommand::qt_invoke (this=)
    at /data/kde/branches/KDE/3.5/kdepim/kmail/kmcommands.moc:147
#10 0x0796ef0f in KMShowMsgSrcCommand::qt_invoke (this=)
    at /data/kde/branches/KDE/3.5/kdepim/kmail/kmcommands.moc:976
#11 0x05cb9c34 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x060332a6 in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#13 0x05cd7143 in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0x05cdf9f7 in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x05c544ed in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x05c54e3c in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x0028b211 in KApplication::notify () from /usr/lib/libkdecore.so.4
#18 0x05c48db9 in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x05bfd024 in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x05c6cb5b in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x05c6ca66 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x05c53eb9 in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x0805ae17 in main (argc=1, argv=0xbfe9ad74)
    at /data/kde/branches/KDE/3.5/kdepim/kontact/src/main.cpp:161
Comment 10 Allen Winter 2006-09-20 04:17:18 UTC
Note that I tried the 'if(mStorage)...' trick but it doesn't really help.

The crash just moves farther downstream.  There really needs to be a re-design to make these types of crashes go away.
Comment 11 Christophe Marin 2008-08-05 13:50:44 UTC
*** Bug 129429 has been marked as a duplicate of this bug. ***
Comment 12 Christophe Marin 2008-08-05 13:51:47 UTC
*** Bug 164698 has been marked as a duplicate of this bug. ***
Comment 13 Christophe Marin 2008-10-18 11:42:15 UTC
*** Bug 173084 has been marked as a duplicate of this bug. ***
Comment 14 Martin Koller 2009-08-28 00:02:50 UTC
can not reproduce with KDE from 4.4 trunk.
Anybody ?
Comment 15 Myriam Schweingruber 2012-08-19 11:00:19 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding