Bug 494779 - "Unable to load applications, please verify internet connectivity" error message
Summary: "Unable to load applications, please verify internet connectivity" error message
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 6.2.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 494791 494835 494836 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-10-14 21:43 UTC by Patrick Silva
Modified: 2024-10-16 06:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
screenshot (53.56 KB, image/png)
2024-10-14 21:43 UTC, Patrick Silva 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2024-10-14 21:43:16 UTC 
Created attachment 174822 [details]
screenshot

SUMMARY
Discover does not find any flatpak/distro package on my system, it says "Unable to load applications, please verify internet connectivity" despite my internet connection is working as expected.

STEPS TO REPRODUCE
1. open Discover
2. 
3. 

OBSERVED RESULT
"Unable to load applications, please verify internet connectivity" error message seen in the attached screenshot.

EXPECTED RESULT
Discover loads all applications from enabled backends

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Graphics Platform: Wayland
Comment 1 Antonio Rojas 2024-10-14 22:30:57 UTC 
libxmlb 0.3.20 broke appstream, not a KDE issue (although the highly misleading error message should definitely be changed)
Comment 2 Antonio Rojas 2024-10-15 06:53:56 UTC 
*** Bug 494791 has been marked as a duplicate of this bug. ***
Comment 3 Antonio Rojas 2024-10-16 06:12:24 UTC 
*** Bug 494835 has been marked as a duplicate of this bug. ***
Comment 4 Antonio Rojas 2024-10-16 06:12:51 UTC 
*** Bug 494836 has been marked as a duplicate of this bug. ***