bzr crashed with error in _curl_perform(): (28, 'SSL connection timeout at 298225') connecting to Launchpad
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Medium
|
Unassigned | ||
Launchpad itself |
Invalid
|
Critical
|
Unassigned | ||
bzr (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned | ||
Oneiric |
Invalid
|
Medium
|
Unassigned | ||
curl (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Won't Fix
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bzr
Running
$ bzr get https:/
gives me a big traceback and doesn't work. Not sure if the problem is on the launchpad side or not, but even if it is, bzr should probably just print an error message rather than crashing.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bzr 2.3.0-2
ProcVersionSign
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
BzrDebugFlags: set()
BzrPlugins:
bash_completion /usr/lib/
bzrtools /usr/lib/
launchpad /usr/lib/
netrc_
news_merge /usr/lib/
BzrVersion: 2.3.0
CommandLine:
['/usr/bin/bzr',
'get',
'https:/
CrashDb: bzr
Date: Wed Mar 16 09:30:55 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101206)
InterpreterPath: /usr/bin/python2.7
Locale: en_US.UTF-8
Platform: Linux-2.
ProcCmdline: /usr/bin/python /usr/bin/bzr get https:/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
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 298225')
UpgradeStatus: Upgraded to natty on 2011-03-09 (6 days ago)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
return self._operation
File "/usr/lib/
self.cleanups, self.func, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
from_location)
File "/usr/lib/
bzrdir = klass.open(
File "/usr/lib/
return BzrDir.
File "/usr/lib/
redirected)
File "/usr/lib/
return obj(*args, **kwargs)
File "/usr/lib/
return action(transport)
File "/usr/lib/
transport, _server_
File "/usr/lib/
return prober.
File "/usr/lib/
server_version = medium.
File "/usr/lib/
client_
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
data = self._medium.
File "/usr/lib/
code, body_filelike = t._post(bytes)
File "/usr/lib/
'Content-Type: application/
File "/usr/lib/
curl.perform()
error: (28, 'SSL connection timeout at 298225')
tags: | removed: need-duplicate-check |
description: | updated |
visibility: | private → public |
Changed in bzr: | |
status: | New → Confirmed |
Changed in bzr (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in bzr: | |
importance: | Undecided → Medium |
tags: | added: error-reporting https |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in bzr (Ubuntu Natty): | |
status: | New → Incomplete |
status: | Incomplete → Invalid |
Changed in bzr (Ubuntu Maverick): | |
status: | New → Invalid |
Changed in bzr (Ubuntu): | |
status: | Triaged → Invalid |
Changed in curl (Ubuntu): | |
status: | New → In Progress |
Changed in curl (Ubuntu Maverick): | |
status: | New → In Progress |
Changed in curl (Ubuntu Natty): | |
status: | New → In Progress |
Changed in bzr: | |
status: | Confirmed → Invalid |
tags: | added: bugpattern-needed |
bzr should not give a traceback for a network error.
As far as the error itself:
1- some users may be firewalled or need a proxy; in that case we'd expect it to fail consistently
2- bzr or a library may be doing something strange that makes failures more likely (perhaps the timeout is unreasonably short?)
3- Launchpad may not be accepting the connection fast enough, and therefore it is a real timeout that they could potentially fix