Ubuntu Sverige

Kod: Markera allt

pappa@PAPPA-2:~$ f-spot

(/usr/lib/f-spot/f-spot.exe:5468): GLib-WARNING **: g_set_prgname() called multiple times
[Info  23:12:47.948] Initializing DBus
[Info  23:12:48.020] Initializing Mono.Addins
[Info  23:12:48.149] Starting new FSpot server (f-spot 0.6.1.5)

** (/usr/lib/f-spot/f-spot.exe:5468): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:5468): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:5468): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:5468): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:5468): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info  23:12:48.648] Starting BeagleService
[Info  23:12:48.661] Hack for gnome-settings-daemon engaged

(/usr/lib/f-spot/f-spot.exe:5468): 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 2956 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.)