Possible bug in icon lookup #1719
|
Running
This seems a bit weird in two different ways:
and the fallback icon works, and I have also set the same icon theme in several other places in my system (dconf, xsettingsd.conf, gtk settings.ini, but NOT in .Xresources).
This happens in a recent build of |
Replies: 1 comment 2 replies
|
2.) Icons are fetched async. So when it is printed does not correlate fully with what is visible at the point in time it is printed. If you scroll through the list, the lookups are queued (multi-threaded) and fetched, once and icon is available the interface is refreshed to show it. 1.) Can you check if '/usr/share/icons/gnome/32x32/apps/terminal.png' exists? or is a broken symlink? or a wrong hardcoded path in a .desktop file? Either the icon theme lookup tells rofi an icon should exists there or a desktop file. I also notice I get some weird icon paths (firefox seems to look in /opt/firefox that does not exists for me) back from the icon system. @sardemff7 is there an 'icon' cache file that is used? edit: ^^ that was a broken .desktop file for me. |
2.) Icons are fetched async. So when it is printed does not correlate fully with what is visible at the point in time it is printed. If you scroll through the list, the lookups are queued (multi-threaded) and fetched, once and icon is available the interface is refreshed to show it.
This makes it you can get the error even though that element is no longer visible.
1.) Can you check if '/usr/share/icons/gnome/32x32/apps/terminal.png' exists? or is a broken symlink? or a wrong hardcoded path in a .desktop file? Either the icon theme lookup tells rofi an icon should exists there or a desktop file.
I also notice I get some weird icon paths (firefox seems to look in /opt/firefox that does not …