** Changed in: gnome-keyring (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1181344

Title:
  python-keyring timeout on import if started with sudo

Status in GNOME Keyring:
  Fix Released
Status in Salt:
  New
Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  steps to reproduce:
  $ sudo python
  Python 2.7.3 (default, Sep 26 2012, 21:53:58)
  [GCC 4.7.2] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import keyring

  this will take ~25 seconds only on Xubuntu. If you do this on Ubuntu
  or Kubuntu (all version 12.10) it will return immediately. Also if you
  import keyring with normal user on Xubuntu it will return immediately.

  It is caused by a dbus call in /usr/share/pyshared/keyring/backend.py 
function SecretServiceKeyring.supported:
  $ sudo python
  Python 2.7.3 (default, Sep 26 2012, 21:53:58)
  [GCC 4.7.2] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import dbus
  >>> bus = dbus.SessionBus()
  >>> bus.get_object('org.freedesktop.secrets', '/org/freedesktop/secrets')
  Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
    File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
      follow_name_owner_changes=follow_name_owner_changes)
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in 
__init__
      self._named_service = conn.activate_name_owner(bus_name)
    File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
      self.start_service_by_name(bus_name)
    File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
      'su', (bus_name, flags)))
    File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
      message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/1181344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to