F-spot throws: "Mono.Data.SqliteClient.SqliteSyntaxException: file is encrypted or is not a database" and crashes

Bug #69910 reported by Tarmo Aidantausta
2
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Confirmed
Undecided
F-Spot

Bug Description

Binary package hint: f-spot

I'm using a stock install of Edgy (6.10) and I've used f-spot a while now so the photos.db has been created some time ago. I'll include the photos.db on the bug report if it helps but I'd rather not if there's no need :)

Just start f-spot on terminal and it'll throw you this:

Starting new FSpot server
XXXXX
Mono.Data.SqliteClient.SqliteSyntaxException: file is encrypted or is not a database
  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 MetaStore.CreateTable () [0x00000]
  at MetaStore..ctor (Mono.Data.SqliteClient.SqliteConnection connection, Boolean is_new) [0x00000]
  at Db.Init (System.String path, Boolean create_if_missing) [0x00000]
  at FSpot.Core..ctor () [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000]
XXXXX
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Stacktrace:

  at (wrapper managed-to-native) System.Threading.Monitor.Monitor_try_enter (object,int) <0x00004>
  at (wrapper managed-to-native) System.Threading.Monitor.Monitor_try_enter (object,int) <0xffffffff>
  at System.Threading.Monitor.Enter (object) <0x00013>
  at (wrapper synchronized) DBus.Service.remove_SignalCalled (DBus.Service/SignalCalledHandler) <0xffffffff>
  at FSpot.Core.Proxy.Finalize () <0x00015>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

        mono(mono_handle_native_sigsegv+0xde) [0x815644e]
        mono [0x8122c88]
        [0xffffe440]
        mono [0x80c3ab3]
        [0xb7394c11]
        [0xb7394b9c]
        [0xb4f77c24]
        [0xb4f77bf6]
        [0xb4f77b71]
        mono [0x80af103]
        mono [0x81158f1]
        mono [0x80af237]
        mono [0x80c6444]
        mono [0x810984e]
        mono [0x811fbf5]
        /lib/tls/i686/cmov/libpthread.so.0 [0xb7e82504]
        /lib/tls/i686/cmov/libc.so.6(__clone+0x5e) [0xb7df051e]
Aborted (core dumped)

Revision history for this message
Yann Simon (yann-simon-fr) wrote :

Same problem here.

Revision history for this message
Yann Simon (yann-simon-fr) wrote :

Found solution here: http://sbug.no-ip.info/words/2006-03-26-45

cp $HOME/.gnome2/f-spot/photos.db $HOME/.gnome2/f-spot/photos.db-BACKUP
sqlite $HOME/.gnome2/f-spot/photos.db .dump | sqlite3 out.db
mv out.db $HOME/.gnome2/f-spot/photos.db

Changed in f-spot:
assignee: nobody → f-spot
status: Unconfirmed → Confirmed
Revision history for this message
Ulisse (ulipo) wrote :

For me it was enough to install sqlite3 and f-spot restarted to work :)

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.