Summary: | Missing connectivity on session-restore launch presents an ugly error message | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Justin Zobel <justin> |
Component: | fwupd Backend | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | aleixpol, kdedev, nate, sharma.abhijeet2096 |
Priority: | NOR | Keywords: | usability |
Version First Reported In: | master | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Justin Zobel
2025-04-01 02:24:15 UTC
This would definitely be more readable for more people This is probably Discover forwarding the raw error string onto the user. In this case we need to specifically detect missing connectivity on launch and present it better. I thought we had, in fact. But apparently there are nuances here. I can't reproduce this issue by disconnecting from the internet and running `plasma-discover --backends fwupd-backend` though. I see a placeholder message saying "Unable to load applications" which is also not great, but not what you saw. Can you try to figure out a way to reproduce it on demand? I had Discover open, I guess I had a saved session, I rebooted, logged in and got this message immediately, other than that I'm not sure what steps to take. So Discover opened on launch as part of session restore? I believe so. Can you verify that by leaving it open and rebooting? See if you get a different result compared to manually launching it with no internet access. Rebooting I can confirm it happens each time. Can reproduce exactly like that on KDE Linux: 1. Have session restore turned on, as it is by default 2. Install an update using Discover 3. With the app still open, reboot the machine to apply the update On login, Discover launches and shows the error message Justin indicated. |