https://bugs.kde.org/show_bug.cgi?id=512772
Bug ID: 512772
Summary: Task Manager pinned launchers often fail due to
outdated .desktop references
Classification: Plasma
Product: plasmashell
Version First 6.3.6
Reported In:
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Application Launcher (Kickoff) widget
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: 1.0
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.
--
You are receiving this mail because:
You are watching all bug changes.
