F-Spot fails to update database

Bug #307960 reported by Andreas Sandberg
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: f-spot

F-spot version 0.5.0.3-0ubuntu4 fails to import the database from an earlier F-spot version. The database is renamed and a new empty database is created instead of upgrading the old one, i.e. all photo tags are lost.

The f-spot produces the following on stdout/stderr:

[Info 21:56:16.676] Initializing DBus
[Info 21:56:16.776] Initializing Mono.Addins
[Info 21:56:16.902] Starting new FSpot server
Updating F-Spot Database
Updated database from version 3 to 3.1
Updated database from version 3.1 to 4
Will add a roll_id field to photos!
Will rename imports to rolls!
Cleaning weird descriptions, fixes bug #324425.
Updated database from version 4 to 5
Updated database from version 5 to 6
Updated database from version 6 to 7
Updated database from version 7 to 8
Updated database from version 8 to 9
Updated database from version 9 to 10
Updated database from version 10 to 11
Updated database from version 11 to 12
Updated database from version 12 to 13
Updated database from version 13 to 14
Updated database from version 14 to 15
photos_temp - photo_versions_temp
Rolling back database changes because of Exception
Mono.Data.SqliteClient.SqliteSyntaxException: no such table: jobs
  at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement (IntPtr pzStart, System.IntPtr& pzTail, System.IntPtr& pStmt) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () [0x00000]
  at Banshee.Database.QueuedSqliteCommand.Execute () [0x00000]

Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for the report, could you try to get a more detailed log running f-spot as: f-spot --debug &> f-spot-debug.txt perform the operation to reproduce the bug and attach that log to the report? thanks in advance.

Changed in f-spot:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Andreas Sandberg (andysan) wrote :

The requested debug output has been attached. Doesn't look like it contains anything useful except for what's in the description already.

Revision history for this message
bd (bdabelow) wrote :

I am experiencing this with f-spot 0.5.0.3-0ubuntu4, too.

I was able to work around the issue by first opening the database with f-spot 0.4.3.1 (from hardy) and then opening it with f-spot 0.5.0.3.

Revision history for this message
Dan Ballard (haplo) wrote :

I'm having the same problem.

Changed in f-spot (Ubuntu):
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

does deleting the photos.db fixes the issue?

Changed in f-spot (Ubuntu):
status: New → Incomplete
Revision history for this message
Andreas Sandberg (andysan) wrote :

It did, which isn't so strange since the problem really is that f-spot can't update the database, creating a new one isn't a problem. IIRC that's what I did and retagged all the photos.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.