Exec key from desktop files gets trimmed when installed by snapd
Metadata
Current evaluation
Snapd incorrectly trims invalid Exec keys from desktop files during installation. The report was closed without resolution and appears abandoned.
Suggested action: —
No scores available.
Issue body
Since snapcraft 2.25 (and the fix for bug #1588359), desktop files get invalid Exec keys for some snaps, and it appears that consequently snapd removes the key altogether when installing the snap.
$ grep Exec /snap/tus/current/meta/gui/tus.desktop
Exec=tus.tus %U
(note how `tus.tus` is not a valid alias, it won’t launch if executed in a terminal, the valid command is `tus`)
$ grep Exec /var/lib/snapd/desktop/applications/tus_tus.desktop || echo "no Exec line"
no Exec line
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Snapd incorrectly trims invalid Exec keys from desktop files during installation. The report was closed without resolution and appears abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The bug where snapd removes invalid Exec keys from desktop files during installation was abandoned due to inactivity. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1814907 desktop file Exec mangling broken | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft failed to mangle desktop file Exec lines to the $snap.$app format, leaving them unmodified. No fix or follow-up was provided. | |
| #1883145 Incorrect Exec entry transformation in .desktop file | snapcraft (launchpad) | open | Snapcraft incorrectly transforms Exec=snap run <snap> in .desktop files to Exec=<snap> run <snap>, producing a broken command. 6+ years old, no labels, no comments, no maintainer interaction. |