F-spot crashes with an X BadRequest when import initiated.

[Martin Ling]

Binary package hint: f-spot

F-spot crashes immediately when I click the Import button.

I'm running Karmic, updated today. F-spot has worked for me within the last week or two. I have tried removing my ~/.config/f-spot/ directory, suspecting database corruption, but I get the same result with a clean start.

Running from a terminal, I see:

[Info 20:43:41.068] Initializing DBus
[Info 20:43:41.239] Initializing Mono.Addins
[Info 20:43:41.464] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (f-spot:23317): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 20:43:42.578] Starting BeagleService
[Info 20:43:42.600] Hack for gnome-settings-daemon engaged

(f-spot:23317): 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 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 2366 error_code 1 request_code 135 minor_code 19)
  (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 Nov 21 20:39:54 2009
DistroRelease: Ubuntu 9.10
Package: f-spot 0.6.1.5-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: f-spot
Uname: Linux 2.6.31-14-generic i686

[Sebastien Bacher (seb128)]

Thank you for your bug report, what gtk theme do you use?

[Martin Ling (martin-launchpad)]

I'm using ClearLooks.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace 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.

[Sebastien Bacher (seb128)]

The issue look similar to bug #411941 but is probably not a duplicate since clearlooks doesn't have the issue

[CMB (magnus-bjureblad)]

Same problem.
Ubuntu 9.10
Theme: Human-Clearlooks

** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 20:03:09.432] Initializing DBus
[Debug 20:03:09.694] DBusInitialization took 0,240622s
[Info 20:03:09.695] Initializing Mono.Addins
[Debug 20:03:10.051] Mono.Addins Initialization took 0,356382s
[Info 20:03:10.080] Starting new FSpot server (f-spot 0.6.1.5)
[Debug 20:03:10.467] Db Initialization took 0,106226s

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

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

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

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

** (f-spot:6713): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Debug 20:03:11.022] 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 20:03:11.025] QueryToTemp took 0,003101s : 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 20:03:11.026] Reloading the query took 0,007683s
[Debug 20:03:11.330] PhotosPerMonth took 0,04462s
[Debug 20:03:11.339] TimeAdaptor REAL Reload took 0,270878s
[Debug 20:03:11.481] 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 20:03:11.482] QueryToTemp took 0,001186s : 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 20:03:11.541] Reloading the query took 0,061244s
[Debug 20:03:11.548] 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 20:03:11.553] QueryToTemp took 0,005055s : 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 20:03:11.569] Reloading the query took 0,021789s
[Info 20:03:11.579] Starting BeagleService
[Debug 20:03:11.582] BeagleService startup took 4,1E-05s
[Info 20:03:11.629] Hack for gnome-settings-daemon engaged

(f-spot:6713): 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 20:03:11.704] PhotosPerMonth took 0,009822s
[Debug 20:03:11.704] TimeAdaptor REAL Reload took 0,150725s
[Debug 20:03:11.785] PhotosPerMonth took 0,022472s
[Debug 20:03:11.786] TimeAdaptor REAL Reload took 0,231854s
The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 2662 error_code 1 request_code 135 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your...

[Martin Ling (martin-launchpad)]

The problem has now gone away after some other updates, although I don't recall seeing f-spot or mono amongst them.

CMB, can you still reproduce this? If so, can you post the results of running mono --debug /usr/lib/f-spot/f-spot.exe ?

[CMB (magnus-bjureblad)]

I still have the same problem.

Running mono --debug /usr/lib/f-spot/f-spot.exe

[Info 22:34:50.998] Initializing DBus
[Info 22:34:51.242] Initializing Mono.Addins
[Info 22:34:51.602] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (f-spot:5026): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 22:34:52.954] Starting BeagleService
[Info 22:34:52.987] Hack for gnome-settings-daemon engaged

(f-spot:5026): 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 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 2249 error_code 1 request_code 135 minor_code 19)
  (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.)

[mavosaure (mavosaure)]

Architecture: i386
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: wl
Package: f-spot 0.6.1.5-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
Uname: Linux 2.6.31-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[mavosaure (mavosaure)]

Same symptoms : but it crashes when I launch F-Spot.
My theme is "New Wave"
(duplicate from bug #411941?)

~$ f-spot

(/usr/lib/f-spot/f-spot.exe:3218): GLib-WARNING **: g_set_prgname() called multiple times
[Info 20:33:54.205] Initializing DBus
[Info 20:33:54.318] Initializing Mono.Addins
[Info 20:33:54.515] Starting new FSpot server (f-spot 0.6.1.5)

** (/usr/lib/f-spot/f-spot.exe:3218): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:3218): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:3218): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:3218): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (/usr/lib/f-spot/f-spot.exe:3218): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 20:33:55.280] Starting BeagleService
[Info 20:33:55.299] Hack for gnome-settings-daemon engaged

(/usr/lib/f-spot/f-spot.exe:3218): 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 '/usr/lib/f-spot/f-spot.exe' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 2971 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.)

[Sebastien Bacher (seb128)]

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