Bug ID | 958891 |
---|---|
Summary | gnupg in Tumbleweed 20151209 - finds ambiguity where there is none |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | 2015* |
Hardware | x86-64 |
OS | SUSE Other |
Status | NEW |
Severity | Critical |
Priority | P5 - None |
Component | Basesystem |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | nwr10cst-oslnx@yahoo.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.14.10 Safari/537.21 Build Identifier: I noticed the problem, because I could not open KDEWallet (uses GPG encryption). Here's some output: --- cut here --- % gpg --list-keys rickert gpg: key specification 'D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1' is ambiguous gpg: (check argument of option '--encrypt-to') gpg: 'D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1' matches at least: gpg: D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1 gpg: D80CB5EF2D9FCB98FF88604BC2781C1A46B1EFE1 --- cut here --- That's bogus ambiguity. Maybe it is finding the same key twice, perhaps because an earlier gpg2 version insisted on copying keys to another place. I've flagged this as "critical" since I lose access to kdewallet. Reproducible: Always