Public bug reported:

adi@bluestar:~$ gpg --list-public-keys
/home/adi/.gnupg/pubring.gpg
----------------------------
pub   4096R/XXXXXXXX 2015-05-21 [expires: 2017-05-20]
uid                  ************** <**************@gmx.net>
sub   4096R/XXXXXXXX 2015-05-21 [expires: 2017-05-20]

pub   1024D/XXXXXXXX 2005-02-21
uid                  ********* ****** <****************@gmx.at>
sub   2048g/XXXXXXXX 2005-02-21

adi@bluestar:~$ gpg2 --list-public-keys
/home/adi/.gnupg/pubring.kbx
----------------------------
pub   rsa4096/XXXXXXXX 2015-05-21 [SCA] [expires: 2017-05-20]
uid         [ unknown] ************** <************mx.net>
sub   rsa4096/XXXXXXXX 2015-05-21 [E] [expires: 2017-05-20]

pub   rsa4096/XXXXXXXX 2015-02-17 [SC] [expires: 2016-11-11]
uid         [ unknown] ********************* <************************>
sub   rsa4096/XXXXXXXX 2015-11-12 [S] [expires: 2016-11-11]
sub   rsa4096/XXXXXXXX 2015-11-12 [E] [expires: 2016-11-11]
sub   rsa4096/XXXXXXXX 2015-12-25 [S]
sub   rsa4096/XXXXXXXX 2015-12-25 [E]
sub   rsa4096/XXXXXXXX 2015-12-25 [A]

pub   rsa4096/XXXXXXXX 2015-04-23 [SC]
uid         [ unknown] ***************** <*****************************>
sub   rsa4096/XXXXXXXX 2015-04-23 [E]
sub   rsa4096/XXXXXXXX 2015-04-23 [S]

The keys in gpg2 were automatically imported because they have signed my key. 
All manually imported keys are imported into gpg-public-list.
Seahorse only provides you the keys in the gpg2-list. Where can i find the 
configuration for this?

** Affects: seahorse (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588605

Title:
  Seahorse imports keys into gpg-list and only shows keys from gpg2-list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1588605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to