Summary: | Edited desktop application file should be removed or hidden after uninstalling its program | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kservice | Reporter: | Fabio S. Reszko Jr. <s.reszkojr> |
Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | arojas, kdedev, kdelibs-bugs, nate |
Priority: | NOR | Keywords: | usability |
Version: | 6.5.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Fabio S. Reszko Jr.
2024-08-17 09:17:31 UTC
How are you installing and unistalling the application? Can reproduce. The issue here is that anything that removes apps (distro package manager, Discover, some other random PackageKit implementation) doesn't necessarily know about the existence of custom desktop files here. Teaching all of them is probably infeasible, though I guess we would probably make Discover do it. But that wouldn't result in full coverage. Another option is to have ksycoca scan desktop files for executables that don't exist, and either delete them, or suppress displaying them in the UI by adding NoDisplay=True to them. (In reply to Antonio Rojas from comment #1) > How are you installing and unistalling the application? Installing with `pacman -S` and uninstalling with `pacman -R`. Though I don't think this is of too much significance, as I tested with flatpak and the issue persists. The problem relies on editing the desktop application, independently of the way it was installed. |