I can confirm that this bug exists, I'm currently experiencing it myself...console output from running f-spot:
** (f-spot:27519): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:27519): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:27519): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:27519): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:27519): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Info 07:12:45.360] Starting BeagleService [Info 07:12:45.385] Hack for gnome-settings-daemon engaged (f-spot:27519): 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 5103 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.) -- f-spot.exe crashes when using new wave theme https://bugs.launchpad.net/bugs/411941 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
