Comment 8 for bug 486418

I still have the same problem.

Running mono --debug /usr/lib/f-spot/f-spot.exe

[Info 22:34:50.998] Initializing DBus
[Info 22:34:51.242] Initializing Mono.Addins
[Info 22:34:51.602] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (f-spot:5026): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 22:34:52.954] Starting BeagleService
[Info 22:34:52.987] Hack for gnome-settings-daemon engaged

(f-spot:5026): 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 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 2249 error_code 1 request_code 135 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.)