calibre-parallel crashed with SIGSEGV

Bug #1428126 reported by J on 2015-03-04

This bug report will be marked for expiration in 6 days if no further activity occurs. (find out why)

12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre (Ubuntu)
Undecided
Unassigned

Bug Description

none

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: Wed Mar 4 11:15:54 2015
Disassembly: => 0x7f30b85370b9: No se puede acceder a la memoria en la dirección 0x7f30b85370b9
ExecutablePath: /usr/bin/calibre-parallel
InstallationDate: Installed on 2014-10-24 (130 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
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_UY.UTF-8
 SHELL=/bin/bash
 LANGUAGE=es_UY:es
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f30b85370b9: No se puede acceder a la memoria en la dirección 0x7f30b85370b9
 PC (0x7f30b85370b9) not located in a known VMA region (needed executable region)!
 source "0x7f30b85370b9" (0x7f30b85370b9) not located in a known VMA region (needed readable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing unknown VMA
 reading unknown VMA
Signal: 11
SourcePackage: calibre
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: calibre-parallel crashed with SIGSEGV
UpgradeStatus: Upgraded to vivid on 2015-01-05 (57 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

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

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
gf (gf-interlinks) wrote :

Hello J,
Thank you for submitting this bug and reporting a problem with Calibre. You made this bug report some time ago and Ubuntu and Calibre have been updated since then.

Could you confirm that this is no longer a problem and that we can close the ticket?
If it is still a problem, are you still interested in finding a solution to this bug?
If you are, could you let us know and, in the current version, could you run the following (only once):
apport-collect 1428126
and upload the updated logs and and any other logs that are relevant for this particular issue.

Thank you again for helping make Ubuntu and Calibre better.
G

Changed in calibre (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers