GNOME Bugzilla – Bug 605648
CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
Last modified: 2009-12-29 06:00:11 UTC
I'm on Ubunutu 9.10, relatively fresh install, i32 P4. I have never even run F-spot until I tried a few minutes ago. It began to open and immediately crashed. I tried at command line with these errors: build@build-desktop:~$ f-spot (/usr/lib/f-spot/f-spot.exe:10605): GLib-WARNING **: g_set_prgname() called multiple times /home/build/.themes/NewSlicknesS/gtk-2.0/gtkrc:29: Overlay image options specified without filename [Info 23:41:30.177] Initializing DBus [Info 23:41:30.270] Initializing Mono.Addins [Info 23:41:30.408] Starting new FSpot server (f-spot 0.6.1.5) ** (/usr/lib/f-spot/f-spot.exe:10605): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:10605): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:10605): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:10605): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (/usr/lib/f-spot/f-spot.exe:10605): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Info 23:41:30.999] Starting BeagleService [Info 23:41:31.013] Hack for gnome-settings-daemon engaged (/usr/lib/f-spot/f-spot.exe:10605): 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 '/usr/lib/f-spot/f-spot.exe' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 2962 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 ***