https://bugs.kde.org/show_bug.cgi?id=409862
ALIEN426 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #14 from ALIEN426 <[email protected]> --- This bug is a bit confusing. Looking at the history of Discover, it seems this works as designed. It was never intended to handle all packages, quite the opposite. The whole system is built around Appstream metadata. To quote an old blog post: "Where does this app metadata come from? The app developers themselves, from their AppStream file. If an app doesn’t provide an AppStream file, or its file is very minimal and doesn’t provide much content, then the packagers have to create this information themselves." "So what’s the plan? We need to get app developers to improve their AppStream metadata. This is an ongoing effort that I’m heavily involved in, but like everything in the FOSS world, it will go much faster if you help!" Search for "Nate Graham: How to make an app look good in Discover" to read the full blog post. I've inspected the actual Discover source code and found no sign of .desktop file scanning, and I believe it never had. This sounds more like a feature request. >> That's right, newer appstream has changed to not create appstream components >> from local desktop files. >> Maybe we should force it, I think it's still possible, although we'll still >> have the same problem with packages that don't install a desktop file. Can somebody confirm when this happened, and which KDE or Discover version you were using? You might be referring to the appstream-generator app indexing .desktop files, but that's done at the repository level and repository maintainers are expected to use it. The fact that the app without appstream data can still be viewed when an update is available might actually be a bug. Whenever any update is available, even something like libxxx (which is clearly not an app) is listed everywhere, including in the Installed apps list. This is probably related to how Discover manages its internal list of applications. These items should be visible on the Updates page only. -- You are receiving this mail because: You are watching all bug changes.
