Activity log for bug #562758

Date Who What changed Old value New value Message
2010-04-14 03:40:22 PresuntoRJ bug added bug
2010-04-14 03:40:22 PresuntoRJ attachment added Dependencies.txt http://launchpadlibrarian.net/44111410/Dependencies.txt
2010-04-14 03:40:22 PresuntoRJ attachment added ProcMaps.txt http://launchpadlibrarian.net/44111411/ProcMaps.txt
2010-04-14 03:40:22 PresuntoRJ attachment added ProcStatus.txt http://launchpadlibrarian.net/44111412/ProcStatus.txt
2010-04-14 03:40:22 PresuntoRJ attachment added Traceback.txt http://launchpadlibrarian.net/44111413/Traceback.txt
2010-04-14 05:17:02 Apport retracing service tags apport-crash i386 lucid need-duplicate-check apport-crash i386 lucid
2011-04-12 07:38:02 Martin Pool description Binary package hint: bzr I was trying to verify a gpg signature in a previous commit inside the log browser using $ bzr vis When I have clicked in the Signature tab bzr frooze for a while (went all gray in my screen) and when it woke up, there was a python error message in my shell and the GUI was alive again, although it have not shown up any values for Key ID, Fingerprint or Trust. Apport kicked in sending this repport It happens every time I try it Buy the waym is there any other method of checking the gpg signature of a commit ? ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: bzr 2.1.1-1 ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic i686 Architecture: i386 Date: Wed Apr 14 00:33:17 2010 ExecutablePath: /usr/bin/bzr InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4) InterpreterPath: /usr/bin/python2.6 ProcCmdline: /usr/bin/python /usr/bin/bzr vis ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=pt_BR.utf8 LANGUAGE=pt_BR:en_US:en PythonArgs: ['/usr/bin/bzr', 'vis'] SourcePackage: bzr Title: bzr crashed with DBusException in call_blocking() UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video Binary package hint: bzr I was trying to verify a gpg signature in a previous commit inside the log browser using $ bzr vis When I have clicked in the Signature tab bzr frooze for a while (went all gray in my screen) and when it woke up, there was a python error message in my shell and the GUI was alive again, although it have not shown up any values for Key ID, Fingerprint or Trust. Apport kicked in sending this repport It happens every time I try it Buy the waym is there any other method of checking the gpg signature of a commit ? ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: bzr 2.1.1-1 ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic i686 Architecture: i386 Date: Wed Apr 14 00:33:17 2010 ExecutablePath: /usr/bin/bzr InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4) InterpreterPath: /usr/bin/python2.6 ProcCmdline: /usr/bin/python /usr/bin/bzr vis ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=pt_BR.utf8 LANGUAGE=pt_BR:en_US:en PythonArgs: ['/usr/bin/bzr', 'vis'] SourcePackage: bzr Title: bzr crashed with DBusException in call_blocking() UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video 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 83, in verify keyset[key] = Key(key) File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/seahorse.py", line 99, in __init__ fields = openpgp.GetKeyFields(key, ['fingerprint', 'trust', 'flags', 'display-name', 'location']) 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) 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.
2011-04-12 07:55:22 Martin Pool visibility private public
2011-04-12 07:59:41 Martin Pool marked as duplicate 730058