Bug 398083

Summary:	Discover says it is busy installing updates, but never makes any progress.
Product:	[Applications] Discover	Reporter:	Andrew <andrewdbanks>
Component:	discover	Assignee:	Aleix Pol <aleixpol>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate, neousr
Priority:	NOR
Version First Reported In:	5.12.6
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andrew 2018-08-30 23:11:51 UTC

When updates are present, Discover seems as though it's attempting to download and install updates, but the progress bars never fill, and it never gets any closer to installing those updates.

I'm on Kubuntu 18.04 64-bit, Plasma 5.12.6, KDE Frameworks 5.44.0, Qt 5.9.5, Kernel 4.15.0-33-generic.

To reproduce:

1. Wait for an update notification.
2. Follow the button in the update notification to Discover, which will present you with a list of updates.
3. Click the button in Discover to install all updates.  The updates will appear to be installing but will actually just hang here.
4. Trying to close the software will give you a response that it is still performing tasks.
5. Open a terminal and run sudo apt update, then sudo apt upgrade.  Neither of these commands has been locked out while Discover is still open and in this state.  They install the updates just fine.
6. At this point, I use xkill to closer Discover, because it won't let me close it otherwise.

This has only been happening to me the past few days.  Previously, Discover was installing updates for me more or less fine.

Comment 1 Neousr 2018-08-31 17:32:29 UTC

I can confirm the same behavior on Neon 5.13.4 forcing me to close discover via KSysGuard.

As a note when it happens, it takes more than a couple of seconds on discover to show the "real size" of the download before being able to install them.

Comment 2 Aleix Pol 2018-09-03 10:26:40 UTC

Is there any chance it's related to this bug? https://bugs.kde.org/show_bug.cgi?id=397759

Would it be possible for you to reproduce with pkmon?

Comment 3 Andrew 2018-09-03 15:09:03 UTC

(In reply to Aleix Pol from comment #2)
> Is there any chance it's related to this bug?
> https://bugs.kde.org/show_bug.cgi?id=397759
> 
> Would it be possible for you to reproduce with pkmon?

It does appear to duplicate that bug.  I'm still not entirely sure what pkmon is even after reading the man page, but it appears to monitor the network traffic of package management.  (Side note: it's very difficult to Google "pkmon" because it just returns a lot of results for Pokemon.)  Perhaps it was an earlier update that fixed this problem (updated by command line and not by Discover), or perhaps it was because I was running pkmon in a terminal while running Discover, but this time Discover did its job exactly the way it was supposed to.  The next time I have an update notification, I'll try it without pkmon running and see if it behaves normally.

Comment 4 Aleix Pol 2018-09-04 11:29:30 UTC

pkmon is a monitoring tool for PackageKit. it shows what's doing and which transactions are being run.

Comment 5 Nate Graham 2018-09-04 18:56:50 UTC

Let us know if Plasma 5.12.7 doesn't fix the issue for you. If it doesn't, then this wasn't a duplicate of Bug 397759 and we can re-open it.

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

Comment 6 Andrew 2018-09-06 13:12:57 UTC

The problematic behavior is now gone, and Discover is behaving properly after two sets of updates.  Note that all of my major software versions for Plasma, KDE Frameworks, Qt, and Kernel are the same as they were when I wrote this ticket.  5.12.7 isn't responsible for the fix, because I'm still using 5.12.6.  I'm not sure what changed, but perhaps one of the updates I installed via command line did the trick.