[ubuntu-mono] [Bug 466425] [NEW] f-spot crashes on startup

[doweller]

Public bug reported:

Binary package hint: f-spot

MSI Wind U100 using UNR Karmic, all updates installed

-----

[Info  12:11:16.223] Initializing DBus
[Info  12:11:16.557] Initializing Mono.Addins
[Info  12:11:17.029] Starting new FSpot server (f-spot 0.6.1.3)

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

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

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

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

** (f-spot:2605): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info  12:11:19.172] Starting BeagleService
[Info  12:11:19.225] Hack for gnome-settings-daemon engaged

(f-spot:2605): 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 3877 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.)

** Affects: f-spot (Ubuntu)
     Importance: Undecided
         Status: New

-- 
f-spot crashes on startup
https://bugs.launchpad.net/bugs/466425
You received this bug notification because you are a member of MOTU Mono
Team, which is subscribed to f-spot in ubuntu.