Bug 2057531 - Discover does not display applications correctly.
Summary: Discover does not display applications correctly.
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-discover
Version: 36
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F36BetaBlocker
TreeView+ depends on / blocked
Reported: 2022-02-23 15:18 UTC by Lukas Ruzicka
Modified: 2022-03-04 22:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-04 22:20:34 UTC
Type: Bug

Attachments (Terms of Use)
Log file from the affected machine. (2.88 MB, text/plain)
2022-02-23 15:18 UTC, Lukas Ruzicka
no flags Details
No applications visible. (136.77 KB, image/png)
2022-02-23 15:26 UTC, Lukas Ruzicka
no flags Details
Available applications (209.15 KB, image/png)
2022-02-23 15:27 UTC, Lukas Ruzicka
no flags Details
Installed applications (172.29 KB, image/png)
2022-02-23 15:29 UTC, Lukas Ruzicka
no flags Details

Description Lukas Ruzicka 2022-02-23 15:18:41 UTC
Created attachment 1862999 [details]
Log file from the affected machine.

Description of problem:

When Discover is started, a cog wheel is spinning for a while (Loading) and finally it does not display any application. Instead it reports "Unable to load applications. Please verify Internet connectivity". At the same time, the ping command is successfully running in the background. 

When I click on Applications, Discover displays applications that can be installed, but all of them are Flatpak applications only.  No RPM applications are available.

The list of installed applications only shows three flatpak items, although I have installed several applications using DNF.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start Discover.
2. Try to list through applications.
3. Try to see the list of installed applications.

Actual results:

Applications are not shown, or only Flatpaks are shown.

Expected results:

All applications should be visible from the start.

Additional info:

See the log file.

Comment 1 Fedora Blocker Bugs Application 2022-02-23 15:21:33 UTC
Proposed as a Blocker for 36-beta by Fedora user lruzicka using the blocker tracking app because:

 Since Discover does not display any RPM based applications, I believe that it violates the following criterion and therefore I am proposing this bug as a Beta Blocker.

# Installing, removing and updating software.


Comment 2 Lukas Ruzicka 2022-02-23 15:26:04 UTC
Created attachment 1863005 [details]
No applications visible.

This image shows the application claiming not to have an internet connection available, but at the same time a successfully running PING that proves the Internet connection was available.

Comment 3 Lukas Ruzicka 2022-02-23 15:27:18 UTC
Created attachment 1863006 [details]
Available applications

This image shows that only Flatpak applications are listed in the list of available applications.

Comment 4 Lukas Ruzicka 2022-02-23 15:29:40 UTC
Created attachment 1863007 [details]
Installed applications

This image shows that only Flatpak applications are listed among the installed applications.

Comment 5 Rex Dieter 2022-02-23 15:52:39 UTC
Does running this (as root) help?

appstreamcli refresh --force

Comment 6 Geraldo Simião 2022-02-24 05:17:16 UTC
It looks similar to this old ticket here at f35

Comment 7 Lukas Ruzicka 2022-02-24 09:40:46 UTC
(In reply to Rex Dieter from comment #5)
> Does running this (as root) help?
> appstreamcli refresh --force

Yes, running the command solves the situation partly.

1. Newly, repositories are available to install (Fedora RPM Fusion, etc) in Applications menu, but their status is still "Loading" so they cannot be installed after all.
2. All packages seem now to be listed in Installed.
3. The application still starts with "Check the internet connection."
4. No RPM applications are available in Applications menu.

Comment 8 Adam Williamson 2022-02-24 17:54:26 UTC
Rex disabled the patch we added to address #2011322 in December:


because it doesn't work with current appstream, apparently. So that would tie in. I think we might want to just re-open #2011322 as this is likely the same thing.

Comment 9 Adam Williamson 2022-02-24 17:55:37 UTC
For now, though, there's +4 in https://pagure.io/fedora-qa/blocker-review/issue/626 , so accepting as a Beta blocker.

Comment 10 Adam Williamson 2022-02-24 19:08:47 UTC
A quick fix we could try here is to try wiping the apparently-bad appstream cache from the KDE live image in kickstart %post - see https://bugzilla.redhat.com/show_bug.cgi?id=2017587 . But I'm going to see first if I can figure out why we get the bad cache on KDE images.

Comment 11 Adam Williamson 2022-02-24 23:54:50 UTC
Huh. So I just tested this myself with Fedora-KDE-Live-x86_64-36-20220224.n.0.iso . Interestingly the appstream cache on that image seems to be full size, not broken. And I can't reproduce the bug. I installed in en_US locale, booted, logged in, ran plasma-discover, and it shows apps fine, RPM as well as flatpak.

Can you reproduce with a clean install from that ISO, Lukas?

Comment 12 Lukas Ruzicka 2022-02-25 13:08:26 UTC
I cannot reproduce it when a clean install from the suggested ISO is performed.

Comment 13 Lukas Ruzicka 2022-02-25 13:15:16 UTC
Also, I cannot reproduce this when I let the VM update to the latest versions.

Comment 14 Adam Williamson 2022-02-25 16:47:04 UTC
OK, that's good news, but let's keep testing with new builds. I don't know if the 'fix' is permanent or if it's just random, maybe another day's compose will have the bad cache and show the bug again...

Comment 15 Ben Cotton 2022-02-25 18:18:35 UTC
I'm setting this to ON_QA to reflect the fact that it's (at least temporarily) fixed. We'll move it back to NEW if the behavior reappears.

Comment 16 Adam Williamson 2022-03-02 06:28:28 UTC
Still working, Lukas?

Comment 17 Lukas Ruzicka 2022-03-04 11:04:34 UTC
Still working for me.

Comment 18 Adam Williamson 2022-03-04 22:20:34 UTC
OK, let's call this fixed for now then. If the bug comes back we can re-open it. Thanks!

Note You need to log in before you can comment on or make changes to this bug.