bzr crashed with UnicodeDecodeError in write_revision_to_string(): 'ascii' codec can't decode byte 0xe2 in position 4759: ordinal not in range(128)

[Jeremy Bícha]

I think this might be because I tried to commit too much at once. A second try also failed but when I shelved some of the changes, I was able to commit the unshelved and then the shelved changes.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bzr 2.4.0-3ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.4.0
CommandLine: ['/usr/bin/bzr', 'commit']
CrashDb: bzr
Date: Fri Sep 2 05:12:41 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InterpreterPath: /usr/bin/python2.7
Locale: en_US.UTF-8
PackageArchitecture: all
Platform: Linux-3.0.0-9-generic-x86_64-with-Ubuntu-11.10-oneiric
ProcCmdline: /usr/bin/python /usr/bin/bzr commit
PythonVersion: 2.7.2
SourcePackage: bzr
Title: bzr crashed with UnicodeDecodeError in write_revision_to_string(): 'ascii' codec can't decode byte 0xe2 in position 4759: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Martin Packman (gz)]

The problem appears to be with the commit message you provided. What mechanism did you use to add it? Was a template supplied by or plugin, or did you type it into your default editor, and what exactly was it? Did any of the files you were adding have non-ascii names?

If you try adding a new set of changes with the same commit message as before, can you reproduce the problem?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jelmer Vernooij (jelmer)]

Resetting this to incomplete - if you are also hitting this, please provide more information. See comment #2.

[Launchpad Janitor (janitor)]

[Expired for Bazaar because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for bzr (Ubuntu) because there has been no activity for 60 days.]

[Martin Packman (gz)]

This appears to be from having bzr-builddeb 2.7.0dev which is quite old, mixed with a newer bzr version. The builddeb issue was fixed in bug 853664 and released in 2.7.9 but that's not backported to oneiric.