GNOME Bugzilla – Bug 605351
F-Spot 0.6.1.5 won't start on Ubuntu 9.10
Last modified: 2009-12-24 12:21:24 UTC
F-spot failed to start under Ubuntu 9.10, it just flash and terminate without any user interaction. Next is the verbose from console: xxxx@xxxxx:~$ f-spot --sync [Info 21:43:41.098] Initializing DBus [Info 21:43:41.253] Initializing Mono.Addins [Info 21:43:41.473] Starting new FSpot server (f-spot 0.6.1.5) ** (f-spot:3143): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:3143): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:3143): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:3143): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:3143): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Info 21:43:42.533] Starting BeagleService [Info 21:43:42.558] Hack for gnome-settings-daemon engaged (f-spot:3143): 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 6314 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.)
*** This bug has been marked as a duplicate of bug 600349 ***