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

[Gonzalo Bulnes Guilpain]

I was running: $ bzr launchpad-login gonzalo-bulnes

$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

$ apt-cache policy bzr
bzr:
  Installed: 2.3.4-0ubuntu1
  Candidate: 2.3.4-0ubuntu1
  Version table:
 *** 2.3.4-0ubuntu1 0
        500 http://mirror.netlinux.cl/ubuntu/ natty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.3.1-1ubuntu1 0
        500 http://mirror.netlinux.cl/ubuntu/ natty/main amd64 Packages

I was expecting to be asked for my launchpad password, or maybe launchpad-login to be set without asking for any password.
Instead of that, bzr crashed and suggested to report this bug.

Best regards,
--
Gonzalo Bulnes

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bzr 2.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.3.4
CommandLine: ['/usr/bin/bzr', 'launchpad-login', 'gonzalo-bulnes']
CrashDb: bzr
Date: Wed Sep 7 01:15:56 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
InterpreterPath: /usr/bin/python2.7
Locale: es_CL.UTF-8
PackageArchitecture: all
Platform: Linux-2.6.38-11-generic-x86_64-with-Ubuntu-11.04-natty
ProcCmdline: /usr/bin/python /usr/bin/bzr launchpad-login username-bulnes
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LC_MESSAGES=en_US.UTF-8
 LANG=es_CL.UTF-8
 LANGUAGE=en
PythonVersion: 2.7.1
SourcePackage: bzr
Title: bzr crashed with error in _curl_perform(): (28, 'SSL connection timeout at 289622')
UpgradeStatus: No upgrade log present (probably fresh install)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout libvirtd 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.