1

(14 replies, posted in Bugs & problems)

Chrismar described exactly what happened with me.  And my gpg is also in /usr/local/bin.

2

(11 replies, posted in Bugs & problems)

If I sign some text in Gmail then re-select the signed block and verify, all without sending, it verifies just fine.  I think the word wrap interpretation is accurate.

3

(11 replies, posted in Bugs & problems)

I have the same problem with word wrapping in Gmail.  Not sure how to workaround it, since the Gmail settings don't seem to give any control over wrapping.

Perhaps if FireGPG had an option to hard wrap the selection before signing, then it might not trigger Gmail's wrapping?  Or maybe there is a way to sign that ignores EOL?

Let me know if I can help, I think this is a great extension.

As I mentioned in another post, I am running OS X, 10.4.9.

4

(14 replies, posted in Bugs & problems)

Excellent!  Thank you!

I did notice that at one point, the dialog did open.  It was behind my main window, though.  Once I moved it forward, now it opens in the front as I expect.

I now have my default key selected and my path to gpg correctly set.

5

(14 replies, posted in Bugs & problems)

I have GnuPG installed but the extension isn't seeing my keychain and default signing/encryption key.  I tried to open the options, both through the Tools->FireGPG->Options menu and from Tools->Add-ons and clicking Preferences.  Neither one opens the options dialog so I cannot check and fix my GPG details.  I have had similar problems with one or two other extensions, but most of them work fine.