calibre crashed with SIGSEGV in PyObject_Call()

Bug #1221120 reported by Barry Drake
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Had just shut Calibre down after importing a new book and downloading metadata for it. Shutdown seemed normal until the crash message. I was not running Calibre through the command line so can offer no more information. Calibre had not been working (reported crash on startup) until a couple of days ago when Calibre was included in the Ubuntu 13.10 updates.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: calibre 1.0.0+dfsg-1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Thu Sep 5 09:18:14 2013
ExecutablePath: /usr/bin/calibre
InstallationDate: Installed on 2013-05-13 (114 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130511)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/calibre
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8118bb3 <PyObject_Call+19>: mov 0x4(%esi),%eax
 PC (0x08118bb3) ok
 source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: calibre
StacktraceTop:
 PyObject_Call ()
 ?? () from /usr/lib/python2.7/dist-packages/lxml/etree.so
 ?? () from /usr/lib/python2.7/dist-packages/lxml/etree.so
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
Title: calibre crashed with SIGSEGV in PyObject_Call()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lp lpadmin plugdev sambashare sudo

Revision history for this message
Barry Drake (b-drake) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 PyObject_Call (func=0x0, arg=arg@entry=0xaf9958c, kw=kw@entry=0x0) at ../Objects/abstract.c:2525
 __pyx_f_4lxml_5etree__hasEncodingDeclaration (__pyx_v_xml_string=0x94395f0) at src/lxml/lxml.etree.c:18270
 __pyx_f_4lxml_5etree__parseMemoryDocument (__pyx_v_text=__pyx_v_text@entry=0x94395f0, __pyx_v_url=__pyx_v_url@entry=0x8335ae4 <_Py_NoneStruct>, __pyx_v_parser=0x8335ae4 <_Py_NoneStruct>) at src/lxml/lxml.etree.c:27180
 __pyx_pf_4lxml_5etree_22fromstring (__pyx_self=0x0, __pyx_v_base_url=0x8335ae4 <_Py_NoneStruct>, __pyx_v_parser=<optimized out>, __pyx_v_text=0x94395f0) at src/lxml/lxml.etree.c:62980
 __pyx_pw_4lxml_5etree_23fromstring (__pyx_self=0x0, __pyx_args=0x935d5cc, __pyx_kwds=0x0) at src/lxml/lxml.etree.c:62932

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in calibre (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package calibre - 1.0.0+dfsg-1build1

---------------
calibre (1.0.0+dfsg-1build1) saucy; urgency=low

  * No change rebuild to deal with sip4 issues (LP: #1221120)
 -- Scott Kitterman <email address hidden> Mon, 14 Oct 2013 14:36:27 -0400

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.