Hello,
I've got a PDF (boarding passes) that causes KPDF to crash (SIGSEV signal 11). Other PDFs print fine, that particular one can be printed from qpdfview, or will print correctly from KPDF only after having been printed to pdf from master pdf editor.
I've got the gdb crash report, it is quite long and I am not sure if there would be something to bebug and where I could (should) post it. Here is the start that seems to relate to TDe libraries:
[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
==== (gdb) bt ==== [TDECrash handler] #6 0x00007f488b5ad785 in FoFiType1C::convertToType0(char*, void (*)(void*, char*, int), void*) () from /opt/trinity/lib/trinity/libkpdfpart.so #7 0x00007f488b542ee5 in PSOutputDev::setupEmbeddedCIDType0Font(GfxFont*, Ref*, GString*) () from /opt/trinity/lib/trinity/libkpdfpart.so #8 0x00007f488b54d523 in PSOutputDev::setupFont(GfxFont*, Dict*) () from /opt/trinity/lib/trinity/libkpdfpart.so #9 0x00007f488b54d8c8 in PSOutputDev::setupFonts(Dict*) () from /opt/trinity/lib/trinity/libkpdfpart.so #10 0x00007f488b54d9bf in PSOutputDev::setupResources(Dict*) () from /opt/trinity/lib/trinity/libkpdfpart.so #11 0x00007f488b54dddb in PSOutputDev::writeDocSetup(Catalog*, int, int) () from /opt/trinity/lib/trinity/libkpdfpart.so #12 0x00007f488b54f1d3 in PSOutputDev::init(void (*)(void*, char*, int), void*, PSFileType, XRef*, Catalog*, int, int, PSOutMode, int, int, int, int, int) () from /opt/trinity/lib/trinity/libkpdfpart.so #13 0x00007f488b54f4a8 in PSOutputDev::PSOutputDev(char*, XRef*, Catalog*, int, int, PSOutMode, int, int, int, int, int, int) () from /opt/trinity/lib/trinity/libkpdfpart.so #14 0x00007f488b50c2f5 in PDFGenerator::print(KPrinter&) () from /opt/trinity/lib/trinity/libkpdfpart.so #15 0x00007f488b4cf160 in KPDF::Part::doPrint(KPrinter&) () from /opt/trinity/lib/trinity/libkpdfpart.so #16 0x00007f488b4d1b31 in KPDF::Part::slotPrint() () from /opt/trinity/lib/trinity/libkpdfpart.so #17 0x00007f488b4d1be8 in KPDF::Part::tqt_invoke(int, TQUObject*) () from /opt/trinity/lib/trinity/libkpdfpart.so #18 0x00007f48916cebeb in TQObject::activate_signal(TQConnectionList*, TQUObject*) () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #19 0x00007f4891970781 in TQSignal::signal(TQVariant const&) () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #20 0x00007f48916e2a30 in TQSignal::activate() () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #21 0x00007f48916ed790 in ?? () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #22 0x00007f489167fa17 in TQApplication::internalNotify(TQObject*, TQEvent*) () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #23 0x00007f48916769a8 in TQEventLoop::activateTimers() () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #24 0x00007f4891663725 in TQEventLoop::gsourceDispatch(_GSource*) () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #25 0x00007f4891663803 in ?? () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #26 0x00007f4890c66789 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f4890c66a18 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f4890c66aac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f4891662d6b in TQEventLoop::processEvents(unsigned int) () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #30 0x00007f4891691981 in TQEventLoop::enterLoop() () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #31 0x00007f4891691919 in TQEventLoop::exec() () from /lib/x86_64-linux-gnu/libtqt-mt.so.3 #32 0x00005647e22fa686 in ?? () #33 0x00007f489124524a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #34 0x00007f4891245305 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #35 0x00005647e22fac81 in ?? ()
Thierry
On 2026/10/03 09:29 PM, Thierry de Coulon via tde-users wrote:
Hello,
I've got a PDF (boarding passes) that causes KPDF to crash (SIGSEV signal 11). Other PDFs print fine, that particular one can be printed from qpdfview, or will print correctly from KPDF only after having been printed to pdf from master pdf editor.
Thierry
Hi Thierry, we have a fix for this ready, thanks to Seb Guerra. Any chance you can share the PDF document for us to test and make sure it really resolves the problem? If it is not confidential, that is. Thanks Michele
On Wednesday 07 October 2026 06:11:10 Michele Calgaro via tde-users wrote:
Hi Thierry, we have a fix for this ready, thanks to Seb Guerra. Any chance you can share the PDF document for us to test and make sure it really resolves the problem? If it is not confidential, that is. Thanks Michele
Not that confidential, but I'd rather not post it here yet. So either I can send it to someone directly, or we can wait (three weeks) and I can post them here with no problem as they will have been used.
Thierry
Not that confidential, but I'd rather not post it here yet. So either I can send it to someone directly, or we can wait (three weeks) and I can post them here with no problem as they will have been used.
Hi Thierry, if you are ok to send it to either me or Seb directly, we can do a test. If not, we can still merge the fix and you will find out in R14.1.7 if it works or not. 3 weeks later is too late for us because we are freezing R14.1.7 development next week.
Either way it will be ok for us, you make the call whether you want the fix tested on your pdf or you want to wait and test yourself after R14.1.7 is out.
Cheers Michele
On 10/6/26 9:11 PM, Michele Calgaro via tde-users wrote:
we have a fix for this ready, thanks to Seb Guerra. Any chance you can share the PDF document for us to test and make sure it really resolves the problem? If it is not confidential, that is.
I have a number of PDFs that cause the same problem Thierry is having. They're mostly old books from Google Books and archive.org. Most books are fine, and the few that have the problem are mostly fine, but have one specific page that crashes kpdf. Would it be helpful to have those to test? Some of the PDFs are quite large, but I can easily burst out the offending pages and send only them. (I've tried it before, and those pages still cause the problem when they're burst out into individual PDFs.)
I have a number of PDFs that cause the same problem Thierry is having. They're mostly old books from Google Books and archive.org. Most books are fine, and the few that have the problem are mostly fine, but have one specific page that crashes kpdf. Would it be helpful to have those to test? Some of the PDFs are quite large, but I can easily burst out the offending pages and send only them. (I've tried it before, and those pages still cause the problem when they're burst out into individual PDFs.) ____________________________________________________
Hi Dan, I have got Thierry's pdf, so I will do a test later today. But it won't hurt to try out yours as well. There were a number of issues with kpdf and thanks to Seb's work we have fixed several ones for R14.1.7, so it will be good to do a bit more testing. Thanks for reaching out on this. Cheers Michele
-
Dan Youngquist -
Michele Calgaro -
Thierry de Coulon