Applications like EndeavorOS Welcome, Tor browser won’t show their actual icons on the taskbar after Gnome 46 update. I have observed that applications launched by invoking the binary through terminal using ./ behaves this way. (Not sure about the EOS Welcome) Is there any fix to this?
OS: EndeavourOS Linux x86_64. DE: GNOME 46.1. Icons: Papirus [GTK2/3].
[Edit: This is not a freshly installed system. Icons were working fine till Gnome 45.]
Gnome reads the icon name from the desktop file. You have to find the desktop file of this app, check its icon name there, and make sure there is a similarly named icon available in the icon pack.
To find the desktop file: open Looking Glass (Alt+F2 -> type lg Enter-> click Windows on the top right) you should see your open windows there, it should show the name of the desktop file, even if you started from terminal. You can find the desktop file in ~/.local/share/applications or in /usr/share/applications. Open the file, and you should see a line starting with Icon, this is what Gnome reads.
To check if a similarly named icon exists search for that name in /usr/share/icons/. If you can’t find a named icon, than the problem is in your icon pack, you should open an issue there. If you want to change the icon to something else, change the line in the desktop file.
More info in the glorious Arch Wiki: https://wiki.archlinux.org/title/Desktop_entries
But it was working fine until gnome 45. I tried multiple icons packs quogir, adwaita (default), papirus. Everything behaves the same. The same cog icon.
Check what is in the desktop file first. If the icon name is misspelled there, it won’t work with any icon pack ever.
I know how this works because the same happened to me with Thunderbird, at some release they changed the icon name in the desktop file, but it wasn’t updated in my icon packs, I expect something similar here as well. Without checking this you can’t be sure who’s fault is this, but I guess the app’s developers or maintainers messed up their desktop file some way.
Try creating a new user profile and see if the error is reproduced there.
Ah ok. Then it’s definitely a bug with Gnome. Sometimes the user configs can get messed up and make Gnome act weird, but I guess it’s not the case here.
Maybe you can roll back up a previous version? What’s your distro?
Endeavour OS. Unfortunately I cannot rollback, not using btrfs (using LUKS). Anyeay I dont have a previous snapshot.
You’ve definitely got a custom config doing something that conflicted with the base configs needed to install for 46.
- Get logs, read logs.
- Try new user and login.
- disable custom plugins and see if it’s all normal
It looks like a third party issue rather than Gnome issue…
Maybe you just need to wait for an update that fiz it
