Desktop entry referrences non-existent icon #3386
Comments
|
I think that there are two potential solutions here:
|
|
No, this is crazy. We're not going to "fix" hundreds of projects and specs just because one theme decided to no longer support FDO. GTK used to depend on Adwaita which used to provide these icons. If Adwaita no longer wants to do that, we just need a replacement base theme and ensure it's installed in all the DEs and/or distributions. |
|
There are plenty of theme that still provide it. |
|
Yes, the issue is that there is no official replacement yet. It won't be up to individual apps to fix the issue though. We'll make sure they can make the assumption that icons are there, just like they did before. |
|
Similar issue in blueman: blueman-project/blueman#2312 |
|
Installing and configuring an alternative icon theme (e.g.: one of the ones mentioned above) will also make the launcher use a custom icons for all other applications (Gimp, Firefox, KeepassXC, Steam, Audadious, Syncthing, Libreoffice, etc) instead of their defaults. The defaults are well-established and easy to recognise and I have no interest in changing them just so that nemo will have an icon. How about just including the Merely having a dependency on Adwaita won't fix anything, because the default theme (as per the spec) is |
That's a bad idea for one very specific reason: Conflicts. *unless other factors are in place, such as DPKG |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Distribution
Alpine Linux Edge
Package version
nemo-6.0.2-r0
Frequency
Always
Bug description
Nemo's desktop entry references the icon
system-file-manager:hicolor(see the icon-theme-spec) includes no icons at all.As a result, launchers will show no icon for nemo, because none is available.
Steps to reproduce
fuzzel(my launcher of choice; the issue is reproducible with any launcher)Expected behavior
Nemo should include a default icon for the
hicolortheme, which is the default/fallback.Additional information
To be fair, there seem to be some gaps in the icon-related specs.
The icon-naming-spec indicates that
system-file-manageris a generic name which can be used "by developers when writing applications which will use the Icon Theme Specification.".The icon-theme-spec indicates that the default/fallback theme is
hicolor, where applications can place their own custom icons.So the situation is that:
system-file-managericon forhicolor.system-file-managerbeing present inhicolor.Obviously these two expectations don't align, and results in
nemohaving no icons at all.The text was updated successfully, but these errors were encountered: