After Upgrade to Gutsy f-spot won't start: "The database is locked"

Bug #223122 reported by Béné
2
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: f-spot

After upgrading from Gutsy to Hardy I am seeing another problem with the migration of my f-spot database to the newest format. Upon launching the application it crashes immediately with the following output:

$f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
Starting new FSpot server
Updating F-Spot Database

Unhandled Exception: Mono.Data.SqliteClient.SqliteBusyException: The database is locked.
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (IntPtr pStmt, System.Int32& cols, System.IntPtr& pazValue, System.IntPtr& pazColName) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (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]

When I move ~/.gnome2/f-spot out of the way f-spot launches just fine. (I am a little terrified at the thought of losing my photo collection, though!)

F-Spot version: 0.4.2
Ubuntu Hardy

Revision history for this message
Béné (bene-d) wrote :

It has now magically started to work. Maybe because of some update? Maybe because of the good weather? I don't know why, but it works. :) Thanks for your patience.

Changed in f-spot:
status: New → Invalid
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.