calibre crashed with SIGSEGV in initpictureflow()

Bug #923289 reported by Michał Pławsiuk (razit.pl)
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre (Ubuntu)
New
Undecided
Unassigned

Bug Description

I can't open Calibre. When I want open I see error :)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: calibre 0.8.34+dfsg-1
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Jan 29 11:14:04 2012
ExecutablePath: /usr/bin/calibre
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/calibre
ProcEnviron:
 PATH=(custom, no user)
 LC_MESSAGES=pl_PL.UTF-8
 LANG=pl_PL.UTF-8
 LANGUAGE=pl:en
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0a21d55e28: addq $0x1,(%rax)
 PC (0x7f0a21d55e28) ok
 source "$0x1" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: calibre
StacktraceTop:
 ?? () from /usr/lib/python2.7/dist-packages/sip.so
 ?? () from /usr/lib/python2.7/dist-packages/sip.so
 initpictureflow () from /usr/lib/calibre/calibre/plugins/pictureflow.so
 _PyImport_LoadDynamicModule ()
 ?? ()
Title: calibre crashed with SIGSEGV in initpictureflow()
UpgradeStatus: Upgraded to precise on 2012-01-27 (2 days ago)
UserGroups:

Revision history for this message
Michał Pławsiuk (razit.pl) (mp3-10) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #922368, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.