F-spot problemer

[Magnus]

martin@martin-laptop:~$ f-spot

(/usr/lib/f-spot/f-spot.exe:3003): GLib-WARNING **: g_set_prgname() called multiple times
[Info 20:19:15.918] Initializing DBus
[Info 20:19:16.024] Initializing Mono.Addins
[Info 20:19:16.184] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (/usr/lib/f-spot/f-spot.exe:3003): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 20:19:16.944] Starting BeagleService
[Info 20:19:16.980] Hack for gnome-settings-daemon engaged

(/usr/lib/f-spot/f-spot.exe:3003): 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 3202 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.)
martin@martin-laptop:~$

[laoshi]

Kanhænde der er en bug i en opdatering af f-spot, da du ikke er den eneste som får problemet: https://ubuntudanmark.dk/forum/viewtopic.php?f=2&t=10016