bzr vis exception org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0

[Loïc Minier]

Hi,

Got this exception thrown at me on a bzr vis today:
% bzr vis
Format <RepositoryFormatKnit1> for file:///home/lool/bzr/launchpad/%7Eubuntu-toolchain/ubuntu-toolchain/glibc-2.5-package/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
bzr: ERROR: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 896, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 842, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 542, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/__init__.py", line 288, in run
    pp = start_viz_window(br, revids, limit)
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/__init__.py", line 256, in start_viz_window
    from bzrlib.plugins.gtk.viz import BranchWindow
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/viz/__init__.py", line 14, in <module>
    from branchwin import BranchWindow
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/viz/branchwin.py", line 18, in <module>
    from bzrlib.plugins.gtk.tags import AddTagDialog
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/tags.py", line 27, in <module>
    from bzrlib.plugins.gtk.revisionview import RevisionView
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/revisionview.py", line 32, in <module>
    from bzrlib.plugins.gtk import seahorse
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/seahorse.py", line 33, in <module>
    crypto = dbus.Interface(bus.get_object(BUS_NAME, CRYPTO_PATH),
  File "/var/lib/python-support/python2.5/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/var/lib/python-support/python2.5/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/var/lib/python-support/python2.5/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 622, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0

bzr 1.12 on python 2.5.4 (linux2)
arguments: ['/usr/bin/bzr', 'vis']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'fr_FR.UTF-8'
plugins:
  builddeb /usr/lib/python2.5/site-packages/bzrlib/plugins/builddeb [2.1dev]
  bzrtools /usr/lib/python2.5/site-packages/bzrlib/plugins/bzrtools [1.12]
  gtk /usr/lib/python2.5/site-packages/bzrlib/plugins/gtk [0.95.0.final.1]
  launchpad /usr/lib/python2.5/site-packages/bzrlib/plugins/launchpad [unknown]
  netrc_credential_store /usr/lib/python2.5/site-packages/bzrlib/plugins/netrc_credential_store [unknown]
  rebase /usr/lib/python2.5/site-packages/bzrlib/plugins/rebase [0.4.2]
  svn /usr/lib/python2.5/site-packages/bzrlib/plugins/svn [0.5]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.

I did a bzr log, and bzr vis again, and it worked fine, so would seem like a race perhaps?

Cheers,

[Loïc Minier (lool)]

Ok, this happened again immediately after a bzr rebase, and I think it was the case the first time as well.

I tried to rebase again, but it doesn't occur if there was nothing to rebase.

[James Westby (james-w)]

Hi,

The problem is that seahorse changed its dbus interface.

It now has both objects on the same interface:

CRYPTO_INTERFACE = 'org.gnome.seahorse'
CRYPTO_PATH = '/org/gnome/seahorse/crypto'

OPENPGP_INTERFACE = 'org.gnome.seahorse'
OPENPGP_PATH = '/org/gnome/seahorse/keys/openpgp'

works.

I'm not sure how to detect which is needed at run-time though.

Opening an Ubuntu task as well, as we can always patch it to use
the new interface in for Jaunty if we can't get auto-detection working
in time.

Thanks,

James

[Launchpad Janitor (janitor)]

This bug was fixed in the package bzr-gtk - 0.95.0+bzr629-1ubuntu1

---------------
bzr-gtk (0.95.0+bzr629-1ubuntu1) jaunty; urgency=low

  * Sync on Debian experimental.
  * Change DBus path for seahorse to match what we have in Jaunty.
    (LP: #332050)
  * Add missing import of gobject in bzr-notify to fix crashes.
  * This version makes the notification icon not be shown all the time.
    (LP: #283832)
  * FFe is in LP: #338013.

bzr-gtk (0.95.0+bzr629-1) experimental; urgency=low

  * New usptream snapshot.
  * Remove Chris Lamb from Uploaders, per his request.
  * Add Depends: python-notify as this is used by bzr-notify. Thanks
    Ralph Janke (LP: #281901)

bzr-gtk (0.95.0+bzr622-1) experimental; urgency=low

  * Add build dependency on python-nautilus.
  * Depend on newer version of python-nautilus, with changed API.
    (Closes: #501597)

bzr-gtk (0.95.0+bzr621-1) experimental; urgency=low

  * New upstream snapshot
  * Use olive-gtk.1 included with upstream.
  * Suggest bzr-loom, since there now is a loom frontend.

bzr-gtk (0.95.0+bzr611-1) experimental; urgency=low

  * Package new upstream snapshot.

 -- James Westby <email address hidden> Wed, 04 Mar 2009 23:26:11 +0000

[David Allouche (ddaa)]

Reopening this bug for Jaunty because this error happened to me on Jaunty using bzr-gtk 0.96.0.dev.1.

[Steve Langasek (vorlon)]

I can confirm this problem here with current bzr-gtk. It doesn't seem to be a racy issue, though; the first 'bzr vis' failed, and every subsequent one succeeded, so perhaps it's a one-time initialization bug?

[Christian Tschabuschnig (tschaboo)]

Steve, thanks for mentioning that it happens only at the first start. I didn't try it a second time!

[Milan Bouchet-Valat (nalimilan)]

See bug 411533 for a very similar issue with the gnome-sytem-tools.