Данная проблема не совпадает ни с одной, существующей на данном форуме, поэтому я решил создать отдельную тему.
при запуске появляется окно F-spot и программа тут же вылетает.
paceholder@paceholder-desktop:~$ f-spot
[Info 00:50:21.029] Initializing DBus
[Info 00:50:21.241] Initializing Mono.Addins
[Info 00:50:21.475] Starting new FSpot server (f-spot 0.6.1.5)
** (f-spot:6887): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (f-spot:6887): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (f-spot:6887): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (f-spot:6887): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (f-spot:6887): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
(f-spot:6887): IBUS-WARNING **: Connect to unix:abstract=/tmp/dbus-UVQBvrRd1k,guid=97a4477e4d487ef3e0d59dd44aed4d39 failed: Failed to connect to socket /tmp/dbus-UVQBvrRd1k: Connection refused.
[Info 00:50:22.762] Starting BeagleService
[Info 00:50:22.793] Hack for gnome-settings-daemon engaged
(f-spot:6887): 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 3018 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.)