Bug 502262

Summary: Missing connectivity on session-restore launch presents an ugly error message
Product: [Applications] Discover Reporter: Justin Zobel <justin>
Component: fwupd BackendAssignee: 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
I just logged in and Discover reopened before there was internet and I got a dialog with "Failed to download metadata for lvfs: network is unreachable: Host unreachable"

This is a bit jargon-y and could be simplified with: "Unable to connect to the Internet to fetch updates. Please check your network connection and try again."
Comment 1 TraceyC 2025-04-01 17:30:03 UTC
This would definitely be more readable for more people
Comment 2 Nate Graham 2025-04-01 22:11:03 UTC
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?
Comment 3 Justin Zobel 2025-04-02 03:21:54 UTC
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.
Comment 4 Nate Graham 2025-04-02 03:27:58 UTC
So Discover opened on launch as part of session restore?
Comment 5 Justin Zobel 2025-04-02 05:21:08 UTC
I believe so.
Comment 6 Nate Graham 2025-04-03 19:50:58 UTC
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.
Comment 7 Justin Zobel 2025-04-07 00:06:18 UTC
Rebooting I can confirm it happens each time.
Comment 8 Nate Graham 2025-04-09 18:00:51 UTC
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.