i get the same crash on startup, here is the data that i currently can get
(/usr/lib/f-spot/f-spot.exe:4933): GLib-WARNING **: g_set_prgname()
called multiple times
[Info 13:57:14.048] Initializing DBus
[Info 13:57:14.215] Initializing Mono.Addins
[Info 13:57:14.413] Starting new FSpot server (f-spot 0.6.1.5)
** (/usr/lib/f-spot/f-spot.exe:4933): CRITICAL **: atk_object_set_name:
assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:4933): CRITICAL **: atk_object_set_name:
assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:4933): CRITICAL **: atk_object_set_name:
assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:4933): CRITICAL **: atk_object_set_name:
assertion `name != NULL' failed
** (/usr/lib/f-spot/f-spot.exe:4933): CRITICAL **: atk_object_set_name:
assertion `name != NULL' failed
[Info 13:57:15.451] Starting BeagleService
[Info 13:57:15.502] Hack for gnome-settings-daemon engaged
(/usr/lib/f-spot/f-spot.exe:4933): 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 3428 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.)
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
