| Summary: | Fwupd backend gets stuck checking for updates and blocks everything else | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | StringentDev |
| Component: | fwupd Backend | Assignee: | Abhijeet Sharma <sharma.abhijeet2096> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aleixpol, leinir, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.4 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-10964-0.html
attachment-30952-0.html |
||
|
Description
StringentDev
2022-04-18 05:54:31 UTC
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them. --------------------------------------------------------- Also emitted ANY TIME that the application proceeds to load the Update scene. Do you have any Flatpak repos configured? Does it work if you open Discover in a terminal window with `plasma-discover --backends packagekit`? On 18/04/2022 16:27, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=452718 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |nate@kde.org > Status|REPORTED |NEEDSINFO > > --- Comment #2 from Nate Graham <nate@kde.org> --- > Do you have any Flatpak repos configured? > > Does it work if you open Discover in a terminal window with `plasma-discover > --backends packagekit`? > No. It does not work in terminal. Yes I have flatpaks configured to flathub. What does `pkcon get-updates` show? If it shows things, can you apply the updates with `pkcon update`? Created attachment 148263 [details] attachment-10964-0.html Ok, so Discover is still saying that there is 1 update available but pkcon returns ---------------------------------------------------------------------------------- Getting updates [=========================] Downloading list of packages [=========================] Finished [=========================] There are no updates available at this time. ---------------------------------------------------------------------------------- That's pretty weird to me. On 19/04/2022 16:08, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=452718 > > --- Comment #4 from Nate Graham<nate@kde.org> --- > What does `pkcon get-updates` show? If it shows things, can you apply the > updates with `pkcon update`? > That means there's an update in Discover that doesn't come from PackageKit. Probably Flatpak or KNS. Can you run Discover with one backend at a time to see where the update comes from? - To run it with only the Flatpak backend, run `plasma-discover --backends flatpak-backend` - To run it with only the KNewStuff backend, run `plasma-discover --backends kns-backend` - To list available backends beyond those, run `plasma-discover --listbackends` Flatpak - OK (Displays updates) KNewStuff - Slow (But shows updates) FWUpdate - Failed (Issue is occurring here) PackageKit - Ok (Displays updates) On 20/04/2022 14:23, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=452718 > > --- Comment #6 from Nate Graham <nate@kde.org> --- > That means there's an update in Discover that doesn't come from PackageKit. > Probably Flatpak or KNS. > > Can you run Discover with one backend at a time to see where the update comes > from? > - To run it with only the Flatpak backend, run `plasma-discover --backends > flatpak-backend` > - To run it with only the KNewStuff backend, run `plasma-discover --backends > kns-backend` > - To list available backends beyond those, run `plasma-discover --listbackends` > Uninstalled the "fwupd" package - it now works fine. On 20/04/2022 14:23, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=452718 > > --- Comment #6 from Nate Graham <nate@kde.org> --- > That means there's an update in Discover that doesn't come from PackageKit. > Probably Flatpak or KNS. > > Can you run Discover with one backend at a time to see where the update comes > from? > - To run it with only the Flatpak backend, run `plasma-discover --backends > flatpak-backend` > - To run it with only the KNewStuff backend, run `plasma-discover --backends > kns-backend` > - To list available backends beyond those, run `plasma-discover --listbackends` > Ok, so the fwupd backend is getting stuck and blocking everything else. Gotcha. If you reinstall fwupd, what happens when you run `fwupdmgr get-updates` in a terminal window? Does that get stuck too? 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! Nope. Everything works in the terminal as "No detected devices" is returned after a couple seconds. And Discover is still hanging now that you reinstalled fwupd, and , right? 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! Created attachment 149252 [details]
attachment-30952-0.html
Sorry, Did a distro jump. I'll install KDE again on Ubuntu and try with fwd again.
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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |