calibre crashed with SIGSEGV in indexOfMethodRelative<4>()

[Barry Drake]

This occurred directly after yesterday's updates to Saucy. There was no update to Calbre itself, so this will be a problem with an updated library of which there were several.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: calibre 0.9.41+dfsg-1
ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic i686
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
Date: Sun Aug 25 12:23:03 2013
ExecutablePath: /usr/bin/calibre
InstallationDate: Installed on 2013-05-13 (103 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: 0xb5355a37: mov (%eax),%edx
 PC (0xb5355a37) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: calibre
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
 ?? () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
 ?? () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
Title: calibre crashed with SIGSEGV in QObject::connect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lp lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 indexOfMethodRelative<4> (normalizeStringData=<optimized out>, method=<optimized out>, baseObject=<optimized out>) at kernel/qmetaobject.cpp:525
 QMetaObjectPrivate::indexOfSignalRelative (baseObject=0xbf829804, signal=0xb5655142 "destroyed(QObject *)", normalizeStringData=false) at kernel/qmetaobject.cpp:628
 QObject::connect (sender=0xadf5ef8, signal=0xb5655142 "destroyed(QObject *)", receiver=0xae0b978, method=0xb5655136 "1disable()", type=Qt::QueuedConnection) at kernel/qobject.cpp:2553
 PyQtProxy::init(QObject*, QMultiHash<void*, PyQtProxy*>*, void*) () from /tmp/apport_sandbox_FXKZUY/usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
 PyQtProxy::PyQtProxy(qpycore_pyqtBoundSignal*, _object*, char const**) () from /tmp/apport_sandbox_FXKZUY/usr/lib/python2.7/dist-packages/PyQt4/QtCore.so

[Launchpad Janitor (janitor)]

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

[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