ebook-viewer crashed with SIGSEGV in QAbstractEventDispatcherPrivate::allocateTimerId()

[emk2203]

calibre tried to open a .txt file and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: calibre 3.14.0+dfsg-1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: LXQt
Date: Mon Jan 22 16:39:02 2018
ExecutablePath: /usr/bin/ebook-viewer
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/ebook-viewer /home/username/tmp/Pihole\ Repair.txt
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f90311d08a1 <_ZN31QAbstractEventDispatcherPrivate15allocateTimerIdEv+65>: mov 0x0(%r13),%r12d
 PC (0x7f90311d08a1) 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:
 QAbstractEventDispatcherPrivate::allocateTimerId() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QAbstractEventDispatcher::registerTimer(int, Qt::TimerType, QObject*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QObject::startTimer(int, Qt::TimerType) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QTimer::start() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QNetworkConfigurationManagerPrivate::startPolling() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
Title: ebook-viewer crashed with SIGSEGV in QAbstractEventDispatcherPrivate::allocateTimerId()
UpgradeStatus: Upgraded to bionic on 2017-06-03 (233 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video

[Apport retracing service (apport)]

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 #1733240, 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.