Summary: | S/MIME plugin fails to initialize for KMail | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Vincent Broman <vbroman> |
Component: | encryption | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | CLOSED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Vincent Broman
2003-06-05 01:44:25 UTC
Subject: Re: New: S/MIME plugin fails to initialize for KMail Sorry, but that's most likely an installation or distribution specific problem. On my SuSE 8.2 system it works fine. I'm using dirmngr-0.4.4, gnupg-1.2.2 and pinentry-0.6.9. The rest is the same as yours. BTW, the correct address for problems with the crypto plugins is gpa-dev@gnupg.org. Subject: Re: S/MIME plugin fails to initialize for KMail On Thursday, 05 June 2003 16:21, you wrote: > http://bugs.kde.org/show_bug.cgi?id=59358 > kloecker@kde.org changed: > Resolution| |WORKSFORME > > ------- Additional Comments From kloecker@kde.org 2003-06-06 01:21 ------- > Subject: Re: New: S/MIME plugin fails to initialize for KMail > > Sorry, but that's most likely an installation or distribution specific > problem. On my SuSE 8.2 system it works fine. Not a very helpful comment, because these packages are not assembled in any polished distribution, they are more-or-less roll your own. If you have spec files that you know work well, I would appreciate them. The weird thing I just noticed was that kmail complains about the plugin with version: 0.3.15, but what I have installed is 0.3.16 ! Where could kmail find some other copy of a plugin, since the plugin installation selects one .so in one directory explicitly? Vincent Broman Subject: Re: S/MIME plugin fails to initialize for KMail On Friday 06 June 2003 02:09, Vincent Broman wrote: > On Thursday, 05 June 2003 16:21, you wrote: > > Sorry, but that's most likely an installation or distribution > > specific problem. On my SuSE 8.2 system it works fine. > > Not a very helpful comment, because these packages are not > assembled in any polished distribution, they are more-or-less roll > your own. If you have spec files that you know work well, I would > appreciate them. You could try to install the RPMs which come with the SuSE 8.2 distribution (which is what I did). This distribution can be found at ftp.suse.com. If the RPMs don't work then download the SRPMs and rebuild them. I updated some of the SRPMs to newer versions. I will try to make them available via http://kmail.ingo-kloecker.de (but not before Tuesday). Before using the SuSE RPMs I've compiled all necessary packages myself according to the instructions at http://www.gnupg.org/aegypten/development.en.html. > The weird thing I just noticed was that kmail complains about > the plugin with version: 0.3.15, but what I have installed is 0.3.16 > ! Where could kmail find some other copy of a plugin, since > the plugin installation selects one .so in one directory explicitly? I think 0.3.15 refers to the version number of the gpgme library and not to the version number of the crypto plugins. Anyway, this error message isn't very helpful. Unfortunately many error messages of the crypto plugins are confusing. You should try whether you get some useful debug messages when you start kmail from command line. Regards, Ingo It looks like the unhelpful message may have been caused by an inability to contact a gpg-agent, where the environment vars didn't get set properly to point to the running gpg-agent. Fixing that, I don't get that message anymore, but I get lots of stored messages marked as having a "bad signature" and logs mention "Invalid Key". Perhaps an independent problem. I have redhat9 src.rpms if anyone wants the specs. |