I forgot about this, I now know what the problem was. Indeed it should be a bug, but it is not what I thought it was.
eog and/or nautilus creates thumbnails, but they are never destroyed. so if you are dealing with a lot of images, or just moving them around a lot and viewing them in nautilus, the thumbnail directory quickly gets very large.
it can be resolved easily by a cron that deletes old files in the thumbnail directory, but that assumes a technically proficient user.
there should be some mechanism that treats the thumbnail directory as a cache that needs maintenance (as the cron solution does)
It would be much much better to throw thumbnails away and regenerate them than to render eog and nautilus unusable because of a glut in the thumbnail directory.
I forgot about this, I now know what the problem was. Indeed it should be a bug, but it is not what I thought it was.
eog and/or nautilus creates thumbnails, but they are never destroyed. so if you are dealing with a lot of images, or just moving them around a lot and viewing them in nautilus, the thumbnail directory quickly gets very large.
it can be resolved easily by a cron that deletes old files in the thumbnail directory, but that assumes a technically proficient user.
there should be some mechanism that treats the thumbnail directory as a cache that needs maintenance (as the cron solution does)
It would be much much better to throw thumbnails away and regenerate them than to render eog and nautilus unusable because of a glut in the thumbnail directory.