bzr crashed with TooManyConcurrentRequests in __init__()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bzr (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: bzr
Got this error when working with a checkout of lp:~jderose/dmedia/thumbnail-improvements
Tried to make a commit, this error occurs. Tried to make commit a few more times, same error each time. Seems like it might actually be a Launchpad availability problem causing it, but if so, bzr should fail gracefully with a friendly error about Lauchpad being out for a cup of tea. :)
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: bzr 2.2.1-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.2.1
CheckboxSubmission: fdbdfcded0c0bb4
CheckboxSystem: edda5d4f616ca79
CommandLine:
['/usr/bin/bzr',
'commit',
'-m',
'Now again storing canon.thm file in _attachments, where it will stay']
CrashDb: bzr
Date: Thu Nov 11 07:11:45 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
Locale: en_US.UTF-8
Platform: Linux-2.
ProcCmdline: /usr/bin/python /usr/bin/bzr commit -m Now\ again\ storing\ canon.thm\ file\ in\ _attachments,\ where\ it\ will\ stay
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
PythonVersion: 2.6.6
SourcePackage: bzr
Title: bzr crashed with TooManyConcurre
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
| Jason Gerard DeRose (jderose) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
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 #635917, 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.