Created attachment 115556 [details] Screenshot SUMMARY After installing version 5.14.0 it is no longer possible to use the "settings" section with satisfaction STEPS TO REPRODUCE 1. Open Discover 2. Go to "Settings" OBSERVED RESULT Every line of the grid shows "undefined" EXPECTED RESULT Possibility to configure repositories SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Linux distribution: KDE Neon based on Ubuntu Bionic
Tried to reproduce the issue on a fresh neon unstable VM, and it seems to work properly for me. SOFTWARE VERSIONS KDE Plasma Version: 5.14.80 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1
Please make sure your system is up to date.
On my PC I have a fresh neon based on bionic. I constantly updated the system until, after the 5.14.0 plasma update, Discover presented this problem. "sudo apt-get update" output is fine without any warning or error. In this old changelog: https://www.kde.org/announcements/plasma-5.11.5-5.12.0-changelog.php in Discover sections, it said: "Don't show "undefined" on the settings page if there's no extra info." I don't know exactly what "extra info" means, but it describes my problem
Updating doesn't help; I experience this on git master too.
*** Bug 399759 has been marked as a duplicate of this bug. ***
I've really tried hard to reproduce this and have been unable to in any helpful way. I found a neon iso that does but then compiling myself didn't make a different. I'm afraid we're hitting some kind of Qt problem. Would any of you be able to run this discover with this patch and tell me what's the output you get? diff --git a/libdiscover/resources/SourcesModel.cpp b/libdiscover/resources/SourcesModel.cpp index 4c5ddd2c..b9047b7c 100644 --- a/libdiscover/resources/SourcesModel.cpp +++ b/libdiscover/resources/SourcesModel.cpp @@ -74,6 +74,7 @@ const QAbstractItemModel * SourcesModel::modelAt(const QModelIndex& index) const QVariant SourcesModel::data(const QModelIndex& index, int role) const { if (!index.isValid()) return {}; + qDebug() << "data" << index << role; switch (role) { case SourceNameRole: return modelAt(index)->property(DisplayName);
It works after this mornings update: discover/bionic,now 2.1.2-8 amd64 [installed] discover-data/bionic,bionic,now 2.2013.01.11 all [installed,automatic] libdiscover2/bionic,now 2.1.2-8 amd64 [installed,automatic] plasma-discover/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic] plasma-discover-common/bionic,bionic,bionic,now 5.14.0+p18.04+git20181016.0050-0 all [installed,automatic] plasma-discover-flatpak-backend/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic] plasma-discover-private/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic] plasma-discover-snap-backend/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic] plasma-discover-updater/bionic,now 5.14.0+p18.04+git20181016.0050-0 amd64 [installed,automatic]
It works after this mornings updates...... on Neon Dev Stable 18.04
Problem persists on KDE Neon 18.04 User Edition
Today I received the plasma update (5.14.1) and the problem has disappeared, so I think we can consider the bug fixed.
Gone for me too. Closing, phew.
I can reliably reproduce this on phone
With the device just flashed, I don't get the issue.
Please investigate, I'm pretty sure it's working on Plasma Mobile too.
Maybe totally irrelevant, but FWIW after installing package fwupd in plasma mobile rootfs pm-rootfs-20181110-183644.tar.gz I don't face the issue anymore.