UnicodeDecodeError in smart_add(), current filesystem encoding ANSI_X3.4-1968
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bzr
Using 'etckeeper'.
Subsequent errors may be instructive.
etckeeper warning: bzr add failed
bzr: warning: unsupported locale setting
bzr could not set the application locale.
Although this should be no problem for bzr itself, it might
cause problems with some plugins. To investigate the issue,
look at the output of the locale(1p) tool.
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_MESSAGES = "en_US.UTF-8",
LANG = "en_US"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Committing to: /etc/
aborting commit write group: BadFilenameEnco
bzr: ERROR: Filename 'ssl/certs/
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bzr 2.4.0~beta2-
ProcVersionSign
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
BzrDebugFlags: set()
BzrVersion: 2.4b2
CommandLine: ['/usr/bin/bzr', 'add', '-q', '.']
CrashDb: bzr
Date: Mon Jun 13 18:07:31 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: ANSI_X3.4-1968
InterpreterPath: /usr/bin/python2.7
Locale: en_US
PackageArchitec
Platform: Linux-2.
ProcCmdline: /usr/bin/python /usr/bin/bzr add -q .
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US
LC_MESSAGES=
SHELL=/bin/bash
PythonVersion: 2.7.2
SourcePackage: bzr
Title: bzr crashed with UnicodeDecodeError in smart_add(): 'ascii' codec can't decode byte 0xc5 in position 28: ordinal not in range(128)
UpgradeStatus: Upgraded to oneiric on 2010-04-01 (438 days ago)
UserEncoding: ANSI_X3.4-1968
UserGroups:
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.