| Summary: | ghostscript --with-tesseract crashes digiKam on startup | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | antikapitalista |
| Component: | Plugin-DImg-Magick | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REOPENED --- | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 7.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
antikapitalista
2022-08-09 10:00:15 UTC
The bug title indicates that you didn't install GDB in 64 bit. Can you have a similar problem with ImageMagick? The crash occurs in ImageMagick and is also unknown until now. Maik Perhaps a mixing 32 and 64 bits binaries ? Gilles Well, I put this here as a sort of placeholder, because it looks really weird. An even weirder thing is that this was a native build in a pure amd64 system, no multilib. I am going to rebuild binutils, binutils-libs and gdb with the multitarget USE flag disabled, as it is not needed anyway. QTWEBENGINE_DISABLE_SANDBOX=1 fixed it for me. Alright, you can close it. At first, I was perplexed because it was crashing all the time but often at different places. So i rebuilt digiKam with almost everything turned off, then it began crashing rather consistently at the same place. And then I noticed the message that it did not like running as UID=0 (root) without --no-sandbox. Thus, QtWebEngine was exiting and letting the rest of digiKam implode. At first it was crashing at seemingly random places; digKam being multithreaded, the first victim was essentially a random thread that wanted to have something to do with QtWebEngine, which had crapped out. It is broken by design and digiKam is its innocent victim. I am awfully sorry to have wasted your time. It has been my fault all along. Perhaps I spake too early... ImageMagick was still crashing it; more specifically: ImageMagick configured --with-gslib and linked to ghostscript-gpl-9.55. (In reply to antikapitalista from comment #5) > Perhaps I spake too early... > > ImageMagick was still crashing it; more specifically: ImageMagick configured > --with-gslib and linked to ghostscript-gpl-9.55... ... and still more specifically, digiKam crashes with versions of >=ghostscript-gpl-9.54 ; versions of <=ghostscript-9.53.3 work as expected. It crash in 32 bits HDRI version of imagemagick. For the digiKam bundle we disable HDRI support in IM : https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_imagemagick/CMakeLists.txt#L26 It's probably a UPSTREAM bug in IM code. Gilles Caulier The culprit is Ghostscript configured --with-tesseract, while ImageMagick is configured with --with-gslib. That is why the conflict appears only in release packages of Ghostscript, which additionally bundle Tesseract (and Leptonica). For ImageMagick configured --with-gslib, Ghostscript must either be configured --without-tesseract, or its source tree have the tesseract directory deleted before building. (In reply to caulier.gilles from comment #7) > It crash in 32 bits HDRI version of imagemagick. > > For the digiKam bundle we disable HDRI support in IM : > > https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/ > 3rdparty/ext_imagemagick/CMakeLists.txt#L26 > > It's probably a UPSTREAM bug in IM code. > > Gilles Caulier It is a conflict caused by Ghostscript. Otherwise everything seems to work with external ImageMagick with all its options enabled -- except autotrace, of course -- which appears to be some ancient abandoned piece of software with a cross-dependence on older versions of ImageMagick and I am not even sure that it is still actually supported in ImageMagick. @antikapitalista@pobox.sk digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier antikapitalista@pobox.sk, What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Thanks in advance Gilles Caulier @antikapitalista, digiKam 8.3.0 stable version is released and available at usual place : https://www.digikam.org/download/ Can you reproduce the dysfunction on your computer ? Thanks in advance Gilles Caulier |