Public bug reported: If a new GnuPG key is created, the key sometimes does not actually get created, or sometimes seems to be created but does not appear in the "GnuPG keys" display until seahorse is restarted.
I haven't been able to nail an exact sequence to force mis-behavior, but the following procedure reliably reproduces the problem after 1-3 iterations: STEPS TO REPRODUCE: 1. Run /usr/bin/seahorse 2. Immediately do File->New... PGP Key (Continue) and enter the info to create a new key 3. In the left panel, select "GnuPG keys" RESULTS (sometimes): The new key is not shown. If the key is _not_ displayed, exit seahorse and restart; sometimes the key appears then (other times it never appears, indicating that the key wasn't actually created or was somehow lost). If the new key _does_ appear, then switch the view to "Gnome2 Key Storage", and repeat steps #2 and #3 above until the new key does not appear under "GnuPG keys" (not viewing GnuPG keys while creating a key seems to encourage the bug :-) EXPECTED RESULTS: Newly-created keys should always appear in the GnuPG keys display ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: seahorse 3.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 4 11:04:38 2015 InstallationDate: Installed on 2013-08-06 (575 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: seahorse UpgradeStatus: Upgraded to utopic on 2014-11-10 (114 days ago) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug third-party-packages utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1428281 Title: Newly created GnuPG keys sometimes disappear and/or are not displayed in seahorse GnuPG keys display Status in seahorse package in Ubuntu: Invalid Bug description: If a new GnuPG key is created, the key sometimes does not actually get created, or sometimes seems to be created but does not appear in the "GnuPG keys" display until seahorse is restarted. I haven't been able to nail an exact sequence to force mis-behavior, but the following procedure reliably reproduces the problem after 1-3 iterations: STEPS TO REPRODUCE: 1. Run /usr/bin/seahorse 2. Immediately do File->New... PGP Key (Continue) and enter the info to create a new key 3. In the left panel, select "GnuPG keys" RESULTS (sometimes): The new key is not shown. If the key is _not_ displayed, exit seahorse and restart; sometimes the key appears then (other times it never appears, indicating that the key wasn't actually created or was somehow lost). If the new key _does_ appear, then switch the view to "Gnome2 Key Storage", and repeat steps #2 and #3 above until the new key does not appear under "GnuPG keys" (not viewing GnuPG keys while creating a key seems to encourage the bug :-) EXPECTED RESULTS: Newly-created keys should always appear in the GnuPG keys display ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: seahorse 3.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 4 11:04:38 2015 InstallationDate: Installed on 2013-08-06 (575 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: seahorse UpgradeStatus: Upgraded to utopic on 2014-11-10 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1428281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp