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

[Brian Rowe]

Binary package hint: bzr

I had just run bzr launchpad-login.

It appears that this crash resulted from a connection timeout. My network has been slow recently, so this could have been a legitimate timeout. That said, I don't think this should have crashed bzr.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bzr 2.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
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', 'launchpad-login', 'briprowe']
CrashDb: bzr
Date: Sat Mar 26 22:10:19 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
Locale: en_US.UTF-8
Platform: Linux-2.6.38-7-generic-x86_64-with-Ubuntu-11.04-natty
ProcCmdline: /usr/bin/python /usr/bin/bzr launchpad-login briprowe
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
PythonVersion: 2.7.1
SourcePackage: bzr
Title: bzr crashed with error in _curl_perform(): (28, 'SSL connection timeout at 294540')
UpgradeStatus: Upgraded to natty on 2011-03-24 (2 days ago)
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.