I'm stumbling into this bug now and then, using standard C code to query gnome-keyring via gnome_keyring_find_password_sync()
Works most of the time, but returns the error with an approximated ratio of 2% of the times it is called. In some implementation this may lead in a dialog asking a password that is already saved, resulting in an overwrite of passwords stored inside the gnome keyring.
The error message is:
```
Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
Gkr-Message: call to daemon returned an invalid response: (null).(null)()
```
A good way to reproduce could be to write a code that loops through subsequent gnome_keyring_find_password_sync() requests.
I'm stumbling into this bug now and then, using standard C code to query gnome-keyring via gnome_keyring_ find_password_ sync()
Works most of the time, but returns the error with an approximated ratio of 2% of the times it is called. In some implementation this may lead in a dialog asking a password that is already saved, resulting in an overwrite of passwords stored inside the gnome keyring.
The error message is:
```
Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
Gkr-Message: call to daemon returned an invalid response: (null).(null)()
```
A good way to reproduce could be to write a code that loops through subsequent gnome_keyring_ find_password_ sync() requests.