calibre-parallel crashed with SIGSEGV

Bug #1429876 reported by J on 2015-03-09
This bug affects 3 people
Affects Status Importance Assigned to Milestone
calibre (Ubuntu)

Bug Description


ProblemType: Crash
DistroRelease: Ubuntu 15.04
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 9 10:51:30 2015
Disassembly: => 0x7f5d965ef0b9: No se puede acceder a la memoria en la dirección 0x7f5d965ef0b9
ExecutablePath: /usr/bin/calibre-parallel
InstallationDate: Installed on 2014-10-24 (136 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/calibre-parallel
 PATH=(custom, no user)
 Segfault happened at: 0x7f5d965ef0b9: No se puede acceder a la memoria en la dirección 0x7f5d965ef0b9
 PC (0x7f5d965ef0b9) not located in a known VMA region (needed executable region)!
 source "0x7f5d965ef0b9" (0x7f5d965ef0b9) not located in a known VMA region (needed readable region)!
 Stack memory exhausted (SP below stack segment)
 executing unknown VMA
 reading unknown VMA
Signal: 11
SourcePackage: calibre
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: calibre-parallel crashed with SIGSEGV
UpgradeStatus: Upgraded to vivid on 2015-01-05 (62 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

J (jsartti) wrote :
information type: Private → Public

 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in calibre (Ubuntu):
status: New → Confirmed
Changed in calibre (Ubuntu):
importance: Undecided → Medium
freikland (freikland) wrote :

it affects me, on Ubuntu 16.04.
"calibre-parallel crashed with SIGSEGV".
This happens when you open a book in the template reader. The bug occurs when you exit.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers