Ubuntu

Comment 7 for bug 488009

Eduardo (vancouverislandgeek) wrote :

$ f-spot
[Info 18:44:23.190] Initializing DBus
[Info 18:44:23.266] Initializing Mono.Addins
[Info 18:44:23.380] Starting new FSpot server (f-spot 0.6.1.5)
[Info 18:44:23.987] Starting BeagleService
[Info 18:44:23.999] Hack for gnome-settings-daemon engaged

(f-spot:20968): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.

## I get this far whenever I open f-spot
## With --debug on and clicking on thumbnail:

Domain: 'GdkPixbuf' Level: Critical
Message: gdk_pixbuf_scale_simple: assertion `dest_height > 0' failed
Trace follows:
   at GLib.Log.PrintTraceLogFunction(System.String domain, LogLevelFlags level, System.String message)
   at Gdk.Pixbuf.gdk_pixbuf_scale_simple(IntPtr , Int32 , Int32 , Int32 )
   at Gdk.Pixbuf.ScaleSimple(Int32 dest_width, Int32 dest_height, InterpType interp_type)
   at PixbufUtils.ScaleToMaxSize(Gdk.Pixbuf pixbuf, Int32 width, Int32 height, Boolean upscale)
   at PixbufUtils.ScaleToMaxSize(Gdk.Pixbuf pixbuf, Int32 width, Int32 height)
   at FSpot.Histogram.Generate(Gdk.Pixbuf input, Int32 max_width)
   at FSpot.Widgets.InfoBox.DelayedUpdateHistogram()
   at FSpot.Delay.HandleOperation()
   at GLib.Idle+IdleProxy.Handler()
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at FSpot.Driver.Main(System.String[] args)
The program 'f-spot' received an X Window System error.

## with --debug on and clicking on Import button

ramdisk - gnome-dev-memory - Mountpoint file:///media/ramdisk True True MemoryStick
The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 7013 error_code 1 request_code 157 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

$ uname -srm
Linux 2.6.32-23-generic x86_64
$ cat /etc/issue
Ubuntu 10.04 LTS \n \l