Bug 409227

Summary:	Discover cannot update applications
Product:	[Applications] Discover	Reporter:	Alan <alangdunbar>
Component:	discover	Assignee:	Dan Leinir Turthra Jensen <leinir>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	aleixpol, jroll, nate
Priority:	NOR
Version First Reported In:	5.16.2
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	screen capture

Description Alan 2019-06-27 03:11:31 UTC

SUMMARY
The KDE Discover App on 5.16.2 still isn't working as it should.  When opening the app, it states "Please Check Your Connection", the Fetching updates section continues to loop and all app buttons are greyed out. Also a number of notifications start to populate which cannot be shut down - each time you try and close one another pops up. The notifications state Resolving, Searching for file, Updating, but nothing is actually happening

STEPS TO REPRODUCE
1. Launch Plasma-Desktop at Login
2. Launch KDE Discover
3. Refresh Discover

OBSERVED RESULT
KDE Discover gets stuck in a loop and will not update

EXPECTED RESULT
KDE Discover should connect, refresh & allow downloads of applications

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 19.04
(available in About System)
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2019-06-28 20:03:02 UTC

Are you using the Kubuntu Backports PPA to get Plasma 5.16 on your Kubuntu?

Can you attach a screen recording that shows the issue?

Comment 2 jr 2019-06-28 21:41:58 UTC

Created attachment 121210 [details]
screen capture

Same issue here. I attached a screen capture of the issue.

Comment 3 jr 2019-06-28 21:54:46 UTC

Sorry, I should clarify that I have no issues with updates, nothing hangs in discover, and no issues with notifications. Just says "Please check you connectivity" although I am connected and can receive updates. I am on KDE 15.6.2 over an Arch install.

Comment 4 Nate Graham 2019-06-30 20:20:57 UTC


*** This bug has been marked as a duplicate of bug 409220 ***