Comment 3 for bug 437402

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:~$