syncpackage gives Python traceback on gnomekeyring.IOError

Bug #1026146 reported by Till Kamppeter
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python-launchpadlib (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When I run

syncpackage -d experimental c2esp

I get

----------
till@till:~/printing/cups/bzr$ syncpackage -d experimental c2esp
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/syncpackage", line 742, in <module>
    main()
  File "/usr/bin/syncpackage", line 642, in main
    Launchpad.login(**kwargs)
  File "/usr/lib/python2.7/dist-packages/ubuntutools/lp/lpapicache.py", line 66, in login
    version=api_version)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 539, in login_with
    credential_save_failed, version)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 342, in _authorize_token_and_login
    authorization_engine.unique_consumer_id)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 282, in load
    return self.do_load(unique_key)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 336, in do_load
    'launchpadlib', unique_key)
  File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 34, in get_password
    return _keyring_backend.get_password(service_name, username)
  File "/usr/lib/python2.7/dist-packages/keyring/backend.py", line 154, in get_password
    items = gnomekeyring.find_network_password_sync(username, service)
gnomekeyring.IOError
till@till:~/printing/cups/bzr$
----------

This happens on both Precise and Quantal.
---
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
DistroRelease: Ubuntu 12.04
Package: ubuntu-dev-tools 0.141
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Tags: precise running-unity
Uname: Linux 3.2.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare
---
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 12.10
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Package: ubuntu-dev-tools 0.143
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Tags: quantal running-unity
Uname: Linux 3.5.0-4-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Till Kamppeter (till-kamppeter) wrote : Dependencies.txt

apport information

tags: added: apport-collected precise running-unity
description: updated
tags: added: quantal
description: updated
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

apport information

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

The first Dependecies.txt attachment is from Precise, the second from Quantal.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

I have checked the instructions in

/usr/share/doc/ubuntu-dev-tools/NEWS.Debian.gz

entry 0.119, but I am not SSHed in in both Precise and Quantal cases. Doing "export `dbus-launch`" anyway does not help, uninstalling python-gnomekeyring does not work as system-config-printer needs it.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

The problem was that on both systems gnome-keyring-daemon was not running (should be started on login). I started it with

gnome-keyring-daemon

so the problem in syncpackage is that it does not show a decent error message like "Do you have gnome-keyring-daemon running?" instead of throwing a backtrace.

Changed in ubuntu-dev-tools (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Stefano Rivera (stefanor) wrote :

Sounds more like launchpadlib's problem than syncpackage's. Reassigning

affects: ubuntu-dev-tools (Ubuntu) → python-launchpadlib (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in python-launchpadlib (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris J Arges (arges) wrote :

Works for me in raring, but I get the same failure in precise.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.