Bug 436373 - Applications addons are not available in Discover
Summary: Applications addons are not available in Discover
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: KNewStuff Backend (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-29 20:08 UTC by Patrick Silva
Modified: 2021-10-30 04:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (14.45 KB, image/png)
2021-04-29 20:08 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2021-04-29 20:08:24 UTC
Created attachment 138010 [details]
screenshot

STEPS TO REPRODUCE
1. open Discover
2. 
3. 

OBSERVED RESULT
As we can see in the attached screenshot, Applications Addons category is missing from sidebar.

EXPECTED RESULT
Applications Addons category present in the sidebar

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.21.80
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 1 Patrick Silva 2021-04-29 20:51:02 UTC
Humm, this bug does not occur consistently.
Sometimes Applications Addons category is available, but apparently
not all sub-categories work well. When I click on Pages or Script Sieve, for example, Discover says "Nothing found". When I click in K3b Themes, only one
theme is available despite several K3b themes are available in KDE Store website.
Comment 2 Nate Graham 2021-04-30 16:34:49 UTC
Seems like an issue with the KNS backend.

Cannot reproduce, FWIW.
Comment 3 Bug Janitor Service 2021-09-27 22:02:08 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/169
Comment 4 Aleix Pol 2021-09-30 11:02:52 UTC
Git commit c0e9cb9376ca5348a214458532a0611832f12f71 by Aleix Pol Gonzalez, on behalf of Aleix Pol.
Committed on 30/09/2021 at 11:02.
Pushed by apol into branch 'master'.

kns: Centralise the backend query state handling

We put it all into ::setResponsePending which is the function that we
call to tell we are embarking on a new query.
This allows us to make sure the signals to wrap up the previous state
can be emitted as well as notifying about the new state accordingly.
This also allows us to assert when the state isn't as expected, which
allowed to address some issues already as it's done in this change.

Hence, this fixes:
- issuing 2 searches before the backend has initialised will result in
an infinite job as both queries would be waiting forever for the backend
to initialise.
- issuing 2 searches where the first is pageable would leave the second
idling forever even though it's the one we care about.
- checking for updates didn't check whether we are already querying, we
could get 2 tasks weirdly overlapping
- fetchMore wouldn't notify about starting to fetch
- fetchEntryById isn't paged
- findResourceByPackageName wouldn't reset the m_responsePending value
Related: bug 432965

M  +69   -37   libdiscover/backends/KNSBackend/KNSBackend.cpp
M  +2    -0    libdiscover/backends/KNSBackend/KNSBackend.h

https://invent.kde.org/plasma/discover/commit/c0e9cb9376ca5348a214458532a0611832f12f71
Comment 5 Nate Graham 2021-09-30 14:14:01 UTC
Can you check this again, Patrick?
Comment 6 Bug Janitor Service 2021-10-15 04:35:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2021-10-30 04:35:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!