f-spot crashes at startup complains about "Unsupported database version" - Bad error message when NFS locking fails

I presume that at sometime in the past you ran F-Spot from universe, from when it was using sqlite 2.x by default (this was changed early in dapper development)

To convert your database, install both sqlite & sqlite3, then run 'sqlite ~/.gnome2/f-spot/photos.db .dump | sqlite3 ~/.gnome2/f-spot/photos.db'.

The reason that sqlite2 is not still a dependency of f-spot, is that we do not want to have the old library still supported in main, as it has some issues which were fixed in the redesign resulting in sqlite3.

No, this is the first time I'm trying f-spot.
Trying to manipulate photo.db with sqlite in anyway returns "Database locked" even though lsof 'photo.db' returns nothing.

My home directory is NFS mounted, so after much head-scratching it turned out to be an NFS client side locking issue, installing 'nfs-common' on the client machine, remounting /home and deleting photo.db solved the problem.

Thanks for the help, just wished the error message would have been less misleading.

http://mail.gnome.org/archives/f-spot-list/2005-February/msg00018.html
http://r0ver-linux.blogspot.com/
http://bugzilla.gnome.org/show_bug.cgi?id=167647

/home directory was NFS mounted and client side locking was not enabled. Error message was misleading. Installing 'nfs-common' so that rpc.statd executes solved the problem.

Ah, thanks for that. Yes, the error message is very misleading & says nothing about locking at all - a great way to confuse the user. I'll retitle the bug.

still an issue with intrepid? may someone having the behavior could send this upstream at bugzilla.gnome.org? thanks.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.