Which app complaining about login keyring?

[Colin Law]

On 29 August 2015 at 08:55, Colin Law <clanlaw at gmail.com> wrote:
> Recently on 15.04 (standard Ubuntu) I have started getting the popup
> message "Enter password to unlock your keyring, the login keyring did
> not get unlocked when you logged into your computer".  Anyone know how
> to find out which app is requesting the keyring?  I want to find why
> it has only started happening recently as I have not changed my login
> credentials.

I am homing in on this, it appears to be oneconf that is doing it.
Immediately before the popup appears (or as it appears) data in
.cache/oneconf/..../package_list_... and host are updated and after a
valid pwd is entered last_sync is updated.

In auth.log the following is seen after entering the pwd, though I
don't know whether it tells us anything useful

Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: completed password
prompt for callback :1.96@/org/gnome/keyring/Prompt/p1
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: encrypting data
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: sending the secret
exchange: [sx-aes-1]\npublic=[snipped]
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: calling the
PromptReady method on /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: returned from the
PromptReady method on /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: received PerformPrompt
call from callback /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: stopping prompting for
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: closing the prompt
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: stopping prompting for
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: couldn't find the
callback for prompting operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: stopping prompting for
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: couldn't find the
callback for prompting operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: stopping prompting for
operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: couldn't find the
callback for prompting operation /org/gnome/keyring/Prompt/p1@:1.96
Aug 31 07:54:40 tigger gcr-prompter[4444]: Gcr: calling the PromptDone
on /org/gnome/keyring/Prompt/p1@:1.96, and ignoring reply
Aug 31 07:54:50 tigger gcr-prompter[4444]: 10 second inactivity
timeout, quitting
Aug 31 07:54:50 tigger gcr-prompter[4444]: Gcr: unregistering prompter
Aug 31 07:54:50 tigger gcr-prompter[4444]: Gcr: disposing prompter
Aug 31 07:54:50 tigger gcr-prompter[4444]: Gcr: finalizing prompter

It seems I am not the only one seeing this
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1474182

I suppose the next question is whether oneconf is doing its thing
(whatever that is) when it should not be, or whether it is requesting
a key when it should not.

Colin