You are not logged in.

#1 2019-07-13 12:52:10

fleger
Member
Registered: 2018-10-18
Posts: 7

calibre: Segmentation Fault

Hi,

Since the last qt5 update calibre crashes at startup with a Segmentation Fault.

Here's the back trace:

(gdb) run /usr/bin/calibre
Starting program: /usr/bin/python2 /usr/bin/calibre
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0xaee89b40 (LWP 9689)]

Thread 1 "python2" received signal SIGSEGV, Segmentation fault.
0x00001150 in ?? ()
(gdb) bt
#0  0x00001150 in  ()
#1  0xb7fe546c in call_init.part () at /lib/ld-linux.so.2
#2  0xb7fe557a in _dl_init () at /lib/ld-linux.so.2
#3  0xb7fe9228 in dl_open_worker () at /lib/ld-linux.so.2
#4  0xb7f050db in _dl_catch_exception () at /usr/lib/libc.so.6
#5  0xb7fe8a6a in _dl_open () at /lib/ld-linux.so.2
#6  0xb7b8a3cc in  () at /usr/lib/libdl.so.2
#7  0xb7f050db in _dl_catch_exception () at /usr/lib/libc.so.6
#8  0xb7f05194 in _dl_catch_error () at /usr/lib/libc.so.6
#9  0xb7b8abe5 in  () at /usr/lib/libdl.so.2
#10 0xb7b8a46a in dlopen () at /usr/lib/libdl.so.2
#11 0xb3fd2f8b in  () at /usr/lib/libQt5Core.so.5
#12 0xb3fcc51a in  () at /usr/lib/libQt5Core.so.5
#13 0xb3fccb4b in  () at /usr/lib/libQt5Core.so.5
#14 0xb3fc203a in QFactoryLoader::instance(int) const () at /usr/lib/libQt5Core.so.5
#15 0xb3242ce4 in QPlatformThemeFactory::create(QString const&, QString const&) () at /usr/lib/libQt5Gui.so.5
#16 0xb324dcf9 in QGuiApplicationPrivate::createPlatformIntegration() () at /usr/lib/libQt5Gui.so.5
#17 0xb324f6f5 in QGuiApplicationPrivate::createEventDispatcher() () at /usr/lib/libQt5Gui.so.5
#18 0xb3fddef6 in QCoreApplicationPrivate::init() () at /usr/lib/libQt5Core.so.5
#19 0xb3251656 in QGuiApplicationPrivate::init() () at /usr/lib/libQt5Gui.so.5
#20 0xb119340b in QApplicationPrivate::init() () at /usr/lib/libQt5Widgets.so.5
#21 0xb18c6777 in  () at /usr/lib/python2.7/site-packages/PyQt5/QtWidgets.so
#22 0xb18c6869 in  () at /usr/lib/python2.7/site-packages/PyQt5/QtWidgets.so
#23 0xb4762c84 in  () at /usr/lib/python2.7/site-packages/PyQt5/sip.so
#24 0xb7c9cdab in wrapper_call () at /usr/lib/libpython2.7.so.1.0
#25 0xb7cab33a in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#26 0xb7c337e1 in PyEval_CallObjectWithKeywords () at /usr/lib/libpython2.7.so.1.0
#27 0xb7c9d177 in wrapperdescr_call.lto_priv () at /usr/lib/libpython2.7.so.1.0
#28 0xb7cab33a in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#29 0xb7c3a673 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#30 0xb7c340ea in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#31 0xb7c93608 in function_call.lto_priv () at /usr/lib/libpython2.7.so.1.0
#32 0xb7cab33a in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#33 0xb7ca00d2 in instancemethod_call.lto_priv () at /usr/lib/libpython2.7.so.1.0
#34 0xb7cab33a in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#35 0xb7c5b5a4 in slot_tp_init.lto_priv () at /usr/lib/libpython2.7.so.1.0
#36 0xb7c61822 in type_call.lto_priv () at /usr/lib/libpython2.7.so.1.0
#37 0xb7cab33a in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#38 0xb7c3a673 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#39 0xb7c340ea in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#40 0xb7c3acde in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#41 0xb7c340ea in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#42 0xb7c3a821 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#43 0xb7c340ea in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#44 0xb7c3a821 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#45 0xb7c340ea in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#46 0xb7ccc27d in PyEval_EvalCode () at /usr/lib/libpython2.7.so.1.0
#47 0xb7cc548a in run_mod () at /usr/lib/libpython2.7.so.1.0
#48 0xb7cc5526 in PyRun_FileExFlags () at /usr/lib/libpython2.7.so.1.0
#49 0xb7cc5e04 in PyRun_SimpleFileExFlags () at /usr/lib/libpython2.7.so.1.0
#50 0xb7cc0cff in Py_Main () at /usr/lib/libpython2.7.so.1.0
#51 0x00401076 in main ()

Could this be a problem with python2-pyqt5?

I'm using the pentium4 repos and my DE is KDE Plasma.

Offline

#2 2019-07-13 18:16:03

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 815
Website

Re: calibre: Segmentation Fault

Confirmed. And its /usr/bin/python2 called by calibre, which is segfaulting. Maybe a Qt/Python binding issue..

Offline

#3 2019-07-14 06:50:53

fleger
Member
Registered: 2018-10-18
Posts: 7

Re: calibre: Segmentation Fault

FYI this is still happening with 3.44.0-3.0.

Offline

#4 2019-07-14 07:56:44

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 815
Website

Re: calibre: Segmentation Fault

Also a rebuild issue around Qt and python2 (though Qt should depend actually on Python).

Offline

#5 2019-09-17 13:28:15

jonathon
Member
From: UK
Registered: 2017-07-19
Posts: 39
Website

Re: calibre: Segmentation Fault

The current sticking point is this build chain:

sip -> pyqt5 -> calibre

SIP needs rebuilding for 4.19.19, which allows pyqt5 5.13.1 to build, which allows calibre to build.

Offline

Board footer

Powered by FluxBB