console launchpad-login warns about gnome-keyring in Precise

[Alex Chiang]

On Canonical's Open Stack cloud:

- started a Precise image
- sudo apt-get install ubuntu-dev-tools packaging-dev
- then attempt bzr launchpad-login <login>

Result:

ubuntu@server-3424:~/Projects$ bzr launchpad-login achiang
WARNING: gnome-keyring:: no socket to connect to

This exact sequence succeeds on a Natty image in the cloud.

Using:
ii bzr 2.5.0~beta4-1ubuntu1 easy to use distributed version control system

ubuntu@server-3424:~/Projects$ bzr plugins
bash_completion 2.5b4
  Generate a shell function for bash command line completion.

builddeb 2.7.0dev
  bzr-builddeb - manage packages in a Bazaar branch.

changelog_merge 2.5b4
  Merge hook for GNU-format ChangeLog files

launchpad 2.5b4
  Launchpad.net integration plugin for Bazaar.

netrc_credential_store 2.5b4
  Use ~/.netrc as a credential store for authentication.conf.

news_merge 2.5b4
  Merge hook for bzr's NEWS file.

po_merge 2.5b4
  Merge hook for ``.po`` files.

weave_fmt 2.5b4
  Weave formats.

[Jelmer Vernooij (jelmer)]

Note that this is just a warning, but it's a bit confusing as lp-login doesn't give any other output.

I wonder what is actually trying to contact gnome-keyring, as bzr itself doesn't talk to it. launchpadlib, which the launchpad and builddeb plugins for bzr use for some things, does use gnome keyring (through python-keyring), but the lp-login command doesn't.

[Martin Pool (mbp)]

can you please attach the traceback from ~/.bzr.log?

[Vincent Ladeuil (vila)]

lp-login uses authentication.conf for which bzr-gtk is/was adding a credential store, this is probably the root cause (I thought there was a open bug on bzr-gtk for that or something closely related).