After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 601289 - F-Spot dont work on ubuntu 9.10
F-Spot dont work on ubuntu 9.10
Status: RESOLVED DUPLICATE of bug 600349
Product: f-spot
Classification: Other
Component: General
0.6.x
Other Linux
: Normal blocker
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-09 18:31 UTC by nyaggi
Modified: 2009-11-10 07:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nyaggi 2009-11-09 18:31:12 UTC
F-Spot don't work... ...the terminal say...

f-spot
[Info  15:00:10.552] Initializing DBus
[Info  15:00:10.713] Initializing Mono.Addins
[Info  15:00:10.912] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (f-spot:5241): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info  15:00:12.355] Starting BeagleService
[Info  15:00:12.414] Hack for gnome-settings-daemon engaged

(f-spot:5241): 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 3216 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.)

Thank you... ...i don't speak english... ...im sorry

Gracias a todos.
Comment 1 Maxxer 2009-11-10 07:28:40 UTC

*** This bug has been marked as a duplicate of bug 600349 ***