"bzr viz" / seahorse interop fails

[Michael B. Trausch]

I have a branch that has signed commits in it, and when I view the branch history using "bzr viz", and click on the "Signature" tab, it hangs for ~20 seconds and then comes back with:

Traceback (most recent call last):
  File "/home/mbt/.bazaar/plugins/gtk/revisionview.py", line 460, in _update_signature
    self.signature_table.set_revision(self._revision)
  File "/home/mbt/.bazaar/plugins/gtk/revisionview.py", line 206, in set_revision
    self.show_signature(crypttext)
  File "/home/mbt/.bazaar/plugins/gtk/revisionview.py", line 225, in show_signature
    (cleartext, key) = seahorse.verify(crypttext)
  File "/home/mbt/.bazaar/plugins/gtk/seahorse.py", line 79, in verify
    (cleartext, key) = crypto.VerifyText(KEY_TYPE_OPENPGP, 1, crypttext)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, 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.

This is bzr 1.9.1 and gtk 0.96.0dev1 (revid <email address hidden>) running on Ubuntu 8.10. The key does exist and works, as demonstrated below. Interesting point of note: If I tell GnuPG to *NOT* trust my key, it (bzr viz) will return immediately with an error saying the key isn't present, even though GnuPG will say it's good when piped to it and just give a warning that the signature is untrusted. If the key is set to ultimate trust, bzr viz hangs when I select the signature tab. If I execute bzr viz via the Nautilus extension, all of Nautilus becomes locked up, as well.

Ubuntu Intrepid:[0-7/10014-0]:gtk> cat | gpg
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

bazaar-ng testament short form 1
revision-id: <email address hidden>
sha1: 28662279311d4951ef7b2f1a34643b432108a356
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkkbAYIACgkQ0kE/IBnFmjDlEACfWWLsxOS2bH8SgqpZz3Louc6p
mogAnRhyfP9u5CEzNmbn88pdonFJAcHX
=00cj
-----END PGP SIGNATURE-----
bazaar-ng testament short form 1
revision-id: <email address hidden>
sha1: 28662279311d4951ef7b2f1a34643b432108a356

gpg: Signature made Wed 12 Nov 2008 11:17:06 AM EST using DSA key ID 19C59A30
gpg: Good signature from "Michael B. Trausch <email address hidden>"
gpg: aka "Michael B. Trausch <email address hidden>"
gpg: aka "Michael B. Trausch (Educational Address) <email address hidden>"
gpg: aka "Michael B. Trausch (Primary Address) <email address hidden>"

To duplicate, create a new empty branch, make a revision or two of changes and additions, run "bzr sign-my-commits", and then run "bzr viz" and click on the signature tab.

[Jelmer Vernooij (jelmer)]

I can't reproduce this with current bzr-gtk. Can you still reproduce it ?

[Stephen Warren (srwarren)]

I can reproduce this fairly often using bzr PPA from today. See also bug 441121, which describes what happens in seahorse after the exception above.

Note that even when I don't receive this exception, "bzr viz" will still never show me signature information.

bzr 1.13.1-1
bzr-dbus 0.1~bzr36-3
bzr-gtk 0.97.0-1~bazaar1~jaunty1
bzrtools 1.13.0-1
seahorse 2.26.1-0ubuntu1
seahorse-plugins 2.26.1-0ubuntu1

[Stephen Warren (srwarren)]

Changing status back to new, since I responded to the request for more information, and evidently forgot to change the state.

[Jelmer Vernooij (jelmer)]

This should be fixed with newer versions of seahorse.