Discover's "Installed" page shows an enormous assortment of things in a huge flat list, which is problematic for a variety of reasons: 1. For many of the Plasma components listed there, trying to remove them will remove all of Plasma, which is dangerous and is not something we should ever allow the user to do from Discover 2. It's hard to find actual *apps* so that you can uninstall them, which is the primary use case of going to the Installed page 3. All the Plasma components that appear there show "Launch" buttons" but cannot be launched (if you click the button, Discover displays a message saying "Cannot launch <thing>") Suggestion: Only show items on this page that either can be launched, or were installed using Discover (e.g. wallpapers, app addons, Plasma widgets, etc). This would slim down the list to only what's relevant and remove the ability to accidentally uninstall Plasma.
https://phabricator.kde.org/D19850 should improve this situation.
...If not fix it entirely! We'll see once it lands.
Git commit 9d49c268cf22cf209e1712dde1289c504077b4c3 by Aleix Pol. Committed on 16/04/2019 at 01:26. Pushed by apol into branch 'master'. packagekit: Don't display packages that extend themselves It's common to have appstream components for plugins that some distributions will split into separate packages. This is useful but it can easily clutter the UX. Take Okular for example, it has an appstream component for every format it supports. On some distributions, like ArchLinux, it will not be possible to give them separate states as they all point to the same package. In such case we'll just show the package that is being extended. M +2 -2 libdiscover/backends/PackageKitBackend/AppPackageKitResource.cpp M +2 -2 libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp M +1 -0 libdiscover/backends/PackageKitBackend/PackageKitBackend.h M +15 -0 libdiscover/backends/PackageKitBackend/PackageKitResource.cpp M +2 -0 libdiscover/backends/PackageKitBackend/PackageKitResource.h https://commits.kde.org/discover/9d49c268cf22cf209e1712dde1289c504077b4c3
*** Bug 409863 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 403119 ***
*** This bug has been marked as a duplicate of bug 413272 ***