bzr crashed with KeyError in annotate(): u'current:/home/User Name/nux'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bzr
I just installed bazaar-explorer asked to open a anotate and it crashed with following errors:
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/usr/lib/
return f(*args, **kargs)
File "/usr/lib/
self.
File "/usr/lib/
rev = gv.revid_rev[revid]
KeyError: u'current:
bzr 2.3.1 on python 2.7.1 (linux2)
arguments: ['/usr/bin/bzr', 'explorer']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'eu_ES.UTF-8'
plugins:
bash_completion /usr/lib/
builddeb /usr/lib/
bzrtools /usr/lib/
explorer /usr/lib/
launchpad /usr/lib/
netrc_
news_merge /usr/lib/
qbzr /usr/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bzr 2.3.1-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelMo
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.3.1
CommandLine: ['/usr/bin/bzr', 'explorer']
CrashDb: bzr
Date: Sun Jun 12 21:56:40 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100919)
InterpreterPath: /usr/bin/python2.7
Locale: eu_ES.UTF-8
PackageArchitec
Platform: Linux-2.
ProcCmdline: /usr/bin/python /usr/bin/bzr explorer
ProcEnviron:
SHELL=/bin/bash
LANG=eu_ES.UTF-8
LANGUAGE=eu_ES:en
PythonVersion: 2.7.1
SourcePackage: bzr
Title: bzr crashed with KeyError in annotate(): u'current:
UpgradeStatus: Upgraded to natty on 2011-05-18 (25 days ago)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #794608, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.