Talk: Skanpage crashes in Fedora 42 KDE because of a missing dependency

[kparal (Kamil Páral)]

This is a discussion topic for the following Common Issue:

Skanpage crashes in Fedora 42 KDE because of a missing dependency

Problem Skanpage, a KDE scanning application, crashes in Fedora 42 KDE due to broken dependencies. This happens both in new and (most) upgraded installs, and on a Live image as well. When Skanpage crashes, you’ll either see a crash report or an SELinux alert: [crash report] [SELinux alert] Cause Skanpage needs another package (tesseract) to run accordingly. This package is not automatically installed with Skanpage due to a packaging error, and it’s also not present on the KDE install image…

You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.

If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.

[kparal (Kamil Páral)]

Please see the Common Issue for solution/workarounds:

Skanpage crashes in Fedora 42 KDE because of a missing dependency

Problem Skanpage, a KDE scanning application, crashes in Fedora 42 KDE due to broken dependencies. This happens both in new and (most) upgraded installs, and on a Live image as well. When Skanpage crashes, you’ll either see a crash report or an SELinux alert: [crash report] [SELinux alert] Cause Skanpage needs another package (tesseract) to run accordingly. This package is not automatically installed with Skanpage due to a packaging error, and it’s also not present on the KDE install image…

[pg-tips (P G)]

What’s the impact of this when upgrading from F41 to F42? After the upgrade, do we need to do something like dnf mark dependency tesseract-libs to prevent the dependency from being autoremoved?

[geraldosimiao (Geraldo Simião Kutz)]

I think this has no impact on system upgrade since you already have tesseract installed on F41 and it belongs to the oficial fedora repo, so it will be upgraded to the f42 version togheter with the rest os the packages.
(edit: I’ll test this scenario on VM for being sure about it)

[pg-tips (P G)]

I agree that it would be upgraded together with the rest of the packages.

My concern is this: what happens if I dnf autoremove after the upgrade?

Package tesseract-libs was originally installed as a dependency of skanpage in F41. But it in F42 it’s (incorrectly) not a dependency of the skanpage package. So would it be eligible for autoremoval?

[geraldosimiao (Geraldo Simião Kutz)]

I’ll test this and post the result here.

(edit)
So I did and the result is this:

• F41 kde have only tesseract-libs togheter with skanpage and this is enought for it to work fine.
• dnf system-upgrade did upgraded correctly tesseract-libs from f41 to the one at f42.
• after reboot, if I run sudo dnf autoremove it doesn’t remove anything related to skanpage or tesseract, so this is not an issue.
• At the upgraded F42 Skanpage crash at start, even with tesseract-libs. But if I install the full tesseract package (the one I pointed at the workarround in this common issues post) then Skanpage starts correctly.

Screenshots showing this:

F41 KDE with working Skanpage

sudo dnf system-upgrade download --releasever=42

sudo dnf autoremove (after F42 reboot)

Skanpage crash

Installing full tesseract package (the workaround)

Now Skanpage starts correctly.

[pg-tips (P G)]

Thanks a lot for testing!

So it’s interesting that there has been a change in what dependencies are actually required (i.e. not just an issue with what the package says it needs). In F41, skanpage needed tesseract-libs, but in F42 it needs the full tesseract.

Still, it’s very easy to fix when you know how, so thanks also for documenting this here!