Created attachment 132508 [details] screenshot See attached screenshot. Discover found 10 updates, but can't display the update window. Not sure how to reproduce. I opened Discover and searched for "eventcalendar", then "event calendar", clicking on the categories on the left. Then I noticed the bug. The log contains these errors: file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:102:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... } file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:141:21: QML PrivateActionToolButton: Binding loop detected for property "checkable" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:121:23: QML PrivateActionToolButton: Binding loop detected for property "checkable" qrc:/qml/ApplicationsListPage.qml:125: TypeError: Cannot read property 'application' of null QQmlComponent: Component is not ready file:///usr/lib64/qt5/qml/org/kde/kirigami.2/PageRow.qml:570: Error: Error while loading page: qrc:/qml/UpdatesPage.qml:172 Invalid property assignment: "implicitHeight" is a read-only property SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.0 KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 These are the packages in the plasma-unstable COPR for Fedora: https://copr.fedorainfracloud.org/coprs/mkyral/
Ok, it's actually reproducible every time. No need to click around.
QQmlComponent: Component is not ready file:///usr/lib64/qt5/qml/org/kde/kirigami.2/PageRow.qml:570: Error: Error while loading page: qrc:/qml/UpdatesPage.qml:172 Invalid property assignment: "implicitHeight" is a read-only property That doesn't make any sense. It's *not* a read-only property. Oh. Oh. I see. You're using Frameworks 5.74 which had a bug in it relating to icon sizing which could cause this. The good news is that this is fixed in Frameworks 5.75 which is already released.
> The good news is that this is fixed in Frameworks 5.75 which is already released. That's right. Updated to KDE Frameworks 5.75 from the Fedora COPR repo kf5-unstable, and now the bug is fixed.