[Linux] Calibre 2.73 crashing on exit - python2 segmentation fault

[lesterf]

Running 2.73 on Manjaro Linux.

The application runs fine, but on exit python2 crashes.

The same crash occurs when closing the Calibre e-book reader application too.

What processing occurs on exit for these applications?

Here is the output running calibre in debug mode from CLI, I close Calibre straight away to trigger the segfault and associationed coredump.

$ calibre-debug -g
calibre 2.73  embedded-python: False is64bit: True
Linux-4.8.12-1-MANJARO-x86_64-with-glibc2.2.5 Linux ('64bit', '')
('Linux', '4.8.12-1-MANJARO', '#1 SMP PREEMPT Fri Dec 2 20:03:35 UTC 2016')
Python 2.7.12
Linux: ('', '', '')
Successfully initialized third party plugins: Reading List (1, 6, 6) && Kindle Collections (1, 7, 17) && Count Pages (1, 6, 9)
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.2526315789
physicalDpi: 128.336842105 x 130.628571429
Starting up...
Failed to read metadata from font file: /usr/share/fonts/TTF/TSCu_Comic.ttf tuple index out of range
Failed to read metadata from font file: /usr/share/fonts/TTF/TSCu_Times.ttf tuple index out of range
Started up in 1.52 seconds with 2012 books
Segmentation fault (core dumped)

Here are the log messages for the associated python2 segfault.

systemd-coredump[9411]: Process 9350 (python2) of user 1000 dumped core.

Stack trace of thread 9358:
#0  0x00007f62a73f89cf _ZN7QObject10disconnectEPKS_PKcS
#1  0x00007f62a28c7530 n/a (libQt5DBus.so.5)
#2  0x00007f62a28b3f62 n/a (libQt5DBus.so.5)
#3  0x00007f62a71eed78 n/a (libQt5Core.so.5)
#4  0x00007f62b47dc454 start_thread (libpthread.so.0)
#5  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9357:
#0  0x00007f62b451648d poll (libc.so.6)
#1  0x00007f62a4b2f8e0 n/a (libxcb.so.1)
#2  0x00007f62a4b31679 xcb_wait_for_event (libxcb.so.1)
#3  0x00007f628b5ce449 n/a (libQt5XcbQpa.so.5)
#4  0x00007f62a71eed78 n/a (libQt5Core.so.5)
#5  0x00007f62b47dc454 start_thread (libpthread.so.0)
#6  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9350:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f62a71efc2b _ZN14QWaitCondition4waitEP6QMute
#2  0x00007f62a71ee91e _ZN7QThread4waitEm (libQt5Core.s
#3  0x00007f62a28b3cc6 n/a (libQt5DBus.so.5)
#4  0x00007f62a28b3d59 n/a (libQt5DBus.so.5)
#5  0x00007f62b446c990 __run_exit_handlers (libc.so.6)
#6  0x00007f62b446c9ea exit (libc.so.6)
#7  0x00007f62b4afba32 Py_Exit (libpython2.7.so.1.0)
#8  0x00007f62b4afbb89 handle_system_exit.part.2 (libpy
#9  0x00007f62b4afbe0d PyErr_PrintEx (libpython2.7.so.1
#10 0x00007f62b4afca74 PyRun_SimpleFileExFlags (libpyth
#11 0x00007f62b4b0f0c0 Py_Main (libpython2.7.so.1.0)
#12 0x00007f62b4457291 __libc_start_main (libc.so.6)
#13 0x000056272fc437ea _start (python2.7)

Stack trace of thread 9369:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629eb7a40b n/a (libQt5WebKit.so.5)
#2  0x00007f629eb7a449 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9376:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629e8721d1 n/a (libQt5WebKit.so.5)
#2  0x00007f629ebab5b1 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9377:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629e873323 n/a (libQt5WebKit.so.5)
#2  0x00007f629ebab5b1 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9378:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629e873323 n/a (libQt5WebKit.so.5)
#2  0x00007f629ebab5b1 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9379:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629e873323 n/a (libQt5WebKit.so.5)
#2  0x00007f629ebab5b1 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9380:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629e873323 n/a (libQt5WebKit.so.5)
#2  0x00007f629ebab5b1 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9381:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629e873323 n/a (libQt5WebKit.so.5)
#2  0x00007f629ebab5b1 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9382:
#0  0x00007f62b47e210f pthread_cond_wait@@GLIBC_2.3.2 (
#1  0x00007f629e873323 n/a (libQt5WebKit.so.5)
#2  0x00007f629ebab5b1 n/a (libQt5WebKit.so.5)
#3  0x00007f62b47dc454 start_thread (libpthread.so.0)
#4  0x00007f62b451f7df __clone (libc.so.6)

Stack trace of thread 9375:
#0  0x00007f62b451648d poll (libc.so.6)
#1  0x00007f62aa097786 n/a (libglib-2.0.so.0)
#2  0x00007f62aa09789c g_main_context_iteration (libgli
#3  0x00007f62a741d70f _ZN20QEventDispatcherGlib13proce
#4  0x00007f62a73c723a _ZN10QEventLoop4execE6QFlagsINS_
#5  0x00007f62a71ea0f3 _ZN7QThread4execEv (libQt5Core.s
#6  0x00007f62a71eed78 n/a (libQt5Core.so.5)
#7  0x00007f62b47dc454 start_thread (libpthread.so.0)
#8  0x00007f62b451f7df __clone (libc.so.6)

Any ideas what could be causing this? Any more info I could provide to assist? Are there Calibre application logs with more info?

Apologies if this thread was created in the wrong location, first post.

[kovidgoyal]

This is caused by a bug in PyQt, search the PyQT mailing lists for crash on exit where I reported this issue a couple of years ago. It will likely go away automatically once X11 is retired (the crash occurs in the Qt XCB module).

[lesterf]

Thanks for the response.

Seems this crash is not happening for other Manjaro users trying to recreate the issue by installing Calibre, launching it, then closing it. Is there a reason for this? I'm using latest KDE version, built on Qt, so I'm wondering if this is a DE thing.

So there is basically nothing do be done until the underlying PyQt bug is resolved?

[kovidgoyal]

Assuming it is the same crash then yes there is nothing to be done.

[lesterf]

I'm trying to work out why Calibre crashes every single close on my system, but for other Manjaro users it does not seem to crash.

Im a little bit OCD when it comes to regular segfaults and coredumps.

I have ReadingList, Collections, and CountPages plugins installed, could this have play a role in increased crash frequency?

[BetterRed]

@lesterf - try the ignore-plugins switch ==>> calibre command

BR

[lesterf]

Thanks, but no dice.

$ calibre --ignore-plugins
Segmentation fault (core dumped)

[kovidgoyal]

Looking at the stack trace it is related to DBUS, the crash is happening in the QtDBDUS module -- so it is not the same crash as I mentioned previously (that happens in QXcbEventReader)

[compurandom]

Missing font?