Bug 418041 - Impossible to uninstall an addon via GHNS window if a update is available because there is no "Uninstall" button
Summary: Impossible to uninstall an addon via GHNS window if a update is available bec...
Status: RESOLVED DUPLICATE of bug 260836
Alias: None
Product: frameworks-knewstuff
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.67.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Jeremy Whiting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-22 15:53 UTC by Patrick Silva
Modified: 2020-07-19 19:05 UTC (History)
4 users (show)

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

Attachments
"Use" and "Update" buttons available, missing "Uninstall" button (118.64 KB, image/png)
2020-02-22 15:53 UTC, Patrick Silva 		Details
"Update" and "Details..." buttons available, missing "Uninstall" button (132.75 KB, image/png)
2020-02-22 15:54 UTC, Patrick Silva 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-02-22 15:53:38 UTC 
Created attachment 126298 [details]
"Use" and "Update" buttons available, missing "Uninstall" button

STEPS TO REPRODUCE
1. install an addon via ghns window
2. wait for update to be released
3. try to uninstall such addon via ghns window

OBSERVED RESULT
you can't because there is no "Uninstall" button when you hover over the addon.
As we can see in the attached screenshots, only "Use" and "Update"  or "Update" and "Details..." buttons are available.

EXPECTED RESULT
we can uninstall an addon via ghns window even if there is a update to it available.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.18.1
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Comment 1 Patrick Silva 2020-02-22 15:54:52 UTC 
Created attachment 126299 [details]
"Update" and "Details..." buttons available, missing "Uninstall" button
Comment 2 Alexander Lohnau 2020-07-19 19:05:39 UTC 

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