calibre crashed with SIGSEGV in PyEval_EvalFrameEx()

[JAP]

1) Ubuntu 11.04
2) Calibre 0.7.44
3) Change categories.
4) Crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: calibre 0.7.44+dfsg-1build1
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Mon Oct 10 11:25:27 2011
ExecutablePath: /usr/bin/calibre
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/calibre
ProcEnviron:
 LANGUAGE=de:en_GB:en
 LANG=es_MX.UTF-8
 LC_MESSAGES=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80da844 <PyEval_EvalFrameEx+852>: mov 0x70(%ecx),%eax
 PC (0x080da844) ok
 source "0x70(%ecx)" (0x00000070) 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:
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
 ?? ()
 PyObject_Call ()
 PyEval_EvalFrameEx ()
Title: calibre crashed with SIGSEGV in PyEval_EvalFrameEx()
UpgradeStatus: Upgraded to natty on 2011-07-11 (91 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare tape video

[Launchpad Janitor (janitor)]

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

---------------
calibre (2.0.0+dfsg-1) unstable; urgency=medium

  * New upstream release. (Closes: #759246)
  * Adjust debian/rules get-orig-source for slightly changed upstream tarball
    layout.
  * This version uses Qt5 now. Close all crashes which are related to Qt4.
    (Closes: #673598, #609705) (LP: #1294989, #1074796, #1038931, #1021047,
    #976305, #967316, #958282, #939788, #930445, #927641, #925777, #891924,
    #886504, #871883, #854417, #852624, #762931, #762643, #761719, #745176,
    #720028, #701129, #696077, #659806, #565377, #565366, #565178, #563585,
    #557883, #458403, #1216549, #1051759, #1027371, #720021, #556985, #555961)
  * Adjust build and binary dependencies for the Qt 4 → 5 change.

 -- Martin Pitt <email address hidden> Tue, 26 Aug 2014 20:43:13 +0200