[ubuntu-mono] [Bug 477953] Re: crashes when opened

meist3r markus.napp at gmail.com
Fri Nov 13 02:06:52 UTC 2009


Same behavior here on fresh Karmic install (updates as of 13-11-2009) /
f-spot 0.6.1.5-0ubuntu1

Kernel 2.6.31-14-generic
Theme used: New Wave (Dark Menus)

$ mono --debug /usr/lib/f-spot/f-spot.exe
[Info  03:02:17.493] Initializing DBus
[Info  03:02:17.701] Initializing Mono.Addins
[Info  03:02:18.043] Starting new FSpot server (f-spot 0.6.1.5)

** (f-spot:14447): CRITICAL **: atk_object_set_name: assertion `name !=
NULL' failed

** (f-spot:14447): CRITICAL **: atk_object_set_name: assertion `name !=
NULL' failed

** (f-spot:14447): CRITICAL **: atk_object_set_name: assertion `name !=
NULL' failed

** (f-spot:14447): CRITICAL **: atk_object_set_name: assertion `name !=
NULL' failed

** (f-spot:14447): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info  03:02:19.237] Starting BeagleService
[Info  03:02:19.269] Hack for gnome-settings-daemon engaged

(f-spot:14447): 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 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 2866 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.)

-- 
crashes when opened
https://bugs.launchpad.net/bugs/477953
You received this bug notification because you are a member of MOTU Mono
Team, which is subscribed to f-spot in ubuntu.




More information about the Ubuntu-mono mailing list