F-Spot crashes

Thank you taking the time to report this bug and helping to make Ubuntu better. 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.

Debug Log:

** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 16:54:21.103] Initializing DBus
[Debug 16:54:21.561] DBusInitialization took 0.374578s
[Info 16:54:21.562] Initializing Mono.Addins
[Debug 16:54:22.451] Mono.Addins Initialization took 0.888383s
[Info 16:54:22.480] Starting new FSpot server
[Debug 16:54:23.233] Db Initialization took 0.474811s
[Debug 16:54:24.893] QueryToTemp took 0.023439s : SELECT id, time, uri, description, roll_id, default_version_id, rating, md5_sum FROM photos WHERE id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC
[Debug 16:54:25.167] PhotosPerMonth took 0.007894s
[Debug 16:54:25.173] TimeAdaptor REAL Reload took 0.221859s
[Info 16:54:25.772] Starting BeagleService
[Debug 16:54:25.775] BeagleService startup took 5.5E-05s
[Info 16:54:25.775] Hack for gnome-settings-daemon engaged
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 3264 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.)
jesse@jesse-desktop:~$

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

what theme do you use?

My bug ( lp:488009 ) has been marked a duplicate of this one. Although I'm not sure if it's the same bug (I get different output in the terminal, as far as I can see)

I've submitted the Apport report also, if that helps. I have a feeling it has got to do with the theme I am using. I am using New Wave. I've always had problems with this theme. GNOME-Do used to crash and automatically log me out when I used this theme earlier.

Alright, using the new Human in Karmic I can use F-Spot perfectly. No problem.

Does the New Wave theme work differently from the rest? Maybe, if it has problems, it should not be included for Lucid, which is a LTS?

interesting, i encountered the same exact issue, f-spot will not run when [new wave] theme is the active theme.
i came to figure this out while trying to determine if i had a new f-spot bug and reading Umang comment [#6] here.
why is it an .exe file anyway, creepy.
furthermore, i dont agree this is the same bug.

the new wave issue is known and fixed in lucid does anybody has the issue using an another theme there?

[Expired for f-spot (Ubuntu) because there has been no activity for 60 days.]