[Shotwell] Slow start up
Peter DO Smith
pdo.smith at gmail.com
Wed Sep 15 04:18:33 PDT 2010
My installation of Shotwell is suffering from slow start up again, but under
very specific circumstances.
It took 34 minutes to start up. During this time Shotwell was greyed out and
CPU usage varied from 40% to 99%
I downloaded and compiled the latest version from trunk yesterday morning.
I maintain two identical installations of my photo library in Ubuntu Linux
(10.04), one at Home and one in my Office.
The Shotwell data folder is kept in the Pictures folder (to make backup
simpler) and I invoke Shotwell as follows
shotwell -d /home/peter/Pictures/shotwell
My Home installation is my primary installation where I load photos.
Then I use Unison to synchronise my Pictures folder to a USB drive.
The Pictures folder is then restored from the USB drive to my Office
machine, once again using Unison.
This strategy has worked well until now.
Since yesterday, when I start up Shotwell on my Office machine after
restoring from my USB drive, I find that Shotwell is greyed out and
unresponsive for more than 30 minutes.
If I then close down Shotwell and restart it starts up quickly, as it did
I used Unison to see if the folders had changed. This showed me that
Shotwell had rebuilt 7904 thumbnails (both 128 and 360 bit) but that the
primary photos were still identical. I have 9668 photos in my library. Both
sets of folders are identical in every other respect, except, as expected,
the database had been updated
As far as I can tell Unison does does an excellent job maintaining
identical, synchronised folders.
Why would Shotwell rebuild the thumbnails? (many but not all)
Could the rebuild process not run in a separate thread at lower priority to
avoid this extended unresponsive period?
Thanks for including the No Events folder. That is a real life saver when I
am scanning film.
More information about the Shotwell