de...@denva-laptop:~$ mono --debug /usr/lib/f-spot/f-spot.exe [Info 01:14:10.559] Initializing DBus [Info 01:14:10.780] Initializing Mono.Addins [Info 01:14:11.137] Starting new FSpot server (f-spot 0.6.1.4)
** (f-spot:1931): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:1931): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:1931): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:1931): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:1931): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Info 01:14:12.450] Starting BeagleService [Info 01:14:12.485] Hack for gnome-settings-daemon engaged (f-spot:1931): 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 2951 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.) -- [karmic] F-Spot crashes when opened https://bugs.launchpad.net/bugs/477953 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
