A fix for this is given in https://bugs.archlinux.org/task/20606.  The gpg setting should be changed to use the gpg2 program (Settings->Configure GPG, GnuPG Settings, Program path: gpg2).

Alternatively, the ~/.kde4/share/config/kgpgrc file needs to be modified as follows.  From:

[GPG Settings]
gpg_bin_path[$e]=gpg
gpg_config_path[$e]=$HOME/.gnupg/gpg.conf

to:

[GPG Settings]
gpg_bin_path[$e]=gpg2
gpg_config_path[$e]=$HOME/.gnupg/gpg.conf

Is there a way of automating this for the user in a new RPM file?

Hardware: i586 => x86_64

Ouch! gpg2 doesn't support the idea algorithm, which my key (created back with
pgp 1 (or maybe 2), uses.

I hope idea will be added for gpg2, when the patent expires next Jan.

CC: (none) => davidwhodgins

I'm not sure it's a good idea to force gpg2 configuration.
Also during the first configuration of kgpg,the user is asked to choice is gpg program (& so configure it), so we should not force the user to a specific configuration.
Did you try using gpg-agent eventually ?

(In reply to comment #3)
> I'm not sure it's a good idea to force gpg2 configuration.
> Also during the first configuration of kgpg,the user is asked to choice is gpg
> program (& so configure it), so we should not force the user to a specific
> configuration.
> Did you try using gpg-agent eventually ?

@ John
Maybe the addressed person wasn't aware he was addressed. You might want to mention his name when you ask him again ;)

CC: (none) => marja11

If it was addressed to me, then I haven't tried gpg-agent and wouldn't know how to use it to solve this problem.  It is working for me now as I changed this to gpg2.  I have just changed back to gpg and tried to decrypt my file in the kgpg editor window, and the window just goes blank.  Reverting to gpg2 fixes this.  I'm guessing the kgpg configuration file from my previous Mandriva install was clobbered and the gpg binary setting reset to blank (hence defaulting to gpg).

So the way a user encounters this is when the user decrypts an old file and the editor goes blank.  The only solution for the user is a very difficult Google search for a solution which is to change the binary path from nothing to gpg2.  Ideally upstream should detect this and suggest switching from gpg to gpg2 (or the reverse if the idea algorithm is detected).  I do not want to test this on the new Mageia alpha as my system is production.

i'm closing it as wontfix thought.
We don't have to force a gpg configuration by default since :
- the wizard ask for user's choice
- gpg & gpg2 seems to not have the same functionnality according to #2

We should document in our wiki the fact that sometimes it could be wise to switch to gpg2 if the binary path is empty (but maybe it's already inside the kgpg fact i did not check)

Status: NEW => RESOLVED
CC: (none) => balcaen.john
Resolution: (none) => WONTFIX

(In reply to comment #6)

> We should document in our wiki the fact that sometimes it could be wise to
> switch to gpg2 if the binary path is empty (but maybe it's already inside the
> kgpg fact i did not check)

Added it to the list here, please remove if it isn't needed (or add your name down as volunteer to get this in the wiki :þ)

add your name down :/

add your name 
or
put your name down 

;)

(In reply to comment #7)
> (In reply to comment #6)
> 
> > We should document in our wiki the fact that sometimes it could be wise to
> > switch to gpg2 if the binary path is empty (but maybe it's already inside the
> > kgpg fact i did not check)
> 
> Added it to the list here, please remove if it isn't needed (or add your name
> down as volunteer to get this in the wiki :þ)
I added this in formation in the wiki few minutes after adding this comment cf ( the Mageia 1 Erra cf https://wiki.mageia.org/en/Mageia1_errata#Kgpg_decrypt_issue )

(In reply to comment #9)

> I added this in formation in the wiki few minutes after adding this comment cf
> ( the Mageia 1 Erra cf
> https://wiki.mageia.org/en/Mageia1_errata#Kgpg_decrypt_issue )

Great :D

You're very welcome in the documentation team ;)