(/usr/lib/f-spot/f-spot.exe:20771): 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 '/usr/lib/f-spot/f-spot.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 2939 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.)
same error on toshiba tecra a7 running 9.10
(/usr/lib/ f-spot/ f-spot. exe:20771) : GLib-WARNING **: g_set_prgname() called multiple times
[Info 13:02:49.677] Initializing DBus
[Info 13:02:49.906] Initializing Mono.Addins
[Info 13:02:50.170] Starting new FSpot server (f-spot 0.6.1.5)
** (/usr/lib/ f-spot/ f-spot. exe:20771) : CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (/usr/lib/ f-spot/ f-spot. exe:20771) : CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (/usr/lib/ f-spot/ f-spot. exe:20771) : CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (/usr/lib/ f-spot/ f-spot. exe:20771) : CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (/usr/lib/ f-spot/ f-spot. exe:20771) : CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed daemon engaged
[Info 13:02:51.489] Starting BeagleService
[Info 13:02:51.526] Hack for gnome-settings-
(/usr/lib/ f-spot/ f-spot. exe:20771) : 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. f-spot/ f-spot. exe' received an X Window System error.
The program '/usr/lib/
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 2939 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.)