calibre crashed with SIGSEGV in QObject::connect()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calibre (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Calibre crashed on startup.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: calibre 0.9.41+dfsg-1
ProcVersionSign
Uname: Linux 3.11.0-3-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Fri Aug 23 23:49:43 2013
ExecutablePath: /usr/bin/calibre
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python2.7 /usr/bin/calibre
SegvAnalysis:
Segfault happened at: 0x7f0708a73bd8: mov (%rax),%edx
PC (0x7f0708a73bd8) ok
source "(%rax)" (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/
QObject:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: calibre crashed with SIGSEGV in QObject::connect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
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 #1216549, 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.