https://bugs.kde.org/show_bug.cgi?id=409862
--- Comment #11 from Michael Mikowski <[email protected]> --- We (kfocus.org) consider this behavior to be a significant bug, as it frequently confuses users and results in support calls. It also makes Discover inappropriate for managing all GUI apps in one place. Users report they can't find a package they just installed or inspected in the updater mode, where it was nicely presented in detail. We had to rewrite our [software management guide](https://kfocus.org/wf/update.html) to move away from recommending Discover because of this. I attached images that hopefully help better illustrate this behavior (“Google Chrome viewed by clicking on the package during upgrade”; “While you can see chrome in updater and inspect it, it does not appear when searched”; “Searching for the package name also fails”). > Maybe we should force [appstream to create appstream components from local > desktop files], I think it’s still possible... This would be **great**! Perhaps you could suggest what needs to be done, and we can try to submit a PR? > ... although we’ll still have the same problem with packages that don’t > install a desktop file. We believe this is the desired behavior, since we don’t want non-expert people deleting libraries and breaking their systems. However, the updater displays all packages (including libraries), so completely hiding those would be confusing to experts and those managing CLI tools. Perhaps a suitable compromise might be to add a separate category (“All Packages” or similar) that only gets searched when the user explicitly picks it, and would have a red warning bar at the top stating “Experts only” or similar. As with the above, perhaps you could suggest what needs to be done, and we can try to submit a PR? -- You are receiving this mail because: You are watching all bug changes.
