[solved] F-spot się nie uruchamia.
: 25 gru 2009, 20:40
Od samego początku instalacji Ubuntu 9.4 mam problem z uruchomieniem programu F-spot. Przez chwilę pojawia się interfejs programu i natychmiast wylatuje. Uruchamiany z terminala generuje następujący komunikat:
(/usr/lib/f-spot/f-spot.exe:11857): GLib-WARNING **: g_set_prgname() called multiple times
[Info 20:21:51.123] Initializing DBus
[Info 20:21:51.323] Initializing Mono.Addins
[Info 20:21:51.717] Starting new FSpot server (f-spot 0.6.1.5)
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 20:21:53.263] Starting BeagleService
[Info 20:21:53.283] Hack for gnome-settings-daemon engaged
(/usr/lib/f-spot/f-spot.exe:11857): 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 3076 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.)
Proszę o pomoc.
(/usr/lib/f-spot/f-spot.exe:11857): GLib-WARNING **: g_set_prgname() called multiple times
[Info 20:21:51.123] Initializing DBus
[Info 20:21:51.323] Initializing Mono.Addins
[Info 20:21:51.717] Starting new FSpot server (f-spot 0.6.1.5)
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:11857): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 20:21:53.263] Starting BeagleService
[Info 20:21:53.283] Hack for gnome-settings-daemon engaged
(/usr/lib/f-spot/f-spot.exe:11857): 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 3076 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.)
Proszę o pomoc.