I see this frequently when running f-spot (0.6.1.4) e.g.
dougie@icarus:~/photos/in$ dougie@icarus:~/photos/in$ icarusfspot 12Nov09_22:15:16 - STARTING script: icarusfspot 12Nov09_22:15:16 - Checking for existence of lock file. 12Nov09_22:15:16 - Writing pid 2646 to lockfile Taking backup of f-spot database to /home/dougie/fspotbackups/photos.db.12Nov09_22:15:16 Backup successful. Starting f-spot ... [Info 22:15:19.039] Initializing DBus [Info 22:15:19.443] Initializing Mono.Addins [Info 22:15:20.008] Starting new FSpot server (f-spot 0.6.1.4)
** (f-spot:2657): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (f-spot:2657): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Info 22:15:47.887] Starting BeagleService [Info 22:15:47.993] Hack for gnome-settings-daemon engaged
I see this frequently when running f-spot (0.6.1.4) e.g.
dougie@ icarus: ~/photos/ in$ icarus: ~/photos/ in$ icarusfspot fspotbackups/ photos. db.12Nov09_ 22:15:16
dougie@
12Nov09_22:15:16 - STARTING script: icarusfspot
12Nov09_22:15:16 - Checking for existence of lock file.
12Nov09_22:15:16 - Writing pid 2646 to lockfile
Taking backup of f-spot database to /home/dougie/
Backup successful. Starting f-spot ...
[Info 22:15:19.039] Initializing DBus
[Info 22:15:19.443] Initializing Mono.Addins
[Info 22:15:20.008] Starting new FSpot server (f-spot 0.6.1.4)
** (f-spot:2657): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:2657): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:2657): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:2657): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:2657): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed daemon engaged
[Info 22:15:47.887] Starting BeagleService
[Info 22:15:47.993] Hack for gnome-settings-