Summary: | =mail-client/mutt-1.5.20-r1 crashes with =app-crypt/gpgme-1.2.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | Fabian Groffen <grobian> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | arfrever, net-mail+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://dev.mutt.org/trac/ticket/3300 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 277890 | ||
Attachments: |
The build log
gpgme-1.2.0 patch gpgme init patch v2 gpgme init patch v3 |
Description
Michał Górny
2009-07-20 09:39:32 UTC
Created attachment 198553 [details]
The build log
From NEWS file of app-crypt/gpgme-1.2.0: * gpgme_new will fail if gpgme_check_version was not called, or a selftest failed (for example, if -mms-bitfields was not used on MingW32 targets). Created attachment 198635 [details, diff]
gpgme-1.2.0 patch
From what I've been told this should make it work.
Could you please give this a try?
(In reply to comment #3) > Created an attachment (id=198635) [edit] > gpgme-1.2.0 patch Calling gpgme_check_version(NULL) once per initialization of mutt should be sufficient, but this patch shouldn't create noticeable performance penalty. It would be better if mutt upstream applied a patch which causes calling gpgme_check_version(NULL) only once per initialization of mutt. Patch fixes the issue but I agree with Arfrever that this is not the best solution. Created attachment 198713 [details, diff]
gpgme init patch v2
Can you please try this patch as well. Unfortunately I don't have emails to test this.
Created attachment 198714 [details, diff]
gpgme init patch v3
right, too quick, this should work better
Works fine for me. Ok, thanks for testing. Patch went upstream, we'll see what they'll do eventually. |