f-spot crashes on startup when using the New Wave theme

Bug #485356 reported by Mondo1287
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: f-spot

f-spot crashes on startup when using the New Wave theme on 9.10. I tried all of the other built-in themes and they work fine, but when using New Wave I get the following:

** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 10:41:14.569] Initializing DBus
[Debug 10:41:14.782] DBusInitialization took 0.192311s
[Info 10:41:14.782] Initializing Mono.Addins
[Debug 10:41:15.096] Mono.Addins Initialization took 0.313743s
[Info 10:41:15.120] Starting new FSpot server (f-spot 0.6.1.5)
[Debug 10:41:15.505] Db Initialization took 0.24509s

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

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

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

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

** (f-spot:10647): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Debug 10:41:15.988] Query Started : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC
[Debug 10:41:15.996] QueryToTemp took 0.008014s : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC
[Debug 10:41:15.996] Reloading the query took 0.012693s
[Debug 10:41:16.283] PhotosPerMonth took 0.003965s
[Debug 10:41:16.286] TimeAdaptor REAL Reload took 0.230038s
[Debug 10:41:16.436] Query Started : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC
[Debug 10:41:16.443] QueryToTemp took 0.007678s : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC
[Debug 10:41:16.508] Reloading the query took 0.070049s
[Debug 10:41:16.514] Query Started : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC
[Debug 10:41:16.520] QueryToTemp took 0.005855s : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC
[Debug 10:41:16.537] Reloading the query took 0.023428s
[Info 10:41:16.543] Starting BeagleService
[Debug 10:41:16.544] BeagleService startup took 1.9E-05s
[Info 10:41:16.586] Hack for gnome-settings-daemon engaged

(f-spot:10647): 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.
[Debug 10:41:16.659] PhotosPerMonth took 0.009958s
[Debug 10:41:16.659] TimeAdaptor REAL Reload took 0.139103s
[Debug 10:41:16.734] PhotosPerMonth took 0.000638s
[Debug 10:41:16.734] TimeAdaptor REAL Reload took 0.213916s
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 2891 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.)

Mondo1287 (mondo1287)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in f-spot (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.