FS#41620 - [calibre] Crash on startup

Attached to Project: Community Packages
Opened by Bogdan Szczurek (thebodzio) - Monday, 18 August 2014, 23:41 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 04 October 2014, 15:18 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Right after start calibre dies with the error report presented below. This behaviour started with the switch from “release” to “beta” line of calibre.

Additional info:
* calibre 1.206.1-1
* python2 2.7.8-1

calibre-debug -g gives:

calibre 1.206.1 isfrozen: False is64bit: True
Linux-3.16.1-1-ARCH-x86_64-with-glibc2.2.5 Linux ('64bit', 'ELF')
('Linux', '3.16.1-1-ARCH', '#1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014')
Python 2.7.8
Linux: ('', '', '')
Successfully initialized third party plugins: Find Duplicates
*** Error in `python2': free(): invalid pointer: 0x00007fe905fc5be0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x73f8e)[0x7fe921a6bf8e]
/usr/lib/libc.so.6(+0x7988e)[0x7fe921a7188e]
/usr/lib/libc.so.6(+0x7a04b)[0x7fe921a7204b]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x55d8f)[0x7fe905f87d8f]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x575b8)[0x7fe905f895b8]
/usr/lib/libQt5Gui.so.5(+0x1aa2f6)[0x7fe917d352f6]
/usr/lib/libQt5Gui.so.5(_ZN13QFontDatabase8findFontEiPK12QFontPrivateRK8QFontDefb+0xb65)[0x7fe917d37bc5]
/usr/lib/libQt5Gui.so.5(_ZN13QFontDatabase4loadEPK12QFontPrivatei+0x7be)[0x7fe917d384ee]
/usr/lib/libQt5Gui.so.5(_ZNK12QFontPrivate15engineForScriptEi+0x79)[0x7fe917d13b89]
/usr/lib/libQt5Gui.so.5(_ZNK9QFontInfo6familyEv+0x14)[0x7fe917d140a4]
/usr/lib/python2.7/site-packages/PyQt5/QtGui.so(+0x1cb35d)[0x7fe91848835d]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5ff8)[0x7fe9220a2a18]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7fe9220a33c0]
/usr/lib/libpython2.7.so.1.0(+0x6e06d)[0x7fe92203206d]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7fe92200e4c3]
/usr/lib/libpython2.7.so.1.0(+0x58a9d)[0x7fe92201ca9d]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7fe92200e4c3]
/usr/lib/libpython2.7.so.1.0(+0x9e2d7)[0x7fe9220622d7]
/usr/lib/libpython2.7.so.1.0(+0x9d05f)[0x7fe92206105f]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7fe92200e4c3]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3a5d)[0x7fe9220a047d]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x552a)[0x7fe9220a1f4a]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7fe9220a33c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x541e)[0x7fe9220a1e3e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7fe9220a33c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x541e)[0x7fe9220a1e3e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7fe9220a33c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7fe9220a34b9]
/usr/lib/libpython2.7.so.1.0(+0xf801f)[0x7fe9220bc01f]
/usr/lib/libpython2.7.so.1.0(PyRun_FileExFlags+0x72)[0x7fe9220bd192]
/usr/lib/libpython2.7.so.1.0(PyRun_SimpleFileExFlags+0xd7)[0x7fe9220be297]
/usr/lib/libpython2.7.so.1.0(Py_Main+0xc3a)[0x7fe9220cf15a]
/usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7fe921a18000]
python2[0x40073e]

-- lenghty memory map follows --

Steps to reproduce:
Start calibre
This task depends upon

Closed by  Jelle van der Waa (jelly)
Saturday, 04 October 2014, 15:18 GMT
Reason for closing:  Not a bug
Additional comments about closing:  fontconfig config
Comment by Doug Newgard (Scimmia) - Tuesday, 19 August 2014, 03:53 GMT
It's running fine here and for many others. Can you try `calibre --ignore-plugins`?
Comment by Bogdan Szczurek (thebodzio) - Tuesday, 19 August 2014, 08:51 GMT
Unfortunately “calibre --ignore-plugins” leads to the same crash. I also tried backing up the config (~/.config/calibre to ~/.config/calibre.backup) and running calibre then, but the result was exactly the same.

Reinstalling packages involved in backtrace (glibc, qt5-base, python2-pyqt5 and python2) was also to no avail.
Comment by Jelle van der Waa (jelly) - Saturday, 23 August 2014, 09:36 GMT
CAlibre 2.0 is now released, is this still a problem?
Comment by Bogdan Szczurek (thebodzio) - Saturday, 23 August 2014, 18:11 GMT
I was hoping the new version will work, but… nope :{ – unfortunately the same crash as before:

*** Error in `python2': free(): invalid pointer: 0x00007f6d723e7be0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x73f8e)[0x7f6d8d536f8e]
/usr/lib/libc.so.6(+0x7988e)[0x7f6d8d53c88e]
/usr/lib/libc.so.6(+0x7a04b)[0x7f6d8d53d04b]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x55d8f)[0x7f6d723a9d8f]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x575b8)[0x7f6d723ab5b8]
/usr/lib/libQt5Gui.so.5(+0x1aa2f6)[0x7f6d83c5b2f6]
/usr/lib/libQt5Gui.so.5(_ZN13QFontDatabase8findFontEiPK12QFontPrivateRK8QFontDefb+0xb65)[0x7f6d83c5dbc5]
/usr/lib/libQt5Gui.so.5(_ZN13QFontDatabase4loadEPK12QFontPrivatei+0x7be)[0x7f6d83c5e4ee]
/usr/lib/libQt5Gui.so.5(_ZNK12QFontPrivate15engineForScriptEi+0x79)[0x7f6d83c39b89]
/usr/lib/libQt5Gui.so.5(_ZNK9QFontInfo6familyEv+0x14)[0x7f6d83c3a0a4]
/usr/lib/python2.7/site-packages/PyQt5/QtGui.so(+0x1cb35d)[0x7f6d843ae35d]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5ff8)[0x7f6d8db6da18]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7f6d8db6e3c0]
/usr/lib/libpython2.7.so.1.0(+0x6e06d)[0x7f6d8dafd06d]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7f6d8dad94c3]
/usr/lib/libpython2.7.so.1.0(+0x58a9d)[0x7f6d8dae7a9d]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7f6d8dad94c3]
/usr/lib/libpython2.7.so.1.0(+0x9e2d7)[0x7f6d8db2d2d7]
/usr/lib/libpython2.7.so.1.0(+0x9d05f)[0x7f6d8db2c05f]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7f6d8dad94c3]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3a5d)[0x7f6d8db6b47d]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x552a)[0x7f6d8db6cf4a]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7f6d8db6e3c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x541e)[0x7f6d8db6ce3e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7f6d8db6e3c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7f6d8db6e4b9]
/usr/lib/libpython2.7.so.1.0(+0xf801f)[0x7f6d8db8701f]
/usr/lib/libpython2.7.so.1.0(PyRun_FileExFlags+0x72)[0x7f6d8db88192]
/usr/lib/libpython2.7.so.1.0(PyRun_SimpleFileExFlags+0xd7)[0x7f6d8db89297]
/usr/lib/libpython2.7.so.1.0(Py_Main+0xc3a)[0x7f6d8db9a15a]
/usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7f6d8d4e3000]
python2[0x40073e]

and so on…
Comment by Oscar Alonso (jester400) - Saturday, 23 August 2014, 22:04 GMT
I have a similar problem even with the last version.

If I run calibre using the shorcut the aplication doesn't work.
dmesg show me this message:
python2[2055]: segfault at dfda00 ip b739d745 sp ab396060 error 4 in libc-2.19.so[b732b000+1bb000]

if I run the aplication from a terminal writing: calibre-debug -g
calibre 2.0 isfrozen: False is64bit: False
Linux-3.16.1-1-ARCH-i686-with-glibc2.0 Linux ('32bit', 'ELF')
('Linux', '3.16.1-1-ARCH', '#1 SMP PREEMPT Thu Aug 14 07:48:39 CEST 2014')
Python 2.7.8
Linux: ('', '', '')
Starting up...
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Started up in 1.22 seconds with 19 books
----------------------
With calibre-debug -g the application seems works ok.
Comment by Bogdan Szczurek (thebodzio) - Friday, 29 August 2014, 22:42 GMT
Another version (2.1.0), another fail:

*** Error in `python2': free(): invalid pointer: 0x00007faf1fd2fbe0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x73f8e)[0x7faf3ac76f8e]
/usr/lib/libc.so.6(+0x7988e)[0x7faf3ac7c88e]
/usr/lib/libc.so.6(+0x7a04b)[0x7faf3ac7d04b]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x55d8f)[0x7faf1fcf1d8f]
/usr/lib/qt/plugins/platforms/libqxcb.so(+0x575b8)[0x7faf1fcf35b8]
/usr/lib/libQt5Gui.so.5(+0x1aa2f6)[0x7faf3139b2f6]
/usr/lib/libQt5Gui.so.5(_ZN13QFontDatabase8findFontEiPK12QFontPrivateRK8QFontDefb+0xb65)[0x7faf3139dbc5]
/usr/lib/libQt5Gui.so.5(_ZN13QFontDatabase4loadEPK12QFontPrivatei+0x7be)[0x7faf3139e4ee]
/usr/lib/libQt5Gui.so.5(_ZNK12QFontPrivate15engineForScriptEi+0x79)[0x7faf31379b89]
/usr/lib/libQt5Gui.so.5(_ZNK9QFontInfo6familyEv+0x14)[0x7faf3137a0a4]
/usr/lib/python2.7/site-packages/PyQt5/QtGui.so(+0x1cb35d)[0x7faf31aee35d]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5ff8)[0x7faf3b2ada18]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7faf3b2ae3c0]
/usr/lib/libpython2.7.so.1.0(+0x6e06d)[0x7faf3b23d06d]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faf3b2194c3]
/usr/lib/libpython2.7.so.1.0(+0x58a9d)[0x7faf3b227a9d]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faf3b2194c3]
/usr/lib/libpython2.7.so.1.0(+0x9e2d7)[0x7faf3b26d2d7]
/usr/lib/libpython2.7.so.1.0(+0x9d05f)[0x7faf3b26c05f]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faf3b2194c3]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3a5d)[0x7faf3b2ab47d]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x552a)[0x7faf3b2acf4a]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7faf3b2ae3c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x541e)[0x7faf3b2ace3e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7faf3b2ae3c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x541e)[0x7faf3b2ace3e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x830)[0x7faf3b2ae3c0]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7faf3b2ae4b9]
/usr/lib/libpython2.7.so.1.0(+0xf801f)[0x7faf3b2c701f]
/usr/lib/libpython2.7.so.1.0(PyRun_FileExFlags+0x72)[0x7faf3b2c8192]
/usr/lib/libpython2.7.so.1.0(PyRun_SimpleFileExFlags+0xd7)[0x7faf3b2c9297]
/usr/lib/libpython2.7.so.1.0(Py_Main+0xc3a)[0x7faf3b2da15a]
/usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7faf3ac23000]
python2[0x40073e]
Comment by Oscar Alonso (jester400) - Sunday, 31 August 2014, 22:52 GMT
The last version seems to fix my problems.
Comment by Bogdan Szczurek (thebodzio) - Sunday, 31 August 2014, 23:41 GMT
Moments ago I did some digging and testing and found the problem. The offending piece was… fontconfig settings! In my home directory I've had some old ~/.config/fontconfig/fonts.conf file in which I turned off hinting. The thing is I did that with value “none” instead of “hintnone”. IIRC the former was proper when I was doing that. Then I didn't pay much attention to changes in fontconfig configuration syntax and… there you go! Anyway, I don't think such misconfiguration should have so great impact on an app, but that's something for the Calibre/QT projects to worry about ;)

To sum things up: changing

<match target="font">
<edit mode="assign" name="hintstyle">
<const>none</const>
</edit>
</match>

to

<match target="font">
<edit mode="assign" name="hintstyle">
<const>hintnone</const>
</edit>
</match>

fixed the problem completely for me, so I'm providing this solution as a reference for other unfortunate souls around ;}.

As for the bug, I think it can be safely closed. A big TY for all the participants in this discussion!

Loading...