Thanks!
On 05.11.19 21:30, Sebastien Bacher wrote:
> thanks, closing then
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: Incomplete => Invalid
>
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
htt
thanks, closing then
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1841051
Title:
gpg password ca
It is no fault.
My original FR concerned gpg-agent because I was unaware of the fact
that
seahorse/gnome-keyring had the password stored.
On 05.11.19 11:26, Sebastien Bacher wrote:
> Thank you for your bug report. Could you give details on what you did
> exactly? If you ticked the box to store t
Thank you for your bug report. Could you give details on what you did
exactly? If you ticked the box to store the auth in the keyring that's
what it did, why would you expect it to do instead?
** Package changed: seahorse (Ubuntu) => gnome-keyring (Ubuntu)
** Changed in: gnome-keyring (Ubuntu)
** Package changed: gnupg2 (Ubuntu) => seahorse (Ubuntu)
** Changed in: seahorse (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1841051
Ti