Bug 131032 - KMail Crashes Frequently
Summary: KMail Crashes Frequently
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-18 17:01 UTC by Bipin
Modified: 2008-06-17 18:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bipin 2006-07-18 17:01:19 UTC
Version:           1.9.1 (using KDE 3.5.3, Debian Package 4:3.5.3-1 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-1-686

Hi,

I am not sure, if this has already been brought to your notice. But this seems to be increasing day by day. Please check this. This is a fantastic peice of application, never had issues with earlier versions of KMAIL.

(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)
(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 -1248732960 (LWP 28194)]
[New Thread -1277977680 (LWP 28198)]
[New Thread -1269589072 (LWP 28197)]
[New Thread -1261200464 (LWP 28196)]
[New Thread -1252811856 (LWP 28195)]
(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)
(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]
#5  0xb78b57c7 in raise () from /lib/tls/libc.so.6
#6  0xb78b706b in abort () from /lib/tls/libc.so.6
#7  0xb78ec545 in __fsetlocking () from /lib/tls/libc.so.6
#8  0xb78f2b97 in malloc_usable_size () from /lib/tls/libc.so.6
#9  0xb78f3032 in free () from /lib/tls/libc.so.6
#10 0xb593b1a2 in gpgme_err_make_from_errno () from /usr/lib/libgpgme.so.11
#11 0xb593e8ac in gpgme_err_make_from_errno () from /usr/lib/libgpgme.so.11
#12 0xb593e182 in gpgme_err_make_from_errno () from /usr/lib/libgpgme.so.11
#13 0xb59369af in gpgme_set_engine_info () from /usr/lib/libgpgme.so.11
#14 0xb59369e6 in gpgme_set_engine_info () from /usr/lib/libgpgme.so.11
#15 0xb5937d7f in gpgme_set_engine_info () from /usr/lib/libgpgme.so.11
#16 0xb59328a9 in gpgme_op_card_edit () from /usr/lib/libgpgme.so.11
#17 0xb592b62a in gpgme_wait () from /usr/lib/libgpgme.so.11
#18 0xb592f9fb in gpgme_op_keylist_ext_start () from /usr/lib/libgpgme.so.11
#19 0xb5953279 in GpgME::Context::startKeyListing ()
   from /usr/lib/libgpgme++.so.0
#20 0xb643f703 in Kleo::QGpgMEKeyListJob::attemptSyncKeyListing ()
   from /usr/lib/libkleopatra.so.1
#21 0xb6446aad in Kleo::QGpgMEKeyListJob::exec ()
   from /usr/lib/libkleopatra.so.1
#22 0xb7ebfdac in Kleo::KeyResolver::lookup ()
   from /usr/lib/libkmailprivate.so
#23 0xb7ec02d6 in Kleo::KeyResolver::getEncryptionKeys ()
   from /usr/lib/libkmailprivate.so
#24 0xb7ec0901 in Kleo::KeyResolver::EncryptionPreferenceCounter::operator()
    () from /usr/lib/libkmailprivate.so
#25 0xb7ec9ef2 in std::for_each<__gnu_cxx::__normal_iterator<Kleo::KeyResolver::Item*, std::vector<Kleo::KeyResolver::Item, std::allocator<Kleo::KeyResolver::Item> > >, Kleo::KeyResolver::EncryptionPreferenceCounter> ()
   from /usr/lib/libkmailprivate.so
#26 0xb7ec0af2 in Kleo::KeyResolver::checkEncryptionPreferences ()
   from /usr/lib/libkmailprivate.so
#27 0xb7eaf777 in MessageComposer::determineWhetherToEncrypt ()
   from /usr/lib/libkmailprivate.so
#28 0xb7eb1588 in MessageComposer::adjustCryptFlags ()
   from /usr/lib/libkmailprivate.so
#29 0xb7eba5f0 in AdjustCryptFlagsJob::execute ()
   from /usr/lib/libkmailprivate.so
#30 0xb7eadef5 in MessageComposer::slotDoNextJob ()
   from /usr/lib/libkmailprivate.so
#31 0xb7eadf32 in MessageComposer::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#32 0xb73ac54b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#33 0xb773e1a9 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#34 0xb73c9c4c in QSignal::activate () from /usr/lib/libqt-mt.so.3
#35 0xb73d1710 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#36 0xb734287a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#37 0xb7342a76 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#38 0xb6ff624e in KApplication::notify () from /usr/lib/libkdecore.so.4
#39 0xb72d4001 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#40 0xb7334305 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#41 0xb72e7d2a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#42 0xb735b255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#43 0xb735b17a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#44 0xb734138d in QApplication::exec () from /usr/lib/libqt-mt.so.3
#45 0x0804a098 in ?? ()
#46 0xbfaf6088 in ?? ()
#47 0xbfaf6274 in ?? ()
#48 0x00000000 in ?? ()
Comment 1 Dave Rowe 2006-07-18 17:19:40 UTC
Can you provide additional details to give some background on the crash?  For instance, what were you doing when the crash occured?  From the looks of the BT, you have GPG enabled, is this correct?  What type of mail were you sending?  Was it to be signed / encrypted / both?
Comment 2 Dave Rowe 2006-07-18 17:20:47 UTC
Caps Lock won't get additional attention.
Comment 3 Bipin 2006-07-18 18:59:55 UTC
I am sorry, my intention was not that. Actually I did not pay much notice to it. Sorry again
Comment 4 Bipin 2006-07-18 19:05:33 UTC
I don't use GnuPG and neither was that mail supposed to be signed or encrypted. The mail was compossed in HTML format, and was also not a reply. The mail had about 9 recepients as such, that would be it as per the mail. Please let me know what more info you guys would need.
Comment 5 Philip Rodrigues 2006-07-18 23:05:23 UTC
Can you describe exactly when KMail crashed? When you were typing the message, or when you clicked on send, or...?
Comment 6 Bipin 2006-07-18 23:08:42 UTC
The crash was when I hit the 'send' button.
Comment 7 Philip Rodrigues 2006-09-06 13:41:20 UTC
The crash seems to be well within the gpgme code, so you might want to twiddle your signing/encryption settings
Comment 8 Bipin 2006-09-06 16:12:59 UTC
Looks like by default both the OpenPGP (gpg) and S/MIME (gpgsm) were checked. I have no clue on how to tweak it. Have unchecked both these options. Let me monitor with these setting and report back to you guys.
Comment 9 Philip Rodrigues 2006-09-20 11:45:43 UTC
Bipin, what results with the changed settings?
Comment 10 Bipin 2006-09-21 05:13:50 UTC
Philip,

It was not happening for a while, but then two days back it again crashed and when I ran the backtrace I saw some reference to gpgsm. Unfortunately I could not save to upload here. If this happens again I would definitely update you guys. Thanks for following up.
Comment 11 A. Spehr 2008-06-12 21:27:08 UTC
Does that mean it hasn't happened again and this report can be closed? 
Thanks!
Comment 12 Bipin 2008-06-13 11:43:37 UTC
:-)
I moved from using Kmail to other apps and later settled for Mutt. If no one has even reported this problem, then in my opinion we should close this one.
Comment 13 Thomas McGuire 2008-06-17 18:39:14 UTC
Closing as WORKSFORME, probably fixed in newer versions.