Re: Failed attempt to upgrade in Ubuntu Edgy



Hi

Perhaps your database is still in Sqlite2 version, while F-Spot demands
Sqlite3?

Try with 
	file ~/.gnome2/f-spot/photos.db
If this is Sqlite2 (not 3) then try to convert the database.

Gabriel (and a number of others) have sent the following instruction to
the list before.

/Bengt

cd ~/.gnome2/f-spot/
mv photos.db photos_sqlite2.db
sqlite photos_sqlite2.db .dump | sqlite3 photos.db

Note the first sqlite call in the last instruction is sqlite (which is
sqlite2 implicitly, so you must have it installed).

Gabriel

On Sat, 2007-03-31 at 20:40 -0400, Roger Mudd wrote:
> Need a little help. Tried updating to the most recent version F-Spot.
> I failed and then tried to get back to square one by reinstalling via
> aptitude on Ubuntu Edgy. Unfortunately, that didn't work. Below is the
> message the system returns when I attempt to start F-Spot from the
> command line. Any ideas on how I can extricate myself from this mess?
> I'm more interested in getting back to the version currently available
> in the Edgy repositories. I'll wait for the Feisty release as a means
> to update F-Spot.
> Thanks in advance,
> 
> Roger
> 
> ===================
> 
> Starting new FSpot server
> XXXXX
> System.Exception: Unsupported database version
>   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
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> Starting new FSpot server
> 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]
>         [0xb73a3c11]
>         [0xb73a3b9c]
>         [0xb5ee066c]
>         [0xb5ee063e]
>         [0xb5ee05b9]
>         mono [0x80af103]
>         mono [0x81158f1]
>         mono [0x80af237]
>         mono [0x80c6444]
>         mono [0x810984e]
>         mono [0x811fbf5]
>         /lib/tls/i686/cmov/libpthread.so.0 [0xb7e91504]
>         /lib/tls/i686/cmov/libc.so.6(__clone+0x5e) [0xb7dff51e]
> Aborted (core dumped)
> _______________________________________________
> F-spot-list mailing list
> F-spot-list gnome org
> http://mail.gnome.org/mailman/listinfo/f-spot-list
> 




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]