Attempted a test in VirtualBox. I have zero experience with the Discover app.

Started by installing discover and its dependencies. Ran it and tried to use it, but there was a lot that didn't seem to work - searches for available things mostly. Probably user error.

Used http://madb.mageia.org/tools/listRpmsForQaBug/bugnum/30150/application/0 to get an rpm list for qarepo. No installation issues.

Tried Discover again, and didn't see any change. Tried a reboot just in case, and still saw no change. That makes me think even more that the cause is user error due to inexperience.

The best that I can say is that I didn't see any regressions with regard to plasma-interface. Probably not enough for an OK. This needs someone with Discover experience to test with any competence.

CC: (none) => andrewsfarm

MGA8-64 Plasma on Lenovo B50 in Dutch
No installation issues
Installed discover packages, drawing in some more.
Starting from CLI gives
$ plasma-discover
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
adding empty sources model QStandardItemModel(0x13b1ab0)
invalid kns backend! "/usr/share/knsrcfiles/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation."
invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation."
QObject::connect(AbstractReviewsBackend, ResourcesModel): invalid nullptr parameter
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:77:5: QML Binding: Binding loop detected for property "value"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
could not open to check "/home/tester8/.cache/fwupd/remotes.d/lvfs/metadata.xml.gz.jcat"
Fwupd Error 0 Failed to update metadata for lvfs: checksum failure: failed to verify data, expected a51b653cd2d65c319ea28a29f09a6e8b7dc35c40

The program opens, but most of the items give "Still waiting"
Makes me think that more other packages are needed to make this run this with some success.

CC: (none) => herman.viaene

@Testers
Did you update all to versions 5.20.4-5.2 and 5.76.0-1.1?
For me it was a total of 12 packages updated.

@Packager
Please list rpms

Quick test here: Both before and after update, plasma-discover could find and install flatpak updates.

// There is a minor issue, like it have been every time i tried this app, last two years maybe: it on every start wants to update "ATER cursor theme" from version 0.0 to 0.1 (same version???) and it seem to succeed every time... I have no idea where that theme comes from or is for, and I dont care... //

CC: (none) => fri

@Morgan
I copy/paste from first post into QARepo and I just checked my testsetup:those are the versions installed then and still are.

@Morgan:

According to qarepo, this is the list that it downloaded:

knewstuff-5.76.0-1.1.mga8.x86_64.rpm
lib64colorcorrect5-5.20.4-5.2.mga8.x86_64.rpm
lib64kf5newstuff-devel-5.76.0-1.1.mga8.x86_64.rpm
lib64kf5newstuff5-5.76.0-1.1.mga8.x86_64.rpm
lib64kf5newstuffcore5-5.76.0-1.1.mga8.x86_64.rpm
lib64kfontinst5-5.20.4-5.2.mga8.x86_64.rpm
lib64kfontinstui5-5.20.4-5.2.mga8.x86_64.rpm
lib64kworkspace5-5.20.4-5.2.mga8.x86_64.rpm
lib64notificationmanager1-5.20.4-5.2.mga8.x86_64.rpm
lib64plasma-geolocation-interface5-5.20.4-5.2.mga8.x86_64.rpm
lib64plasma-workspace-devel-5.20.4-5.2.mga8.x86_64.rpm
lib64taskmanager6-5.20.4-5.2.mga8.x86_64.rpm
lib64weather_ion7-5.20.4-5.2.mga8.x86_64.rpm
plasma-workspace-5.20.4-5.2.mga8.x86_64.rpm
plasma-workspace-handbook-5.20.4-5.2.mga8.noarch.rpm
plasma-workspace-wayland-5.20.4-5.2.mga8.x86_64.rpm

I checked, and everything except the devel packages, the plasma workspace handbook, and the wayland package was installed. Be advised that I didn't install anything  "extra" to do with flatpack, and didn't activate any sources other than the Mageia repositories for my test.

I just ran it again, and it did better this time, much better, actually. It could be that I didn't give discover enough time to catalog what is available from the repos before attempting to actually DO something with it. (If only dealing with our repos, MCC is considerably faster.)

(In reply to Thomas Andrews from comment #5)
> 
> I just ran it again, and it did better this time, much better, actually. It
> could be that I didn't give discover enough time to catalog what is
> available from the repos before attempting to actually DO something with it.
> (If only dealing with our repos, MCC is considerably faster.)

Well, that was wrong. Thinking the problem might be the lesser capabilities of a Vbox guest, I tried it on real hardware. No difference. The first time I ran it I got a message that it was unable to load applications (Bug 27647) I closed it, then opened it again and it loaded applications - some of the ones in our repos. Stopped it again, and ran it from the command line, getting the same messages that Herman got in Comment 2.

Did some investigation, and it seems that what we are seeing is an inability to connect to the "KDE Store." 

And, that may be the "certain KDE web services" that are supposed to be fixed here. I found this: https://bugs.kde.org/show_bug.cgi?id=425380 which describes what I am seeing perfectly.

Think I may have figured out the problem. While knewstuff-dialog appears to be
working ok, discover update is not.

$ plasma-discover-update
plasma-discover-update: error while loading shared libraries: libDiscoverCommon.so: cannot open shared object file: No such file or directory

CC: (none) => davidwhodgins

The file /usr/lib64/plasma-discover/libDiscoverCommon.so is installed, but ...
$ ldd /usr/bin/plasma-discover-update|grep found
        libDiscoverCommon.so => not found

On a hunch that there was a lib64/lib confusion somewhere, I tried installing and updating in a 32-bit mga8 Plasma install on real 64-bit hardware.

It didn't help. The 32-bit Discover shows the same behavior as the 64-bit one.

So much for "hunches."

discover isn't part of this update, so this can't be a blocker.


This update is a really important as this can make load on KDE servers

I have been running the updates for a while, no regression noted.

Those who see problem with Discover, please open a bug on it.

That said Discover seem not well integrated anyway - IMO better to just use mgaonline and for flatpak CLI is much more informative.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

(In reply to Nicolas Lécureuil from comment #10)
> discover isn't part of this update, so this can't be a blocker.
> 
> 
> This update is a really important as this can make load on KDE servers

I did notice that there weren't any discover packages in this update, which did seem strange in light of the title.

I haven't observed any regressions on either arch. Even Discover seems to work the same both before and after these updates, so no obvious new regressions were introduced. 

So, giving it OKs on both arches.

Whiteboard: (none) => MGA8-32-OK MGA8-64-OK

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0042.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED