In case anyone has this problem with 0.10.1;

Clinton gave me instructiones to compile from source (see below). It looks like the problem is fixed in the current trunk version; compiling Shotwell from git and loading the database file makes it work smoothly again.

Best,
Ivo

--------
   1. Back up your current photo.db.
   2. Create a new directory and open a command shell there.
   3. Run the following command: 'git clone git://yorba.org/shotwell .'.
   4. Run the command 'make'.
5. When it finishes, run the command './shotwell' and check whether the crash still occurs?
--------


On 06/23/2011 01:41 AM, Clinton Rogers wrote:
Hi Ivo,

On Wed, Jun 22, 2011 at 12:32 AM, Ivo Roghair <[email protected]
<mailto:[email protected]>> wrote:

    Hi,

    Yesterday I updated the exif-data of quite some JPG images manually
    (using exiftool), especially the 'Rating' and 'Subject' tags in the
    images. I now get a force-close of the application on Shotwell
    startup (I do see the window, and it says 'Updating Library', then
    it crashes). The terminal gives me:

    **
    
ERROR:src/core/__SourceHoldingTank.c:663:__source_holding_tank_internal___notify_altered:
    assertion failed: (_tmp0_)
    Aborted


Can you send me a copy of the file ~/.shotwell/data/photo.db, if you
feel comfortable doing so?  This would greatly help us in determining
what's causing Shotwell to crash here.

    I updated the exif of the images while shotwell was closed, so it
    would update the library afterwards. I also moved and deleted quite
    some images from the file system. This worked fine, it found the new
    ratings and I removed the missing files from the library. I closed
    the program properly, but now it gives the error mentioned above.
    While I don't mind waiting for all images to be imported again (I
    moved my ~/.shotwell dir to a backup), I'd like to get the sorting
    into events back. Is it possible to restore this, somehow?

Unfortunately, restoring the event sorting may not be possible.  It may
be possible to manually edit photo.db like you want it, but this isn't
recommended.

On that score, though, it sounds as if your .db could still be valid,
and us fixing things on our side might make it usable again.

Cheers,
-c

_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell

Reply via email to