GPG seems broken on FC13 after upgrade.

[Perry, James J.]

I was able to get that to work a while back but the main problem I am
having is that if I have the display set on the terminal doing the ssh
into the host but no X-server (Cygwin/X) running on my PC, then it fails
to fall back to text-based password requests, making me spend hours
trying to figure out what happened.  If the interface is being changed
in this manner than it would seem that simple code to check for a
responding X-server or if the X-server connection is denied, it would
fall back to curses style windows.

HP's diagnostic tool stm, installation utility swinstall and OS level
tool SAM all have had this logic for > 10 years.

Just me doing something unexpected when the application was being beta
tested that I wanted to bring up with a solution to see if it could
improve the new interface to the application.

   Thanks!
   -Jim

-----Original Message-----
From: Chris Ruff [mailto:jcruff at gmail.com] 
Sent: Tuesday, July 20, 2010 6:09 PM
To: Perry, James J.
Cc: gnupg-users at gnupg.org
Subject: Re: GPG seems broken on FC13 after upgrade.

On 06/01/2010 06:49 PM, Perry, James J. wrote:
> I just updated to FC 13 and not gpg fails to work for any user.  I get
> the following messages when I try to decrypt a file and have the
DISPLAY
> set even though I am not using X.
> 
>  
> 
> gpg --pgp6 EDI997.20100601091546.pgp
> 
>  
> 
> You need a passphrase to unlock the secret key for
> 
> user: "xyz"
> 
> 2048-bit ELG key, ID ...
> 
>  
> 
> can't connect to `/root/.gnupg/S.gpg-agent': No such file or directory
> 
> gpg-agent[24444]: command get_passphrase failed: Operation cancelled
> 
> gpg: cancelled by user
> 
> gpg: encrypted with 2048-bit ELG key, ID ...
> 
> gpg: public key decryption failed: General error
> 
> gpg: decryption failed: No secret key
> 
>  
> 
> This happens when I have a DISPLAY variable set.  Without it I get a
bad
> looking curses interface image like below:
> 
>
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
k
> 
>    x Please enter the passphrase to unlock the secret key for the
OpenPGP  x
> 
>    x certificate:
x
> 
>    x "xyz"
x
> 
>    x 2048-bit ELG key, ID ...                                        x
> 
>    x created 2010-05-30 (main key ID ...).
x
> 
>    x
x
> 
>    x
x
> 
>    x Passphrase
__________________________________________________________ x
> 
>    x
x
> 
>    x          <OK>                                         <Cancel>
x
> 
>
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
j
> 
>  
> 
> This was not how it worked when I used it prior to upgrading to FC13.
I
> do not want all the pretty stuff and I need it to prompt for a
password
> on the command line like it did prior to the used of pinentry-qt or
> pinentry-curses.  What do I need to fix?  I spent 4 hours digging
around
> to just find that if I had a DISPLAY variable set but no X-Server
> running on my MS Win box, it would not even work.  Users of GPG here
on
> Linux will not understand that issue so I will need to keep it running
> as it did before, but no manuals I found seemed to indicate how to
> correct it.
> 
>  
> 
>   Thanks!
> 
>    -Jim
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users

I'm not sure if this is your exact problem but on my openSuSE 11.2
system Seahorse really made a mess of things.  Try running your
gpg-agent the old fashion way and export the variables.  I'm
initializing mine in .xinitrc with an eval statement and relevant
arguments b/c seahorse doesn't seem to work correctly with scdaemon.

-- 
__________________________________
Chris Ruff
email: jcruff at gmail.com
gpg key: 0x0621F585
gpg fgpr: E3C4 0E2E AD99 59A2 E4D0
          DC1B FD21 25BC 0621 F585
 
Proud partner. Susan G. Komen for the Cure.
 
Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------