After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 551944 - Do not "housekeep" the thumbnails
Do not "housekeep" the thumbnails
Status: RESOLVED DUPLICATE of bug 552680
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.23.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
: 552197 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-09-12 11:41 UTC by Stephane Delcroix
Modified: 2008-09-20 13:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stephane Delcroix 2008-09-12 11:41:38 UTC 
A new housekeeping plugin was added in 2.23.1. Even if it looks a bright idea at first sight, it really gets in the way for heavy thumbnails user applications, like f-spot.

F-Spot rely on the fdo .thumbnail spec for displaying the miniatures, and having to regenerate all the thumbs every few weeks slow down a lot of things. On large db, with images stored on remote locations, regenerating the thumbs can take more than a few hours (yes, even on decent hardware).

So here are the few options I have as an f-spot developper:
1. Ask the users to tweak their gconf keys: BAD, as it's not a user task
2. Silently check and overwrite those gconf keys at every startup: BAD, as applications shouldn't have to overwrite global keys
3. Keep my thumbs in another location that .thumbnails: BAD, create duplicates and no longer follow the standard
4. touch every thumb at every startup: NOT GOOD, will only postpone housekeeping
Comment 1 Jens Granseuer 2008-09-12 16:26:34 UTC 
I guess we can't make everyone happy. The plugin was added because users complained "the desktop" swamped there home directory (and rightly so). Plus something thought it might be a good idea to stat all thumbnails at startup. Yes, it's a trade-off, we're aware of that.

In short, disabling the plugin is not an option. We probably have a good deal of leeway to tweak the default housekeeping parameters, but "enable" isn't one of them.
Comment 2 Jens Granseuer 2008-09-14 13:49:55 UTC 
*** Bug 552197 has been marked as a duplicate of this bug. ***
Comment 3 Stephane Delcroix 2008-09-15 08:28:15 UTC 
see bug #547190 for this bug in action
Comment 4 Stephane Delcroix 2008-09-16 08:34:22 UTC 
whar are the current default for starting to housekeep ?

(I still think this is a really bad idea, hope I'll wake up)
Comment 5 Stephane Delcroix 2008-09-16 08:53:43 UTC 
I checked the defaults... 64MB... come on

It means that if you have more than 1000 images in f-spot, g-s-d will housekeep at every startup (as reported in bug #547190)?

And by f-spot standard, a 1000 images db is ridiculous, the average being 10k, with some people hitting 50k (up to 3GB of thumbs? who cares...)

I really hope there's something to do about this... Can I raise that issue as BLOCKER ?
Comment 6 Jens Granseuer 2008-09-20 13:50:40 UTC 
Increased defaults are being discussed in libgnome bug 552680.

*** This bug has been marked as a duplicate of 552680 ***