Bug 59358 - S/MIME plugin fails to initialize for KMail
Summary: S/MIME plugin fails to initialize for KMail
Status: CLOSED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-05 01:44 UTC by Vincent Broman
Modified: 2007-09-14 12:17 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 Vincent Broman 2003-06-05 01:44:25 UTC
Version:            (using KDE KDE 3.1.2)
Installed from:    RedHat RPMs
Compiler:          gcc-3.2.2-5 from redhat 
OS:          Linux

I am running a new installation of redhat 9 on a slow pentium.
I've upgraded KDE to 3.1.2-0.9x.2 .
I had a working set of sphinx tools for kmail under redhat 7.3.
I've recompiled the rpm packages under redhat9, installed them,
and configured them into KMail.

(Well, almost. The "configuration" step under
Configure KMail->Security->Crypto Plugins->configure
fails for the S/MIME plugin with this message:

    KGpgCertManager
    The crypto plugin could not be initialized; the error message was .
    Certificate Manager will terminate now.
)

In any case, KMail now produces a pop-up error message when
the program starts, saying:

Error - KMail
    Error: Plug-in "S/MIME" initialization unsuccessful.
    library: /usr/lib/cryptplug/gpgme-smime.so
    version: 0.3.15
    Plug-in is out-dated or not installed properly.

I believe I've installed it the same as before, but these
messages don't give much of a clue what to fix.

My package versions:
cryptplug-0.3.16-1vpb.i386.rpm
dirmngr-0.4.5-1vpb.i386.rpm
gnupg-1.2.1-1vpb.i386.rpm
gpgme-0.3.15-2vpb.i386.rpm
gpgme-devel-0.3.15-2vpb.i386.rpm
libgcrypt-1.1.12-5vpb.i386.rpm
libgcrypt-devel-1.1.12-5vpb.i386.rpm
libgcrypt-static-1.1.12-5vpb.i386.rpm
libksba-0.4.7-1vpb.i386.rpm
libpth14-1.4.1-5vpb.i386.rpm
libpth14-devel-1.4.1-5vpb.i386.rpm
newpg-0.9.4-4vpb.i386.rpm
pinentry-0.6.8-3vpb.i386.rpm
kdenetwork-3.1.2-0.9x.1.i386.rpm

I guess I could send the src rpms if needed.

Vincent P. Broman
Comment 1 Ingo Klöcker 2003-06-06 01:21:56 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.

Comment 2 Vincent Broman 2003-06-06 02:09:20 UTC
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

Comment 3 Ingo Klöcker 2003-06-07 14:42:11 UTC
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

Comment 4 Vincent Broman 2003-06-13 02:19:04 UTC
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.