SUMMARY I installed the flatpak version on Garuda linux got an error STEPS TO REPRODUCE 1. flatpak install itinerary (install) 2. flatpak run org.kde.itinerary OBSERVED RESULT has portal: true QQmlApplicationEngine failed to load component qrc:/main.qml:311:9: Type App.BarcodeScannerPage unavailable qrc:/BarcodeScannerPage.qml:11:1: plugin cannot be loaded for module "org.kde.prison.scanner": Cannot load library /usr/lib/qml/org/kde/prison/scanner/libprisonscannerquickplugin.so: (/usr/lib/x86_64-linux-gnu/libKF5PrisonScanner.so.5: undefined symbol: _ZN5ZXing11ReadBarcodeERKNS_9ImageViewERKNS_13ReaderOptionsE) EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.6.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 62,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION
Just an fyi, if I install the package version, that does work
A possibly relevant merge request was started @ https://invent.kde.org/pim/itinerary/-/merge_requests/262
Git commit a637744a176eb8f89c01189a0115b1393cb57cc6 by Volker Krause. Committed on 15/01/2024 at 17:44. Pushed by vkrause into branch 'master'. Build ZXing statically to avoid clashing with the one in the platform The org.kde.Platform contains an internal dynamically linked ZXing, if our version differs in an ABI-incompatible way things break. Avoid that by linking our one statically into KItinerary, the only place needing it here. M +1 -1 .flatpak-manifest.json https://invent.kde.org/pim/itinerary/-/commit/a637744a176eb8f89c01189a0115b1393cb57cc6
A possibly relevant merge request was started @ https://invent.kde.org/pim/itinerary/-/merge_requests/264
Git commit dc8bebdf031c26219ac17264d077ad3ffc82b199 by Volker Krause. Committed on 17/01/2024 at 17:53. Pushed by vkrause into branch 'release/23.08'. Build ZXing statically to avoid clashing with the one in the platform The org.kde.Platform contains an internal dynamically linked ZXing, if our version differs in an ABI-incompatible way things break. Avoid that by linking our one statically into KItinerary, the only place needing it here. (cherry picked from commit a637744a176eb8f89c01189a0115b1393cb57cc6) M +1 -1 .flatpak-manifest.json https://invent.kde.org/pim/itinerary/-/commit/dc8bebdf031c26219ac17264d077ad3ffc82b199
The fixes have propagated to Flathub meanwhile.
Can confirm this fixed it!