calibre crashed with SIGSEGV in QAbstractEventDispatcherPrivate::allocateTimerId()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calibre (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was also running a large copy job with nemo.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: calibre 3.21.0+dfsg-1
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 11 16:31:34 2018
ExecutablePath: /usr/bin/calibre
InstallationDate: Installed on 2018-03-26 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python2.7 /usr/bin/calibre
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
SegvAnalysis:
Segfault happened at: 0x7fc47ab439a1 <_ZN31QAbstract
PC (0x7fc47ab439a1) ok
source "0x0(%r13)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%r12d" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: calibre
StacktraceTop:
QAbstractEvent
QAbstractEvent
QObject:
QTimer::start() () from /usr/lib/
QNetworkConfig
Title: calibre crashed with SIGSEGV in QAbstractEventD
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare 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 #1729262, 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.