Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 120286 - Kmail crashes with new stable glibc sending to pgp enabled users
Summary: Kmail crashes with new stable glibc sending to pgp enabled users
Status: RESOLVED DUPLICATE of bug 61146
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL: http://forums.gentoo.org/viewtopic-t-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-25 04:20 UTC by Francesco
Modified: 2006-02-02 11:40 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francesco 2006-01-25 04:20:30 UTC
As you can read in the url I posted kmail has problems sending mail to people you have encription keys for, even if you don't encrypt the mail you're sending.
Fixaround is disabling gpg support in kmail.

Error is glibc related:
*** glibc detected *** double free or corruption (out): 0x086712e8 ***
*** KMail got signal 6 (Crashing)

Rebuilding kmail or gnupg doesn't solve the problem.
Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev 2006-01-25 06:00:05 UTC
No it's not glibc related, there's something that's trying to double free a pointer, that's plainly wrong.
Try to get a backtrace out of it, and please post emerge info.
Comment 2 Caleb Tennis (RETIRED) gentoo-dev 2006-01-25 08:11:54 UTC
You can workaround it by setting MALLOC_CHECK_ environment variable to 0, but that's just a hack.
Comment 3 Bernd Wurst 2006-02-02 11:26:11 UTC
I also had this bug. 

For me, this was solved after re-merging glibc, qt, kdelibs and kmail with the same compiler. I switched the compilter (3.3.6 to 3.4.4) just before the kde upgrade, so glibc and qt had been compiled with 3.3.6 and kde with 3.4.4. Recompiling all of them with 3.4.4 solved this.
Comment 4 Diego Elio Pettenò (RETIRED) gentoo-dev 2006-02-02 11:40:25 UTC

*** This bug has been marked as a duplicate of 61146 ***