I thought about this later, after I sent my last comment. We still don't know what caused the crash.
This is a long-shot, but we did have an import crash recently due to bad EXIF data in a photo. The fix is in a separate library, gexiv2, which uses Exiv2 to read metadata. It's possible you've updated to Shotwell 0.7.2 but are still using the older version of gexiv2. You can tell what version you have by typing this at the console: $ pkg-config --modversion gexiv2 If it says 0.2.0, it's worth upgrading to 0.2.1 and see if that solves your problem. You can get it at our PPA at https://launchpad.net/~yorba/+archive/ppa Could you remove ~/.shotwell again and try importing again? This time, however, run Shotwell like this: $ SHOTWELL_LOG=1 gdb shotwell 2>&1 | tee shotwell.gdb When you get to the gdb prompt type this: (gdb) run Import the photos as before. When (if!) Shotwell crashes, you'll be returned to the gdb prompt. Type this: (gdb) backtrace full Then exit and attach to this ticket the shotwell.gdb file and ~/.cache/shotwell/shotwell.log That would help us quite a bit. Thanks! ** Changed in: shotwell Assignee: (unassigned) => Jim Nelson (yorba-jim) ** Bug watch added: trac.yorba.org/ #2560 http://trac.yorba.org/ticket/2560 ** Bug watch added: trac.yorba.org/ #2561 http://trac.yorba.org/ticket/2561 -- Shotwell 0.7.2 crash at start https://bugs.launchpad.net/bugs/638065 You received this bug notification because you are a member of Registry Administrators, which is the registrant for Shotwell. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
