GNOME Bugzilla – Bug 333643
F-spot crashes on start
Last modified: 2006-03-16 01:47:17 UTC
Distribution: Ubuntu 6.04 (dapper) Package: f-spot Severity: major Version: GNOME2.13.92 unspecified Gnome-Distributor: Ubuntu Synopsis: F-spot crashes on start Bugzilla-Product: f-spot Bugzilla-Component: General Bugzilla-Version: unspecified Description: Description of Problem: Starting the application makes it crash. Steps to reproduce the problem: 1. Start f-spot from command line or menu 2. 3. Actual Results: Starting new FSpot server Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object in <0x001b9> PhotoStore:Query (System.String query) in <0x0044a> PhotoStore:Query (.Tag[] tags, .DateRange range) in <0x00025> FSpot.PhotoQuery:.ctor (.PhotoStore store) in <0x00779> MainWindow:.ctor (.Db db) in <0x0002a> FSpot.Core:get_MainWindow () in <0x0000c> FSpot.Core:Organize () in <0x004d8> FSpot.Driver:Main (System.String[] args) Expected Results: Application started How often does this happen? Always Additional Information: ------- Bug created by bug-buddy at 2006-03-06 19:15 ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this. Unknown version unspecified in product f-spot. Setting version to "0.0.10".
this version of f-spot is ancient, closing.
I don't think so... f-spot --version gives me Gnome f-spot 0.1.10 Which is the newest release listed on f-spot.org
ok I'll update the version info then. the bug originally said 0.0.10
does moving ~/.gnome2/photos.db out of the way allow f-spot to start?
Oh... so that was it. Yes, it is starting now. Must be because I deleted some dirs and files which were on the database...
can you attach your photos.db to this bug so I can try to find the issue?
Created attachment 61067 [details] The offending one For sure, here it is the photos.db which caused the bug
I get this problem too, as of today, also on Ubuntu dapper using the same version. I added a bunch of new photos yesterday, possibly the problem is related to that in some way? I can attach my photos.db if desired. If I do 'select * from photos;' using sqlite photos.db, I get entries for the new photos that look like this: 3003|1142012387|/home/msmith/media/photos/misc-uncategorised-2005-2006|R0013825.JPG|Invalid size of entry (272, expected 264 x 1).|1 The 'invalid size of entry [...]' bit looks bad.
I did some quick debugging (but quickly reached my limits of knowledge of mono/C#/sql/etc.), and found that the exception was being thrown from PhotoStore.cs:1178, which reads "photo.Description = reader[4].ToString();" It turns out that it's not the 'invalid size of entry' things that are causing problems - some of my slightly older photos have those too. I imported a new directory of photos that had a non-US-ASCII character in the name; the exception occurs when processing the first of the SQL results that contains one of these. sqllite prints out this row as: 3063|1137810060|/home/msmith/media/photos/2006/cal�ots|RIMG0001.JPG|Invalid size of entry (272, expected 264 x 1).|1 The directory is actually /home/msmith/media/photos/2006/calçots/ (and does contain the referenced filename). I'm probably capable of 'fixing' this up myself by renaming the directory and deleting the bad bits from the db, but I'll keep a copy of the db around for later testing if you want.
michael, an you try loading this with f-spot 0.1.11 or later. I think I've fixed the issue.
Good news: It now doesn't crash. Bad news: all the entries with the non-US-ASCII directories don't show up in f-spot any more (though they initially imported just fine). Good news: after deleting these 'bad' photos from f-spot and re-importing with 0.1.11, these entries stick around and work correctly. Weirdness: they're imported with the comment "Unicode", rather than no comment at all as I expected. Thanks!
Michael, where does it say unicode? in the entry under the image? can you attach one of those images to this bug please?
Yes, in the entry labelled 'Comment' under the image. I've uploaded one of the photos to here, as it's too large (~2 meg) for bugzilla: http://people.xiph.org/~msmith/R0013862.JPG I've reproduced this with 0.1.11 as follows: 1) Import directory full of photos (/home/msmith/media/photos/2006/calçots/), with 'copy files to Photos directory' turned off. 2) See that the comment is empty, as expected. 3) Close f-spot and restart. 4) See that the comment on these imported images is now the string "Unicode".
ok this is fixed in cvs now. Thanks for catching it.