calibre-parallel crashed with error in connect()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| calibre (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: calibre
Yet another Calibre crash. I'm on Maverick with latest updates, and last night I set up Calibre to bulk convert 200 comics files to ePub. after EVERY file, I would get a crash message saying that calibre-parallel crashed with some error. I ignored those and let it run overnight.
This morning, I found that the majority of my conversions failed to happen because of calibre-parallel crashes. Apparently, when the instance crashes, the system still thinks it's running, even though it's dead and gone. SO, at some point, calibre starts saying "Maximum number of instances reached". I had to close out well over 130 of those windows, and however man of the crash message windows this morning to get rid of them all.
Calibre fires off an apport report for every instance that is not cleanly exiting.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: calibre 0.7.18+dfsg-1
ProcVersionSign
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Mar 2 00:41:08 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python2.6 /usr/bin/
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: calibre
Title: calibre-parallel crashed with error in connect()
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare vboxusers
| Jeff Lane (bladernr) 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 #646897, 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.