| Summary: | Non-MIME-GnuPG encrypted messages often crash KMail | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | micu <micuintus> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | emilsedgh, micuintus, montel, plautrba, sknauss, swapon |
| Priority: | NOR | Keywords: | triaged |
| Version: | 4.8.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
micu
2012-04-03 22:00:36 UTC
Created attachment 70648 [details]
New crash information added by DrKonqi
kmail (4.9 pre) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.1
- What I was doing when the application crashed:
Clicked on an encrypted message. Dialog opened up asking for my password, when I entered it, kmail crashed.
-- Backtrace (Reduced):
#6 0x00007f1f1225c4f4 in KMime::Content::parent (this=0x8804470) at /home/emilsedgh/kde/sc/kdepimlibs/kmime/kmime_content.cpp:949
#7 0x00007f1f0b873a45 in MessageCore::NodeHelper::nextSibling (node=0x8804470) at /home/emilsedgh/kde/sc/kdepim/messagecore/nodehelper.cpp:32
#8 0x00007f1f08b677c7 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff00971740, node=0x8804470) at /home/emilsedgh/kde/sc/kdepim/messageviewer/objecttreeparser.cpp:296
#9 0x00007f1f08b9bcaf in MessageViewer::ViewerPrivate::parseContent (this=0x1f59640, content=0x8804470) at /home/emilsedgh/kde/sc/kdepim/messageviewer/viewer_p.cpp:952
#10 0x00007f1f08b9e434 in MessageViewer::ViewerPrivate::displayMessage (this=0x1f59640) at /home/emilsedgh/kde/sc/kdepim/messageviewer/viewer_p.cpp:824
Ok I need to configure kmail to open a dialogbox to decrypt it.... Don't know how to do it... Perhaps you have some infos about it. Yes for the moment I didn't test crypto + kmail. Hi Laurent. Should I describe a KMail feature to KMail's maintainer? :p Well, I've setup gpg keys using KGPG/Kleopatra. Then someone sent me an encrypted message. I think you can even setup a gpg key and then send an encrypted email to yourself. "Should I describe a KMail feature to KMail's maintainer? :p" yes :) Thanks will look at it soon. I never really test crypto feature so it's the time to test/debug it :) Laurent you probably don't have gpg-agent running, then KMail behaves a bit ugly and does not open a dialogbox to decrypt it. Start it on the command line: eval $(gpg-agent --daemon) before starting Kontact. This should be autostarted by your distribution. I've just tested with an inline openpgp (Content-Type text/Plain, Content-Disposition iniline) mail sent by kontact and could not reproduce this. (Found another bug though that the mail is decrypted without explicitly clicking on decrypt -> privacy leak) :( Could someone please send me a message that whould crash for him to aheinecke@intevation.de My Key fingerprint = B248 32EB D9AA DA17 15D2 A2E5 5DE9 385C C978 22F5 Created attachment 70873 [details]
New crash information added by DrKonqi
kmail (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1
- What I was doing when the application crashed:
Just clicked on the mail. KMail crashes (does not depent on entering the correct passphrase)
-- Backtrace (Reduced):
#6 0x0000003c1ea43eb4 in KMime::Content::parent() const () from /usr/lib64/libkmime.so.4
#7 0x0000003c226354e5 in MessageCore::NodeHelper::nextSibling (node=0x57e5c70) at /usr/src/debug/kdepim-4.8.2/messagecore/nodehelper.cpp:32
#8 0x0000003c22e862d9 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff62397270, node=0x57e5c70) at /usr/src/debug/kdepim-4.8.2/messageviewer/objecttreeparser.cpp:296
#9 0x0000003c22eb796f in MessageViewer::ViewerPrivate::parseContent (this=0x1b1c960, content=0x57e5c70) at /usr/src/debug/kdepim-4.8.2/messageviewer/viewer_p.cpp:866
#10 0x0000003c22eba3fa in MessageViewer::ViewerPrivate::displayMessage (this=0x1b1c960) at /usr/src/debug/kdepim-4.8.2/messageviewer/viewer_p.cpp:738
Created attachment 74260 [details]
New crash information added by DrKonqi
kmail (4.9.1) on KDE Platform 4.9.1 using Qt 4.8.3
- What I was doing when the application crashed:
Clicked on an encrypted message. Dialog opened up asking for my password, when I entered it, kmail crashed.
-- Backtrace (Reduced):
#5 0x0000003b55c43ee4 in KMime::Content::parent() const () from /lib64/libkmime.so.4
#6 0x0000003b62e2c386 in MessageCore::NodeHelper::nextSibling(KMime::Content const*) () from /lib64/libmessagecore.so.4
#7 0x0000003b63e8cdd4 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*) () from /lib64/libmessageviewer.so.4
#8 0x0000003b63ec21b0 in MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from /lib64/libmessageviewer.so.4
#9 0x0000003b63ec3a7c in MessageViewer::ViewerPrivate::displayMessage() () from /lib64/libmessageviewer.so.4
Created attachment 75603 [details] New crash information added by DrKonqi kmail (4.9.3) on KDE Platform 4.9.3 using Qt 4.8.4 - What I was doing when the application crashed: tried to decrypt a non-mime GnuPG message -----BEGIN PGP MESSAGE----- Charset: ISO-8859-1 Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org hQQOAzdCI0LImZTFEA/+PP6cGT7gDgBI19R12D1rGA/Md1xvRkBfumttAz7gN1l1 qz3pqeT3qfQkKhDd4co6ldIt68zpjnN4282rltzy73VQF/Hn7/i6/0FV7h2Z65DP 4QeSE2i3pDfk5nEGKzvUUlwo6JgYkbt92tCG5TTnJDy92xF5B+1udgKa5/a5Raqg 6Cw3zrjqOU+mS2sK+5hTJ+yoXsA4wvnGHIZ7MN7KQyV5kYINsN66L+2rasu53+1S LAV7oyaLoxD20Eih9dlMsfCClbJ0XN90x4wBTtPcYpyu6RZEUvbmKV0VaGQdU1gM YkMYWHtH4OLp9W/pHVE72WJ8zzSY++u4VtKltfkfZx/ElVlEyUBoMYTc6x8uoXV7 DBl4TCDfmRuVNNN4TTEkb2bM02rVQYVey5i4Z79CQtCrSPiJ/H/UX+bmCYJ7f55q […] -- Backtrace (Reduced): #6 0x000000394c443e84 in KMime::Content::parent (this=0x36b1180) at /usr/src/debug/kdepimlibs-4.9.3/kmime/kmime_content.cpp:949 #7 0x000000351562c336 in MessageCore::NodeHelper::nextSibling (node=0x36b1180) at /usr/src/debug/kdepim-4.9.3/messagecore/nodehelper.cpp:32 #8 0x00007ffa2d307cc4 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff0cd19e90, node=0x36b1180) at /usr/src/debug/kdepim-4.9.3/messageviewer/objecttreeparser.cpp:296 #9 0x00007ffa2d33d530 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x2714f00, content=0x36b1180) at /usr/src/debug/kdepim-4.9.3/messageviewer/viewer_p.cpp:1023 #10 0x00007ffa2d33edfc in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0x2714f00) at /usr/src/debug/kdepim-4.9.3/messageviewer/viewer_p.cpp:895 Created attachment 77821 [details]
New crash information added by DrKonqi
kmail (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4
- What I was doing when the application crashed:
Klicking on a non-MIME-encrypted PGP mail…
-- Backtrace (Reduced):
#6 0x000000367d043e44 in KMime::Content::parent (this=0x4f9c9d0) at /usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_content.cpp:952
#7 0x000000368302c106 in MessageCore::NodeHelper::nextSibling (node=0x4f9c9d0) at /usr/src/debug/kdepim-4.10.1/messagecore/nodehelper.cpp:32
#8 0x0000003683890224 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal (this=0x7fff66518100, node=0x4f9c9d0) at /usr/src/debug/kdepim-4.10.1/messageviewer/objecttreeparser.cpp:296
#9 0x00000036838c4f20 in MessageViewer::ViewerPrivate::parseContent (this=this@entry=0x2bd4210, content=0x4f9c9d0) at /usr/src/debug/kdepim-4.10.1/messageviewer/viewer_p.cpp:974
#10 0x00000036838c674c in MessageViewer::ViewerPrivate::displayMessage (this=this@entry=0x2bd4210) at /usr/src/debug/kdepim-4.10.1/messageviewer/viewer_p.cpp:846
Can someone attach such a mail that let kmail crash? I'm actually working in the crypto part of kmail, and test all different crypto types and had never this problem with a chrashing kmail. This would make the life easier for me to find the bug. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |