You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2020. It is now read-only.
The icon path in the created .desktop launcher file is hardcoded to Icon=/opt/{{name}}/icon.png. This prevents icon theming without editing the launcher file.
I'd like to ask you to change the icon location as well as the icon path line in the launcher according to the freedesktop.org standards. Please find more info here and here.
According to the above resources standard icon locations are:
When the icon is located in one of the above the corresponding standard icon line in the .desktop launcher only has to be Icon=[icon name], without the full path and without file extension. In this programs case, for an icon eintopf.svg or eintopf.png stored in a standard location it would read: Icon=eintopf
The icon path in the created .desktop launcher file is hardcoded to
Icon=/opt/{{name}}/icon.png
. This prevents icon theming without editing the launcher file.I'd like to ask you to change the icon location as well as the icon path line in the launcher according to the freedesktop.org standards. Please find more info here and here.
According to the above resources standard icon locations are:
/usr/share/icons/hicolor/[size]/apps/[icon name]
~/.local/share/icons/hicolor/[size]/apps/[icon name]
/usr/share/pixmaps/[icon name]
When the icon is located in one of the above the corresponding standard icon line in the .desktop launcher only has to be
Icon=[icon name]
, without the full path and without file extension. In this programs case, for an iconeintopf.svg
oreintopf.png
stored in a standard location it would read:Icon=eintopf
Cf. this example .desktop launcher.
Could you please install the icon to one of those locations and adjust the icon path in the .desktop file accordingly?
The text was updated successfully, but these errors were encountered: