bzr crashed with UnicodeDecodeError in smart_add(): 'ascii' codec can't decode byte 0xc3 in position 11: ordinal not in range(128)

[Olaf Gladis]

Binary package hint: bzr

I have to files with a false filename encoding in a folder.

I would expect, that those files would not be added instead of crashing.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bzr 2.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
BzrDebugFlags: set()
BzrPlugins:
 bash_completion /usr/lib/python2.7/dist-packages/bzrlib/plugins/bash_completion [2.3.1]
   bzrtools /usr/lib/python2.7/dist-packages/bzrlib/plugins/bzrtools [2.3.1]
   launchpad /usr/lib/python2.7/dist-packages/bzrlib/plugins/launchpad [2.3.1]
   netrc_credential_store /usr/lib/python2.7/dist-packages/bzrlib/plugins/netrc_credential_store [2.3.1]
   news_merge /usr/lib/python2.7/dist-packages/bzrlib/plugins/news_merge [2.3.1]
BzrVersion: 2.3.1
CommandLine: ['/usr/bin/bzr', 'add', '--dry-run']
CrashDb: bzr
Date: Sat Jun 18 10:49:24 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: ANSI_X3.4-1968
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
Locale:

PackageArchitecture: all
Platform: Linux-2.6.38-8-generic-x86_64-with-Ubuntu-11.04-natty
ProcCmdline: /usr/bin/python /usr/bin/bzr add --dry-run
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=
 LANGUAGE=
PythonVersion: 2.7.1
SourcePackage: bzr
Title: bzr crashed with UnicodeDecodeError in smart_add(): 'ascii' codec can't decode byte 0xc3 in position 11: ordinal not in range(128)
UpgradeStatus: Upgraded to natty on 2011-05-18 (31 days ago)
UserEncoding: ANSI_X3.4-1968
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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 #790268, 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.