Bug 413829

Summary: Discover does not start with Qt 5.12
Product: [Frameworks and Libraries] frameworks-kirigami Reporter: Fabian Vogt <fabian>
Component: generalAssignee: Marco Martin <notmart>
Status: RESOLVED NOT A BUG    
Severity: normal CC: aleixpol
Priority: NOR    
Version First Reported In: 5.63.0   
Target Milestone: Not decided   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Fabian Vogt 2019-11-05 10:19:01 UTC 
Fails with:

QQmlApplicationEngine failed to load component
qrc:/qml/DiscoverWindow.qml:257 Type Kirigami.ContextDrawer unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ContextDrawer.qml:170 Type ContextDrawerActionItem unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/ContextDrawerActionItem.qml:53 Type ActionsMenu unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/ActionsMenu.qml:31 Type ActionMenuItem unavailable
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/ActionMenuItem.qml:34 "Controls.MenuItem.icon" is not available due to component versioning.

org.kde.plasma.discover: Errors when loading the GUI

Probably because of:

discover/qml/ActionListItem.qml:    icon: action.iconName
discover/qml/SourcesPage.qml:                    icon: model.icon
Comment 1 Fabian Vogt 2019-11-05 10:34:09 UTC 
Actually, more likely to be a bug in kirigami which got fixed(?) by just removing the offending line in 5.64: https://phabricator.kde.org/D24501
Comment 2 Aleix Pol 2019-11-06 02:21:45 UTC 
It would be great if you could confirm that the patch fixes the issue so we can close the bug.
Comment 3 Fabian Vogt 2019-11-06 14:21:37 UTC 
Debugged a bit further: It was actually qqc2-desktop-style.

qqc2-desktop-style was not rebuilt against the latest Qt version, so it used "import QtQuick.Templates 2.2" instead of 2.3 for its Components. That broke every import if QQC2 > 2.2...

I can't think of a way to avoid this packaging issue upstream other than an ugly hack in libqqc2desktopstyleplugin.so, so closing as INVALID.
Comment 4 Aleix Pol 2019-11-06 23:54:50 UTC 
Brilliant, thanks for investigating.