Ubuntu
f-spot package

  1. Bug #412091
  2. Comment #4

Comment 4 for bug 412091

Revision history for this message
Arvind S Raj (arvindsraj-deactivatedaccount) wrote : Re: [karmic] f-spot imports photos _before_ I hit the import button

I can't even start f-spot in karmic. I get the following error!
[Info 13:30:20.090] Initializing DBus
[Info 13:30:20.186] Initializing Mono.Addins
[Info 13:30:20.324] Starting new FSpot server (f-spot 0.6.1.5)

** (f-spot:3097): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (f-spot:3097): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (f-spot:3097): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (f-spot:3097): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (f-spot:3097): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 13:30:20.950] Starting BeagleService
[Info 13:30:20.964] Hack for gnome-settings-daemon engaged

(f-spot:3097): 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.
The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 2944 error_code 11 request_code 53 minor_code 0)
  (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.)

When I tried to load f-spot binary in gdb, I got the following error:
"/usr/bin/f-spot": not in executable format: File format not recognized