Bug 497709 - Skanpage crashes on startup
Summary: Skanpage crashes on startup
Status: RESOLVED WORKSFORME
Alias: None
Product: Skanpage
Classification: Applications
Component: general (show other bugs)
Version: 24.12.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Alexander Stippich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-20 09:33 UTC by MK
Modified: 2025-01-19 03:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MK 2024-12-20 09:33:09 UTC
SUMMARY
Skanpage crashes at startup with the following error:
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
  what():  filesystem error: recursive directory iterator cannot open directory: File o directory non esistente [/usr/share/tessdata/]
KCrash: Application 'skanpage' crashing... crashRecursionCounter = 2


STEPS TO REPRODUCE
1. Be on latest Tumbleweed
2. Try running Skanpage

OBSERVED RESULT
App collapses at startup

EXPECTED RESULT
App starts correctly and is usable

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20241218
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: LENOVO
Product Name: 20FB002UMS
System Version: ThinkPad X1 Carbon 4th
Comment 1 Nate Graham 2024-12-20 19:16:41 UTC
Can you paste the output of `/usr/share/tessdata/` run in a terminal window?

Also, please attach a backtrace of the crash; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Thanks!
Comment 2 Bug Janitor Service 2025-01-04 03:47:33 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-01-19 03:47:44 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.