|
Bugzilla – Full Text Bug Listing |
| Summary: | f-spot photo import fails | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Michael Meeks <mmeeks> |
| Component: | GNOME | Assignee: | Larry Ewing <lewing> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | federico |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | gnome-function-does-not-work, gnome-showstopper | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
f-spot log
photo |
||
|
Description
Michael Meeks
2008-01-04 20:29:32 UTC
Created attachment 189397 [details]
f-spot log
Created attachment 189398 [details]
photo
At first glance, this doesn't look like a duplicate of Bug 327122 I'm unable to reproduce the problem with the attached photo. *** Bug 349067 has been marked as a duplicate of this bug. *** I just started getting this bug as well. It started after: 1. using a recycled /home directory 2. doing a fresh install of openSUSE 10.3 3. finding that I get bug #327122 4. installing sqlite2 5. restarting f-spot - now it starts, but it won't import. I get the same exception as Michael. However, I get the exception as soon as F-spot loads the first photo from the CF card - it never gets to 100%, unlike Michael's case. If I hit "skip" in the error dialog that tells me about the incorrect index, I get the same error again for the next photo. From talking to Larry and then experimenting, this made things work for me: 0. Backup ~/.gnome2/f-spot 1. Install sqlite2 2. Run f-spot, exit it 3. Run f-spot-sqlite-upgrade 3. Run f-spot again After that, importing works fine. *** This bug has been marked as a duplicate of bug 327122 *** So - what about the end-users ? do they all need to run 5 steps from the command-line to be able to import pictures again ;-) Grief - I -hate- databases. Can we not have a dual representation of the tag data in an append-only log file / journal of some kind; treat that as authoritative and re-build the database if necessary. |