Created attachment 302551 [details]
Testcase to illustrate the issue

I'm using the simple api in my application to lookup passwords from the secret service. This works fine if the keyring is unlocked but fails if it is not.

Attached is a simple test case to illustrate my issue.

What probably matters is that I'm running into this issue when using the application from a kde environment, in which gnome-keyring-daemon is not launched and unlocked at startup. When running I am killing gnome-keyring-daemon before running the tests to reproduce this issue.

The test has two executables:
- libsecret-test-store -> will store a password in the secret service to be retrieved with the second executable

- libsecret-test-get -> will attempt to lookup a password using the simple api.

libsecret-test-store is only added to store an initial password so we can test retrieval with the second executable. Storing works fine regardless of whether gnome-keyring-daemon was running or not. If the daemon isn't running it will start the daemon. If the keyring is (still) locked it will prompt for a password to unlock. 

The second executable can be used to illustrate my issue once a password has been stored. Running it immediately after storing the password will work correctly (because the keyring is still unlocked).

Locking the keyring using seahorse and then running libsecret-test-get will make it prompt for a password to unlock and then successfully retrieve the stored password.

However after killing gnome-keyring-daemon, the second executable won't find the password. It won't even ask for a password to unlock the keyring. It does start the gnomne-keyring-daemon though.

I expected the simple API would do what is needed to lookup the password, including unlocking the keyring if that's required to find the password. Is that a wrong assumption ?