bzr crashes on bash tab-completion

[Zygmunt Krynicki]

Nuff said, bzr crashes when invoked as `bzr bash-completion`. The backtrace is attached by apport. This happened on precise alpha with bzr 2.5b4

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr 2.5.0~beta4-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.5b4
CommandLine: ['/usr/bin/bzr', 'bash-completion']
CrashDb: bzr
Date: Tue Dec 13 11:17:06 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
Locale: pl_PL.UTF-8
PackageArchitecture: all
Platform: Linux-3.2.0-4-generic-x86_64-with-Ubuntu-12.04-precise
ProcCmdline: /usr/bin/python /usr/bin/bzr bash-completion
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 LANGUAGE=pl
PythonVersion: 2.7.2
SourcePackage: bzr
Title: bzr crashed with KeyError in options(): 'force'
UpgradeStatus: Upgraded to precise on 2011-12-11 (1 days ago)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare sbuild vboxusers wireshark

[Zygmunt Krynicki (zyga)]

This is caused by bzr-git plugin that is packaged in precise right now. With trunk of bzr:bzr-git the crash goes away

[Launchpad Janitor (janitor)]

This bug was fixed in the package bzr-git - 0.6.6-1

---------------
bzr-git (0.6.6-1) unstable; urgency=low

  * Use DEP5 format for copyright file.
  * New upstream release.
   + Copes with new `possible_transports` argument for Branch.open added in
     bzr 2.5b4. Closes: #652178
   + Copes with removal of global options in bzr 2.5b4. LP: #903639
   + Fixes support for directories in `bzr add`. LP: #894195

 -- Jelmer Vernooij <email address hidden> Thu, 15 Dec 2011 19:06:37 +0100

[Tom Haddon (mthaddon)]

I'm getting this in precise currently, with all the latest updates.

[Martin Packman (gz)]

This symptom can also result from other plugins that are expecting certain options to be globally registered, but are no longer in bzr 2.5 or later. Generally making sure all plugins are updated to the latest version should do, if not it needs narrowing down to the particular plugin causing the issue.