I've been getting the Synaptic warning: "gtk-update-icon-cache: No theme index file" pretty much most of the time when I install software or update via synaptic, but I've never let it worry me much, as from what I can gather through reading various different posts, it's not viewed as an issue or problem. It has quietly irritated me though, none the less. Probably because it keeps popping up, telling me that something is missing, that "apparently" shouldn't be (...Call it a quirk on my behalf, lol)
However, whilst perusing other sites, I came across the further info on the error message, at:
"
https://bbs.archlinux.org/viewtopic.php?id=141072"
Basically, the following extract from that topic (The GTK Icon Cache Conspiricy) implies that for a more responsive system it DOES need to be addressed, by stating the following:
"...I've wondered for a while why GTK (both 2 and 3) seem so slow even on (relatively) powerful computers.
I've also wondered why stock Slackware is very responsive... And why it is equally slow to boot.
Turns out all those things are connected. GTK uses a cache file that helps it access icons. Keep the cache updated with gtk-update-icon-cache, and GTK wil be fast. Do not use the cache, and it will be slow.
Slackware solves this by running the cache updater on boot. Especially with Slack's completely non-parallel init system, this slows things down a bit, but makes for a very response Xfce desktop.
Most other major distros... Don't seem to deal with this. Debian and Fedora at least do not, and I'm pretty sure another distro doesn't either.
That's reasonable for a DIY distro like Arch, or if you're running a server without X. 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. Why not e.g. 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.
...."
Unfortunately, I'm not sure what to think, due to so many different threads over the past few months, essentially "Dismissing" the error as of non importance.
So my questions are these:
...Should this issue be addressed in PCLinuxOS after all?
...And if so, being that the aforementioned article applies to Slackware etc, how would we go about addressing this in PCLinuxOS??
Cheers in advance.
