Doesn't report .desktop file to clients

[robert-ancell]

Due to meta/snap/telegramdesktop.desktop not matching the snap name it does't show to snapd clients (e.g. GNOME Software).

[robert-ancell]

The simplest solution would be to rename the .desktop file - not sure if this would cause any other issues.

[3v1n0]

This is actually a tricky situation that is bothering me since long time... As the desktop id of the app is telegramdesktop and if I would change that it would break the launcher integration, while I didn't want to rename the desktop itself. The package also should be telegram-desktop to match to what is done everywhere, and so (while my initial name was telegramdesktop for that) I didn't change it

One thing I'd like to do is adding an alias to telegramdesktop so that I could rename the binary too, while keeping the snap as it is. But not sure if GNOME software can then reuse this.

Otherwise, one thing we could do is adding an X- parameter to the .desktop file saying what's the snap name it belongs to. As this might not work all the times.

[robert-ancell]

Perhaps this can be solved in snap/snapcraft. From the clients point of view the name of the .desktop file does't matter, it's just snapd not connecting the "app" to the file. Could you comment on the forum about your issue and perhaps suggest the YAML could contain an explicit link?

[robert-ancell]

Hah! Seems you've already done it :)

[jbicha]

@3v1n0 Are you aware of the provides id tag in Appstream metadata? It allows renaming .desktop's that should be recognized by the GNOME Software app.

https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-provides

https://gitlab.gnome.org/GNOME/gnome-tweaks/blob/master/data/org.gnome.tweaks.appdata.xml.in#L21

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/41

[3v1n0]

@jbicha telegram desktop already has a provides stanza: https://github.com/telegramdesktop/tdesktop/blob/dev/lib/xdg/telegramdesktop.appdata.xml#L22

And for some random reason I was just adding this to the snap right now. However I'm not sure if the snap can already parse these informations.