GNOME Bugzilla – Bug 484802
crash in Gimmie:
Last modified: 2007-10-08 18:07:52 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (99431 sec old) --------------------- System.IO.FileNotFoundException: file:///home/jedi/Photos/2007/06/07/IMGP1740.JPG at Gnome.Vfs.Vfs.ThrowException (System.String uri, Result result) [0x00000] at Gnome.Vfs.Vfs.ThrowException (Gnome.Vfs.Uri uri, Result result) [0x00000] at Gnome.Vfs.FileInfo..ctor (Gnome.Vfs.Uri uri, FileInfoOptions options) [0x00000] at Gnome.Vfs.FileInfo..ctor (System.String uri, FileInfoOptions options) [0x00000] at Gnome.Vfs.FileInfo..ctor (System.String uri) [0x00000] at FSpot.ThumbnailGenerator.ThumbnailIsValid (Gdk.Pixbuf thumbnail, System.Uri uri) [0x00000] open uri = file:///home/jedi/Photos/2007/06/07/IMGP1740.JPG System.IO.FileNotFoundException: Could not find uri "file:///home/jedi/Photos/2007/06/07/IMGP1740.JPG". at Gnome.Vfs.VfsStream..ctor (System.String text_uri, FileMode mode, Boolean async) [0x00000] at Gnome.Vfs.VfsStream..ctor (System.String uri, FileMode mode) [0x00000] at (wrapper remoting-invoke-with-check) Gnome.Vfs.VfsStream:.ctor (string,System.IO.FileMode) at FSpot.ImageFile.Open () [0x00000] at FSpot.ImageFile.PixbufStream () [ ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 168830
self.spark.connect("zoom-changed", lambda w, num_days: self.set_zoom_level(num_days))
self.label.set_text(label)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 416920 ***