[Enigmail] [Fwd: Re: Enigmail not detecting/enabling GPG anymore]

[Jean-Marc Meessen]

Hello Olav,

I finally have some time to pick up again this problem. Had to leave it
due to our 20th wedding anniversary (and its preparation !). We had it
yesterday, so I have more time  ;-) 
Thanks for your patience.

I checked your hints but still get not further.

(to put you back in the picture, I crashed my TrueCrypt drive where my
TB profile was residing. Since then, I can't get Enigmail to work again)

Here are a few checks I made that make me really think that the problem
is not related to path problem.

<---------------------------------------------->
/home/user> gpg --version
gpg (GnuPG) 1.4.6
Copyright (C) 2006 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

/home/user> echo $PATH
/home/user/bin:/usr/local/bin:/usr/bin:/bin:/usr/games

/home/user> which gpg
/usr/bin/gpg

<---------------------------------------------->

Starting TB from the shell yields the same results. I am executing for
this what appears to be a bash script located in /opt/thunderbird/ and
called "thunderbird".
Enigmail still fails to initialize (GPG not found in the config screen)

When I look a the produced log file, I only get the following (limited)
information:

<---------------------------------------------->
2008-10-12 11:19:05.829 enigmail.js: Logging debug output to
/home/user/enigdbug.txt
2008-10-12 11:19:05.831 enigmail.js: Enigmail version 0.95.7
2008-10-12 11:19:05.832 enigmail.js: OS/CPU=Linux i686
2008-10-12 11:19:05.834 enigmail.js: Platform=X11
2008-10-12 11:19:05.835 enigmail.js: composeSecure=false
2008-10-12 11:19:05.837 enigmail.js: Enigmail.initialize: Error - Le
service Enigmime n'est pas disponible
<---------------------------------------------->

With the information I have, I don't think it is a path problem. My
current working theory that I hope you will follow or challenge is
rather an init problem caused be the rescue of a corrupted config or
temporary Enigmail file.

When I look at the TB error messages I get the following errors each
time I enter the configuration screen of Enigmail:

<---------------------------------------------->
Erreur : [Exception... "'Failure' when calling method:
[nsIEnigmail::initialize]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"
location: "JS frame :: chrome://enigmail/content/enigmailCommon.js ::
GetEnigmailSvc :: line 214"  data: no]
Fichier source : chrome://enigmail/content/enigmailCommon.js
Ligne : 214

Erreur : Components.classes[ENIG_ENIGMIMESERVICE_CONTRACTID] has no
properties
Fichier source : chrome://enigmail/content/enigmailMsgComposeOverlay.js
Ligne : 223
<---------------------------------------------->

Are these messages helpfull to pinpoint the problem ?

Jmm



Olav Seyfarth a écrit :
> Hi Jean-Marc,
>
> > In a terminal window, when I type "echo $PATH" I get a path where the
> > directory GPG is residing in (/usr/bin) correctly returned.
>
> well, maybe your shell sets an environment different than when you start
> TB through the start menu. Is the result the same when you start it from
> the shell? (first close all instances of TB, open your shell, make sure
> gpg is in path, start TB manually from the command line, try.
>
> > How can I check this value while in Enigmail ? A tracing option maybe ?
>
> OpenPGP -> Preferences
> Enable Expert Settings
> Debugging Tab, enter a DIRECTORY
> Restart TB and reproduce your problem
> check results of your debug DIR
>
> Olav
_______________________________________________
Enigmail mailing list
Enigmail at mozdev.org
https://www.mozdev.org/mailman/listinfo/enigmail


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20081012/bbc42d19/attachment.html>