bzr crashed with ErrorFromSmartServer in _translate_error(): Error received from smart server: ('error', "bytes must be a string, got <type 'bzrlib._static_tuple_c.StaticTuple'>")

[James Gregory-Monk]

I am trying to checkout a project from a shared Bazaar repository, but I am receiving the following error (after entering my username and password):

bzr: ERROR: bzrlib.errors.ErrorFromSmartServer: Error received from smart server: ('error', "bytes must be a string, got <type 'bzrlib._static_tuple_c.StaticTuple'>")

I have seen other reports with this error message, but they talk about inclusions of Subversions repositories and the such like. I'm not sure that that is the case here (the stack trace returned is different anyway).

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bzr 2.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.3.1
CommandLine: ['/usr/bin/bzr', 'checkout', 'gs:dev4-dls/trunk']
CrashDb: bzr
Date: Mon Jul 25 12:59:57 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
Locale: en_GB.UTF-8
PackageArchitecture: all
Platform: Linux-2.6.38-10-generic-x86_64-with-Ubuntu-11.04-natty
ProcCmdline: /usr/bin/python /usr/bin/bzr checkout gs:dev4-dls/trunk
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
PythonVersion: 2.7.1
SourcePackage: bzr
Title: bzr crashed with ErrorFromSmartServer in _translate_error(): Error received from smart server: ('error', "bytes must be a string, got <type 'bzrlib._static_tuple_c.StaticTuple'>")
UpgradeStatus: No upgrade log present (probably fresh install)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Martin Packman (gz)]

This is likely to be the same issue as the existing reports, but the circumstances it happens under are still mysterious. If you could check the server .bzr.log for the traceback there, and add any further insight to the main bug, that may be helpful.

[James Gregory-Monk (jamgregory)]

I believe this issue is actually related to bug #656178, and a problem in the bzr extension _chk_map_pyx.

[Martin Packman (gz)]

You're right that bug 656178 is about the same issue, but that bug entry has been closed since the improved error message was added, and further work is happening in the newer bug.

[Launchpad Janitor (janitor)]

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