SUMMARY org.kde.audiotube flatpak does not run STEPS TO REPRODUCE 1. flatpak install org.kde.audiotube 2. flatpak run org.kde.audiotube OBSERVED RESULT asyncdatabase: Checking whether migration "2022-05-20-194850_init" is already applied asyncdatabase: … yes asyncdatabase: Migrations finished QQmlApplicationEngine failed to load component qrc:/main.qml:97:20: Type Kirigami.ContextDrawer unavailable file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:183:17: Type ContextDrawerActionItem unavailable file:///usr/lib/qml/org/kde/kirigami.2/private/ContextDrawerActionItem.qml:41:5: Type ActionsMenu unavailable file:///usr/lib/qml/org/kde/kirigami.2/private/ActionsMenu.qml:19:38: Type ActionMenuItem unavailable file:///usr/lib/qml/org/kde/kirigami.2/private/ActionMenuItem.qml:18:10: Non-existent attached object EXPECTED RESULT audiotube launches SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6
Unfortunately I can't reproduce this issue, the nightly flatpak and the one from flathub work fine for me. From where did you install the flatpak?
(In reply to Jonah Brüchert from comment #1) > Unfortunately I can't reproduce this issue, the nightly flatpak and the one > from flathub work fine for me. > From where did you install the flatpak? I installed from Flathub How do I try the nightly?
(In reply to login from comment #2) > (In reply to Jonah Brüchert from comment #1) > > Unfortunately I can't reproduce this issue, the nightly flatpak and the one > > from flathub work fine for me. > > From where did you install the flatpak? > > I installed from Flathub > How do I try the nightly? Found one in the pipelines. It works fine.
Sorry, I am tired, I meant it has the same issue. Can’t we edit the comments in KDE bugs?
I could now reproduce this on another device. Deleting the qml cache from ~/.var/app/org.kde.audiotube/cache/ helped. Can you try whether that fixes it for you?
Deleting the cache did the trick
I had the same issue and can confirm deleting the cache resolved the issue.