| Summary: | Allow editing apps from the context menu, like you can do from Kicker and Kickoff | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Andrew Duma <stereator> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | mikel5764, nate, noahadvs, qydwhotmail |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.6 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Thank you for the bug report! Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), and Plasma 6.3.6 is no longer eligible for support or maintenance from KDE. It's possible that the issue exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream. Thanks for understanding! Thanks again! (In reply to Bug Janitor Service from comment #1) > Thank you for the bug report! > > Debian advises users to not submit bugs upstream > (https://www.debian.org/Bugs/Reporting), and Plasma 6.3.6 is no longer > eligible for support or maintenance from KDE. It's possible that the issue > exists only in Debian at this point. > > Could you report the bug to Debian using the report bug utility > (https://packages.debian.org/stable/utils/reportbug)? If necessary, the > maintainer of the package will forward the bug upstream. > Thanks for understanding! > > Thanks again! That is a common issue, not specific for 6.3.6 version only. I just have this one, so I reported it. This is a series of bug reports masquerading as a feature request. :) > 3. The program version stops working. This shouldn't happen. It's a bug and should be reported to the distro or the app author (if they packaged it themselves) > 6. Clicking the pinned icon fails because the .desktop file still points to the old version. This also shouldn't happen, especially if the app in question is a Flapak or a Snap, where there's a stable path for the latest version of the app to be found at. I'd encourage you to submit new bug reports for those. Here we can track the feature request of being able to access KMenuEdit from the context menu of Task Manager icons. *** This bug has been marked as a duplicate of bug 369167 *** |
Description: A core UX inconsistency: KDE allows editing application launchers in KDE Menu Editor, but there is no corresponding Edit Launcher option in the Task Manager context menu. This basic feature is required to provide easy and intuitive UX. Problem / Typical Scenario: A common issue occurs with AppImage applications: 1. User launches an AppImage. 2. Pins it to Task Manager. 3. The program version stops working. 4. User downloads a new version and launches it. 5. Pins the new version. 6. Clicking the pinned icon fails because the .desktop file still points to the old version. This illustrates how pinned launchers can become broken or inconsistent, especially for AppImage, Flatpak, or Snap apps. Users currently must manually edit .desktop files, which is counterintuitive. Proposed Solution: - Add “Edit Launcher…” to the pinned icon context menu. - Opens a GUI form (like KDE Menu Editor) to edit Name, Exec, Icon, Terminal, StartupWMClass, and arguments. - Local copies are used for editing to protect system files: -- System .desktop → local copy in ~/.local/share/applications/ -- AppImage → ~/.local/share/plasma_icons/ -- Flatpak/Snap → local copies with backend handling - Changes immediately update the pinned icon; optional Reset to Original restores defaults. Benefits: - Fixes broken or outdated pins automatically. - Simplifies launcher management. - Protects system files while providing full GUI editing. - Improves Task Manager UX and reduces frustration.