calibre crashed with SIGSEGV

Bug #556985 reported by Michael Terry
210
This bug affects 18 people
Affects Status Importance Assigned to Milestone
calibre (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: calibre

Occurred when I closed calibre for the first time (after importing some ebooks and playing around with it).

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: calibre 0.6.42+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Tue Apr 6 21:33:48 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/calibre
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: python /usr/bin/calibre
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: calibre
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
 ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
 ?? () from /usr/lib/pymodules/python2.6/sip.so
 ?? () from /usr/lib/pymodules/python2.6/sip.so
Title: calibre crashed with SIGSEGV
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Revision history for this message
Michael Terry (mterry) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 subtype_dealloc (self=0x6fe4ff4)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
visibility: public → private
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in calibre (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in calibre (Ubuntu):
status: Confirmed → 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.