Bug 401845

Summary:	Package not found error after second and subsequent cancellations of installation/removal of same app
Product:	[Applications] Discover	Reporter:	Alexander Mentyu <notuxius>
Component:	discover	Assignee:	Aleix Pol <aleixpol>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.14.4
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:	6469e828293af01b6dfa3bf30b288761756f6554	Version Fixed/Implemented In:	5.15
Sentry Crash Report:

Description Alexander Mentyu 2018-12-06 22:50:00 UTC

STEPS TO REPRODUCE
1. Open Discover.
2. Select 'Applications' page.
3. Press any application 'Install'/'Remove' button.
4. Cancel it's current installation/removal by 
appeared circle stop button to the left side of 'Install'/'Remove' button/progress bar.

OBSERVED RESULT
'Transaction canceled' popup message appears after first cancellation of installation/removal of app and 'Package not found' popup message after second and subsequent cancellations of installation/removal of the same app

EXPECTED RESULT
Appearance of 'Transaction canceled' popup message after any cancellation of installation/removal of app

REPRODUCIBILITY
Sometimes

SOFTWARE/OS VERSIONS
Operating System: KDE neon Developer Edition
KDE Plasma Version: 5.14.80
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.2
Kernel Version: 4.15.0-42-generic

Comment 1 Aleix Pol 2018-12-13 03:51:32 UTC

Can you try in devunstable after today's changes? This is probably fixed already.

Comment 2 Alexander Mentyu 2018-12-13 12:49:02 UTC

Can still reproduce it on dev unstable

Comment 3 Aleix Pol 2018-12-19 15:38:08 UTC

Git commit 4d5c1618ce18fd7ca4903f40789d7ef058be9d11 by Aleix Pol.
Committed on 19/12/2018 at 15:37.
Pushed by apol into branch 'master'.

pk: No need to show a message when cancelling

The user knows, he did so

M  +1    -1    libdiscover/backends/PackageKitBackend/PKTransaction.cpp

https://commits.kde.org/discover/4d5c1618ce18fd7ca4903f40789d7ef058be9d11

Comment 4 Aleix Pol 2019-01-09 18:10:40 UTC

This should have been fixed by 6469e828293af01b6dfa3bf30b288761756f6554 which will be in 5.15.

Comment 5 Aleix Pol 2019-01-09 18:13:23 UTC

Also see c980ddf6.