F-spot

hjorthede
Antal: 27
Tilmeldt:
06-10-2006
User is offline
F-spot

Jeg er IKKE nogen ørn til dette, men F-spot starter op når jeg klikker på den.
Umiddelbart derefter afslutter den - hvis jeg derimod åbner et billede ved at bede den åbne i F-spot åbner den i F-spot fremviser.
Hvad er der galt?

Håber der er nogen der forstår mit spørgsmål.

Jeg har haft afinstalleret F-spot.


Anda
Antal: 436
Tilmeldt:
08-11-2008
User is offline
Re: F-spot

Prøv at køre f-spot i en terminal og se hvad der kommer af fejlmeddelelser.


hjorthede
Antal: 27
Tilmeldt:
06-10-2006
User is offline
Re: Re: F-spot

kim@Kimhs:~$ f-spot

(/usr/lib/f-spot/f-spot.exe:3081): GLib-WARNING **: g_set_prgname() called multiple times
[Info 12:21:45.825] Initializing DBus
[Info 12:21:45.967] Initializing Mono.Addins
[Info 12:21:46.183] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

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

(/usr/lib/f-spot/f-spot.exe:3081): 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 2867 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.)
kim@Kimhs:~$