![Earthblade band](https://loka.nahovitsyn.com/117.jpg)
![gpodder in cron job gpodder in cron job](https://www.peepso.com/wp-content/uploads/2019/04/peepso-cron.png)
# gtk-update-icon-cache -q -t -f usr/share/icons/hicolor (WITHOUT leading slash) # These packages should depend on hicolor-icon-theme and should have
Gpodder in cron job install#
# Quite some packages install icons in the hicolor icon theme.
![gpodder in cron job gpodder in cron job](https://bc-robotics.com/wp-content/uploads/2018/10/1.jpg)
After reading GJ's question I checked my build script and found that I've left myself this note: Namcap is smart enough to complain about packages that contain gtk icons and don't call gtk-update-icon-cache (namcap seems to be pretty darn good). I compile everything from source and my build scripts run namcap on every package that I generate. Is there any particular reason why nobody (other than Pat Volkerding and company) does this as part of a default desktop setup?. Do not use the cache, and it will be slow. Keep the cache updated with gtk-update-icon-cache, and GTK wil be fast. GTK uses a cache file that helps it access icons.
![gpodder in cron job gpodder in cron job](https://help.perfexcrm.com/wp-content/uploads/2017/02/plesk2.png)
Is there any particular reason why nobody (other than Pat Volkerding and company) does this as part of a default desktop setup? Other than that it doesn't help KDE and Qt applications, perhaps? package a cache-updating script for desktop users, and run it as a daily cron job? Heck, why not package it as an initscript? Slackware's initscripts do nothing in parallel, but most desktop distributions boot quite fast, and that shouldn't be compromised by updating the icon caches.
Gpodder in cron job windows 7#
Otherwise, though, I have to wonder what gives, because users will definitely be left wondering why their desktop is slower than Windows 7 on the same hardware. That's reasonable for a DIY distro like Arch, or if you're running a server without X. Debian and Fedora at least do not, and I'm pretty sure Ubuntu doesn't either. Especially with Slack's completely non-parallel init system, this slows things down a bit, but makes for a very response Xfce desktop. Slackware solves this by running the cache updater on boot. GTK uses a cache file that helps it access icons. Turns out all those things are connected. I've also wondered why stock Slackware is very responsive. I've wondered for a while why GTK (both 2 and 3) seem so slow even on (relatively) powerful computers.
![Earthblade band](https://loka.nahovitsyn.com/117.jpg)