| Summary: | Discover gets stuck at "Fetching updates..." and shows an error message related to fwupd | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Patrick Silva <bugseforuns> |
| Component: | fwupd Backend | Assignee: | Abhijeet Sharma <sharma.abhijeet2096> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | leinir, nate, spiperman957 |
| Priority: | NOR | ||
| Version: | 5.24.7 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot | ||
I've gotten this from time to time. It's been a while since this problem has occurred on my systems (Arch Linux and neon unstable). Let's consider it fixed. Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Graphics Platform: Wayland This error started to appear about two weeks ago. It is consistent on every launch of discover. The service cannot activate and will time out after 25s. Then discover appears to function normally. Troubleshooting fwupd using systemd or any command using fwupdmgr also reproduces the error. => $ journalctl -xeu fwupd-refresh.service The process' exit code is 'exited' and its exit status is 1. Dec 29 14:42:36 thelio76 systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Subject: Unit failed Defined-By: systemd Support: http://www.ubuntu.com/support The unit fwupd-refresh.service has entered the 'failed' state with result 'exit-code'. Dec 29 14:42:36 thelio76 systemd[1]: Failed to start Refresh fwupd metadata and update motd. Subject: A start job for unit fwupd-refresh.service has failed Defined-By: systemd Support: http://www.ubuntu.com/support My System - Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 6.6.6-76060606-generic (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 62.0 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 Sam, you're using a version of Plasma (5.24) that's no longer supported by KDE, and the issue shown in your logs is not related to Discover itself. The problem is with fwupd, which is a 3rd-party thing that Discover relies on, but doesn't have any control over. I'd recommend reaching out to the Kubuntu folks or System76 for support with this issue. Thanks! |
Created attachment 126634 [details] screenshot SUMMARY This problem does not occur all the time. Sometimes I open Discover to install updates, it gets stuck at "Fetching updates..." and shows an error message related to fwupd a few minutes later. Screenshot attached. STEPS TO REPRODUCE 1. open Discover when updates are available 2. 3. OBSERVED RESULT Discover can get stuck at "Fetching updates..." and show an error message related to fwupd a few minutes later. When this behavior occurs, Konsole says: (process:23562): GLib-CRITICAL **: 16:08:00.383: g_ptr_array_unref: assertion 'array' failed Fwupd Error 20 Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) qml: message: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) EXPECTED RESULT Discover should show available updates. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1