kgpg can't delete key pairs

Thanks for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in kgpg.

This needs to be fixed...soon.

Good evening,

I was working through this bug and am unable to replicate this problem. I am using KGpg 1.2.2 (Using KDE 3.5.8) under Kubuntu 7.10

Steps I took to try and reproduce:
1. generate a keypair
2. select the keypair
3. right-click and select delete
4. answer the questions about deleting the key or not
5. key is no longer in the keyring

Can you please make sure your system is up date and then try to reproduce thsi bug? If you are not please mark this bug as such if you are please update this bug wit hthe exact version of KGpg you are using.

Thanks,

Jonathan

I am using kgpg 1.2.2 (using KDE 2.5.8) in Gnome on Ubuntu 7.10

Even after moving my .gnupg directory out of the way so that gpg settings are at default, it still doesn't do anything when I try to delete the keypair.

Also, not sure if it matters but I am using the gpg agent.

I am using Kgpg 1.2.2 (KDE 3.5.8) running Kubuntu 7.10 (Gutsy Gibbon). I am not able to reproduce this bug using the "Steps to reproduce:" instructions provided. I was able to delete the key pair by right-clicking, selecting "Delete key pair", pressing the "Delete" button on the warning dialog and answering yes to the two questions in the resulting terminal.

Is it possibly failing to spawn a terminal?

Alex, can you try running kgpg from a terminal (konsole, xterm, gnome-terminal, whatever) and see if there's any interesting output when it fails to delete the keypair?

I'm with KDE: 3.5.8 KGpg: 1.2.2 and I can't reproduce your bug

This seems to be working for me now, on a clean install of Ubuntu Hardy.

I'll check for it on the previous install as well.

If it's still not working there, any suggestions of where to check for settings differences?

Also, this is not working in kgpg-kde4 either.

Marking invalid for kdeutils-kde4 as KDE 4 is default in Intrepid, so the issue will be tracked in kdeutils anyway.

The original reporter mentioned that this is working for him now so I'm closing this bug.
(Also it was annoying that this bug was the very first on https://launchpad.net/ubuntu/+bugs because the importance was set to unknown. Now bug #1 is the first as it should be. Please change importance of this bug. )