bzr crashed with error in _curl_perform(): (28, 'SSL connection timeout at 298169')

[TeliuTe]

bzr launchpad-login teliute
bzr: ERROR: pycurl.error: (28, 'SSL connection timeout at 298169')

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 i686
Architecture: i386
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', 'launchpad-login', 'teliute']
CrashDb: bzr
Date: Thu Jun 23 23:53:10 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
Locale: zh_CN.utf8
PackageArchitecture: all
Platform: Linux-2.6.38-8-generic-i686-with-Ubuntu-11.04-natty
ProcCmdline: /usr/bin/python /usr/bin/bzr launchpad-login username
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=zh_CN.utf8
 LANGUAGE=zh_CN:en
PythonVersion: 2.7.1
SourcePackage: bzr
Title: bzr crashed with error in _curl_perform(): (28, 'SSL connection timeout at 298169')
UpgradeStatus: No upgrade log present (probably fresh install)
UserEncoding: UTF-8
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 #722043, 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.