F-Spot crash on start when using new wave theme

[rfrerebe]

Binary package hint: f-spot

With a karmic Beta up to date, fspot crash at startup

See below

familly@largo:~$ f-spot
[Info 14:12:36.747] Initializing DBus
[Info 14:12:36.831] Initializing Mono.Addins
[Info 14:12:36.957] Starting new FSpot server (f-spot 0.6.1.3)
[Info 14:12:37.530] Starting BeagleService
[Info 14:12:37.547] Hack for gnome-settings-daemon engaged

(f-spot:7598): 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 2905 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.)

ProblemType: Bug
Architecture: i386
Date: Sat Oct 3 14:13:41 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: f-spot 0.6.1.3-1ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: f-spot
Uname: Linux 2.6.31-11-generic i686

[Ed Howland (ed-howland)]

Unable to reproduce this in Karmic/F-Spot (f-spot 0.6.1.3-1ubuntu1) running VirtualBox.(i386)

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[bcudda (cannondalef5002)]

I had the same problem. Best output I could get was

f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 22:58:25.251] Initializing DBus
[Debug 22:58:25.723] DBusInitialization took 0.426689s
[Info 22:58:25.723] Initializing Mono.Addins
[Debug 22:58:26.408] Mono.Addins Initialization took 0.68464s
[Info 22:58:26.460] Starting new FSpot server (f-spot 0.6.1.3)
[Debug 22:58:26.937] Db Initialization took 0.227139s
[Debug 22:58:27.965] 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 22:58:27.967] QueryToTemp took 0.002191s : 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 22:58:27.968] Reloading the query took 0.011748s
[Debug 22:58:28.266] PhotosPerMonth took 0.021088s
[Debug 22:58:28.277] TimeAdaptor REAL Reload took 0.239155s
[Debug 22:58:28.848] 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 22:58:28.859] QueryToTemp took 0.010771s : 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 22:58:28.998] Reloading the query took 0.152216s
[Debug 22:58:29.010] 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 22:58:29.014] QueryToTemp took 0.003862s : 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 22:58:29.027] Reloading the query took 0.018058s
[Info 22:58:29.041] Starting BeagleService
[Debug 22:58:29.044] BeagleService startup took 3.7E-05s
[Debug 22:58:29.086] PhotosPerMonth took 0.012301s
[Debug 22:58:29.088] TimeAdaptor REAL Reload took 0.072808s
[Info 22:58:29.123] Hack for gnome-settings-daemon engaged

(f-spot:1973): 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 22:58:29.240] PhotosPerMonth took 0.019861s
[Debug 22:58:29.240] TimeAdaptor REAL Reload took 0.225377s
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 3810 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.)

[Chris Brotherton (protonchris)]

The bug seems to be related to the gtk theme. Take a look at comment #8 at https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/411941

[rfrerebe (remy)]

Hello

Correct, I was using (and still using this theme)
Now this problem is fixed.

You can close the bug

Thanks everyone for your help

[Lucas Bxxx (splidtter)]

most likely a duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-themes-ubuntu/+bug/411941