Bug 498138 - bzr viz always fails first attempt, succeeds second
bzr viz always fails first attempt, succeeds second
Product: Fedora
Classification: Fedora
Component: bzr-gtk (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Toshio Ernie Kuratomi
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-28 23:17 EDT by Warren Togami
Modified: 2009-11-11 11:43 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-11-11 11:43:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 377476 None None None Never

  None (edit)
Description Warren Togami 2009-04-28 23:17:28 EDT
[warren@newcaprica ltsp-trunk]$ rpm -qa 'bzr*'
[warren@newcaprica ltsp-trunk]$ bzr info
Standalone tree (format: pack-0.92)
  branch root: .

Related branches:
    push branch: bzr+ssh://wtogami@bazaar.launchpad.net/%7Eltsp-upstream/ltsp/ltsp-trunk/
  parent branch: bzr+ssh://wtogami@bazaar.launchpad.net/%7Eltsp-upstream/ltsp/ltsp-trunk/
[warren@newcaprica ltsp-trunk]$ bzr viz
/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/ui.py:224: DeprecationWarning: bzrlib.progress.ProgressBarStack was deprecated in version 1.12.
  self._progress_bar_stack = progress.ProgressBarStack(klass=widget)
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/lib64/python2.6/site-packages/bzrlib/commands.py", line 727, in exception_to_return_code
    return the_callable(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/bzrlib/commands.py", line 922, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib64/python2.6/site-packages/bzrlib/commands.py", line 559, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/__init__.py", line 288, in run
    pp = start_viz_window(br, revids, limit)
  File "/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/__init__.py", line 256, in start_viz_window
    from bzrlib.plugins.gtk.viz import BranchWindow
  File "/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/viz/__init__.py", line 14, in <module>
    from branchwin import BranchWindow
  File "/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/viz/branchwin.py", line 18, in <module>
    from bzrlib.plugins.gtk.tags import AddTagDialog
  File "/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/tags.py", line 27, in <module>
    from bzrlib.plugins.gtk.revisionview import RevisionView
  File "/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/revisionview.py", line 32, in <module>
    from bzrlib.plugins.gtk import seahorse
  File "/usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk/seahorse.py", line 33, in <module>
    crypto = dbus.Interface(bus.get_object(BUS_NAME, CRYPTO_PATH),
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0

bzr 1.14rc1 on python 2.6 (linux2)
arguments: ['/usr/bin/bzr', 'viz']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.utf8'
  gtk                  /usr/lib64/python2.6/site-packages/bzrlib/plugins/gtk [0.95.0.final.1]
  launchpad            /usr/lib64/python2.6/site-packages/bzrlib/plugins/launchpad [unknown]
  netrc_credential_store /usr/lib64/python2.6/site-packages/bzrlib/plugins/netrc_credential_store [unknown]
*** 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.
Comment 1 Toshio Ernie Kuratomi 2009-04-29 13:22:58 EDT
I'm not able to reproduce this.  It works for me with seahorse installed and uninstalled.  When seahorse-daemon is running or not running.  To see if seahorse is a red herring could you try:

  $ ps aux |grep warren > before-fail.log
  $ bzr viz
  $ ps aux |grep warren > after-fail.log
  $ bzr viz
  $ ps aux | grep warren > after-success.log

If I'm right we'll see that seahorse-daemon is not running in the before-fail case and then it will be in one of the after cases.  I'm curious to know whether it's started by the time we get to after-fail or not until after-success.  Also if there's anything other process that gets started in the meantime... Maybe dbus itself is having to start?

Versions of dbus and seahorse here are:
Comment 2 Toshio Ernie Kuratomi 2009-05-26 11:12:58 EDT
This looks like the upstream bug.  Trying the patch proposed here:
Comment 3 Toshio Ernie Kuratomi 2009-05-27 13:57:24 EDT
Built for RawHide.  Leaving this open until we see if upstream comes up with what the problem is:

Comment 4 Bug Zapper 2009-06-09 10:44:36 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 5 Toshio Kuratomi 2009-07-27 16:21:53 EDT
Looks like when upstream figured out that it's a bug in seahorse, they reverted the workaround in bzr-gtk.  Warren will try the patch in the seahorse bug http://bugzilla.gnome.org/show_bug.cgi?id=583356

If that works, we can see if the seahorse maintainer would be willing to inlude it in a bugfix release.
Comment 6 Warren Togami 2009-11-11 11:43:35 EST
Fixed in F-12

Note You need to log in before you can comment on or make changes to this bug.