SUMMARY When I open Discover on neon unstable, it gets stuck at "Fetching updates..." and never lists the available updates. EXPECTED RESULT Discover should search for updates and list them if available. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION fwupd backend is not installed on my system if it matters.
Reinstalling fwupd package fixed this problem. But Discover should work well regardless fwupd support is enabled or not. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Graphics Platform: Wayland
I agree it shouldn't be the case, but I also cannot reproduce. A bit of research would be appreciated.
Is this still a thing? As presented, it doesn't make sense. Discover doesn't know about fwupd besides within fwupd support. Do you still have this problem?
Created attachment 145664 [details] output of Discover with fwupd backend disabled Can reproduce on neon unstable. I'm attaching the ouput in Konsole.
I still see lots of fwupd stuff in that log: could not list fwupd remotes The name org.freedesktop.fwupd was not provided by any .service files adding empty sources model FwupdSourcesModel(0x55be3f547830) org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" kf.newstuff.core: KNSCore::HTTPWorker::HTTPWorker(const QUrl&, KNSCore::HTTPWorker::JobType, QObject*) kf.newstuff.core: KNSCore::HTTPWorker::HTTPWorker(const QUrl&, KNSCore::HTTPWorker::JobType, QObject*) kf.newstuff.core: KNSCore::HTTPWorker::HTTPWorker(const QUrl&, KNSCore::HTTPWorker::JobType, QObject*) Fwupd Error 10 The name org.freedesktop.fwupd was not provided by any .service files Fwupd Error 10 The name org.freedesktop.fwupd was not provided by any .service files kf.newstuff.core: void KNSCore::XmlLoader::slotJobData(KJob*, const QByteArray&) kf.newstuff.core: atticaProviderLoaded called kf.newstuff.core: Added provider: "api.kde-look.org" kf.newstuff.core: Engine addProvider called with provider with id "https://api.kde-look.org/ocs/v1/" qml: message: The name org.freedesktop.fwupd was not provided by any .service files qml: message: The name org.freedesktop.fwupd was not provided by any .service files How did you disable the backend? Just by unckecking all the checkboxes for it in the Settings page?
(In reply to Nate Graham from comment #5) > How did you disable the backend? Just by unckecking all the checkboxes for > it in the Settings page? uninstalling fwupd package
Did you also uninstall the package for Discover's fwupd backend?
Are you talking about plasma-discover-backend-fwupd package? If so, it is not installed on my neon unstable. I get this output when trying to install it: $ sudo apt install plasma-discover-backend-fwupd Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) plasma-discover-backend-fwupd:amd64 < none -> 5.18.5-0ubuntu0.1 @un puN Ib > Broken plasma-discover-backend-fwupd:amd64 Depends on plasma-discover:amd64 < 5.23.5+p20.04+tunstable+git20220120.0034-0 @ii mK > (= 5.18.5-0ubuntu0.1) Considering plasma-discover:amd64 214 as a solution to plasma-discover-backend-fwupd:amd64 9999 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: plasma-discover-backend-fwupd : Depends: plasma-discover (= 5.18.5-0ubuntu0.1) but 5.23.5+p20.04+tunstable+git20220120.0034-0 is to be installed E: Unable to correct problems, you have held broken packages.
Is it maybe called plasma-discover-fwupd-backend? deb* changed the name at some point.
No. $ sudo apt install plasma-discover-fwupd-backend Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package plasma-discover-fwupd-backend
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Requested info was provided.
I can confirm the bug. On my tablet, the fwupd backend is not installed and Discover gets stuck on "fetching updates...". Interestingly enough, I can't reproduce the bug if I start Discover from the terminal, only when I start it from a notification of new updates being available. I'm using Neon stable with all the latest updates applied.
Weird. I can reproduce on neon unstable even starting Discover via Konsole.
(In reply to Riccardo Robecchi from comment #13) > I can confirm the bug. On my tablet, the fwupd backend is not installed and > Discover gets stuck on "fetching updates...". Interestingly enough, I can't > reproduce the bug if I start Discover from the terminal, only when I start > it from a notification of new updates being available. > I'm using Neon stable with all the latest updates applied. So it starts working if you do install the fwupd backend?
(In reply to Nate Graham from comment #15) > So it starts working if you do install the fwupd backend? I actually haven't been able to reproduce this for a while. Discover now just works as expected on all of my machines.
Fabulous news!
it's still reproducible on neon unstable. 1. make sure the fwupd feature is enabled in the Settings page of Discover 2. uninstall the fwupd package 3. open Discover via Update Notifier in the system tray Result: Discover shows an error message on opening and gets stuck at 'Fetching updates...' The error message that appears on opening is 'The name org.freedesktop.fwupd was not provided by any .service files'.
(In reply to Patrick Silva from comment #18) > it's still reproducible on neon unstable. > > 1. make sure the fwupd feature is enabled in the Settings page of Discover > 2. uninstall the fwupd package > 3. open Discover via Update Notifier in the system tray > > Result: Discover shows an error message on opening and gets stuck at > 'Fetching updates...' > The error message that appears on opening is 'The name org.freedesktop.fwupd > was not provided by any .service files'. This is very much an invalid thing to do, and reflective of a packaging issue in the distro IMO. I'm using Fedora and when I try to remove the "fwupd" package, the package manager correctly informs me that doing so will remove the fwupd discover backend and Discover itself. Given previously-mentioned packaging issues on Neon, I think this is a Neon bug so I'm moving the bug report there.