Bug 401177 - Discover doesn't show Wallpapers, only "still looking" throbber
Summary: Discover doesn't show Wallpapers, only "still looking" throbber
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.14.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-18 20:11 UTC by Adam Golański
Modified: 2019-01-09 18:23 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Golański 2018-11-18 20:11:02 UTC 
SUMMARY


STEPS TO REPRODUCE
1. Open Discover
2. Select Plasma Addons
3. Select Wallpapers

OBSERVED RESULT

Empty page, with "Still looking" animated throbber on bottom. I checked that for 10 minutes.


EXPECTED RESULT

Wallpaper list or message about wallpaper unavailability


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.2
Comment 1 Chase Lau 2018-12-12 17:09:19 UTC 
I'm not experiencing this issue on Neon Dev Unstable. However, I am seeing that sometimes when I click a category (plymouth, wallpapers, etc.) I get stuck with loading, but results come up if I click another category then back to the original category.
Comment 2 Chase Lau 2018-12-12 17:17:44 UTC 
Something interesting I noticed is that this behavior seems to happen when normally starting discover (i.e. using a panel), but I'm unable to replicate this behavior when running `plasma-discover` in konsole.
Comment 3 James Cain 2018-12-16 10:50:12 UTC 
I ave the O.P.'s exact issue in Plasma 5.14.4. (Neon User). For reference, when run from the command line, the relevant terminal output is the following:

"org.kde.plasma.libdiscover: last stream isn't over yet Filters(category: Category(0x55a12dadeb50, name = "Wallpapers"),) ResourcesProxyModel(0x55a12f99d680)"

Hope this helps.
Comment 4 Aleix Pol 2019-01-09 18:23:26 UTC 
This should be fixed please test on 5.15 and reopen if it's not the case.