Comment 4 for bug 562758

there was a seahorse-daemon process that went berzerk with this crash (using at least 74% of my CPU time) which goes on with every crash and I have to kill manully

this is what I have found on my /var/log/auth.log

Apr 14 00:28:44 eee-u seahorse-daemon[2764]: init gpgme version 1.2.0
Apr 14 00:30:43 eee-u seahorse-daemon[2764]: Cannot marshal type "SeahorseLocation" in variant
Apr 14 00:31:14 eee-u seahorse-daemon[2764]: last message repeated 49324 times
Apr 14 00:31:50 eee-u seahorse-daemon[2764]: last message repeated 57234 times
Apr 14 00:31:50 eee-u seahorse-daemon[2764]: left gtk_main
Apr 14 00:32:24 eee-u seahorse-daemon[2790]: init gpgme version 1.2.0
Apr 14 00:32:52 eee-u seahorse-daemon[2790]: Cannot marshal type "SeahorseLocation" in variant
Apr 14 00:33:53 eee-u seahorse-daemon[2790]: last message repeated 92092 times
Apr 14 00:34:54 eee-u seahorse-daemon[2790]: last message repeated 90792 times
Apr 14 00:35:55 eee-u seahorse-daemon[2790]: last message repeated 85122 times
Apr 14 00:36:56 eee-u seahorse-daemon[2790]: last message repeated 65578 times
Apr 14 00:37:57 eee-u seahorse-daemon[2790]: last message repeated 65555 times
Apr 14 00:38:58 eee-u seahorse-daemon[2790]: last message repeated 63916 times
Apr 14 00:39:59 eee-u seahorse-daemon[2790]: last message repeated 63525 times
Apr 14 00:41:00 eee-u seahorse-daemon[2790]: last message repeated 63420 times
Apr 14 00:42:01 eee-u seahorse-daemon[2790]: last message repeated 85668 times
Apr 14 00:43:02 eee-u seahorse-daemon[2790]: last message repeated 101611 times
Apr 14 00:44:03 eee-u seahorse-daemon[2790]: last message repeated 100003 times
Apr 14 00:45:04 eee-u seahorse-daemon[2790]: last message repeated 97615 times
Apr 14 00:46:05 eee-u seahorse-daemon[2790]: last message repeated 85017 times
Apr 14 00:47:06 eee-u seahorse-daemon[2790]: last message repeated 91545 times
Apr 14 00:48:07 eee-u seahorse-daemon[2790]: last message repeated 88705 times
Apr 14 00:48:07 eee-u seahorse-daemon[2790]: last message repeated 1580 times
Apr 14 00:48:07 eee-u seahorse-daemon[2790]: left gtk_main

and this is what the bzr vis echoed as stdout on the shell I was running during the crash:

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/revisionview.py", line 486, in _switch_page_cb
    self.signature_table.set_revision(self._revision)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/revisionview.py", line 210, in set_revision
    self.show_signature(crypttext)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/revisionview.py", line 229, in show_signature
    (cleartext, key) = seahorse.verify(crypttext)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/seahorse.py", line 79, in verify
    (cleartext, key) = crypto.VerifyText(KEY_TYPE_OPENPGP, 1, crypttext)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, 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.