The program 'f-spot' received an X Window System error

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.

What videocard and driver do you use? Do you use the desktop effects option?

I can confirm the same sympton. Please find trace attached. Full trace is > 300mb so I only attached the trace of the main assembly.

Hi,

Same problem here...
I Use the free ATI-Video driver and have 2 Screens.
My Grafic Card is the ATI Radeon 9600.

I get the following, using the free ATI driver:

** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 16:48:26.464] Initializing DBus
[Debug 16:48:26.680] DBusInitialization took 0.194245s
[Info 16:48:26.680] Initializing Mono.Addins
[Debug 16:48:27.028] Mono.Addins Initialization took 0.347509s
[Info 16:48:27.040] Starting new FSpot server
[Debug 16:48:27.424] Db Initialization took 0.162567s
[Debug 16:48:27.951] QueryToTemp took 0.001183s : 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:48:28.209] PhotosPerMonth took 0.009462s
[Debug 16:48:28.212] TimeAdaptor REAL Reload took 0.231012s
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 329 error_code 1 request_code 156 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.)

I also use the ATI driver; that seems to be a common factor. (No Desktop Effects for me.)

I have the same problem. I'm using "ati" free driver.

Thanks!

Yeah, I'm also using the ATI driver

I am also affected with this problem.

Same problem here. Ubuntu 8.10 on AMD64 with ATI (unsure about free or restricted) drivers (Radeon 9700Pro videocard).

** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 14:19:06.949] Initializing DBus
[Debug 14:19:07.069] DBusInitialization took 0.110399s
[Info 14:19:07.069] Initializing Mono.Addins
[Debug 14:19:07.259] Mono.Addins Initialization took 0.189489s
[Info 14:19:07.266] Starting new FSpot server
[Debug 14:19:07.450] Db Initialization took 0.132095s
[Debug 14:19:07.637] Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time
[Debug 14:19:08.015] Query took 0.377669s
[Debug 14:19:08.032] Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time
[Debug 14:19:08.173] Query took 0.141043s
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 360 error_code 1 request_code 156 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.)

For some reason the Network Manager applet always showed: no network, although I did have an active (wired) network connection. While not doing anything special (just browsing in Firefox), I suddenly got errors about having no network connection. So I created one in the Network Manager (wired, manual) and now f-spot works.... Can't see the connection between the two, but I thought I'd share this information.

HTH

Latest kernel update to 2.6.27-11 and now f-spot gives me the same error again. I even build f-spot from the sources and that gives the same error. GREAT :-(

we still need a backtrace without one the bug is no use for the developers in order to fix it. thanks.

Can't backtrace a mono-app with GDB, and mono --debug gives similar error as already stated above:

switchbl8@rrs01:~$ mono --debug /usr/lib/f-spot/f-spot.exe
[Info 13:09:20.131] Initializing DBus
[Info 13:09:20.463] Initializing Mono.Addins
[Info 13:09:20.995] Starting new FSpot server
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 331 error_code 1 request_code 157 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.)

or

switchbl8@rrs01:~$ mono --debug /usr/lib/f-spot/f-spot.exe --debug
[Info 13:10:52.522] Initializing DBus
[Debug 13:10:52.855] DBusInitialization took 0.304061s
[Info 13:10:52.855] Initializing Mono.Addins
[Debug 13:10:53.381] Mono.Addins Initialization took 0.525691s
[Info 13:10:53.398] Starting new FSpot server
[Debug 13:10:53.622] Db Initialization took 0.120978s
[Debug 13:10:54.245] QueryToTemp took 0.288803s : 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 13:10:54.437] Query took 0.026026s : SELECT * FROM photoquery_temp_0 LIMIT 100 OFFSET 0
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 331 error_code 1 request_code 157 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.)

So, please tell me how to create a backtrace, and I will do so.

I updated the xserver-xorg-video-ati and it's dependencies to the current version in the Jaunty repos (1:6.10.0-1ubuntu1) and f-spot once again starts and runs properly.

Sorry people, I upgraded my system (today), and switched to NVidia. Same installation, no problem whatsoever with f-spot. So definitely ATI related.

Tried with radeon / radeonhd drivers, with an integrated Radeon 1250 card, and both crash.

I'm just surprised this bug is only rated "medium", since like many other people, my parents only use this computer for internet / mails, movies and pictures, and loosing one of the three makes them a bit... loud ^^

Hey guys.

This did the trick for me:

sudo apt-get remove --purge xorg-driver-fglrx

Don't ask me why

On Sat, Feb 7, 2009 at 9:38 AM, fleiber <email address hidden> wrote:

> Tried with radeon / radeonhd drivers, with an integrated Radeon 1250
> card, and both crash.
>
> I'm just surprised this bug is only rated "medium", since like many
> other people, my parents only use this computer for internet / mails,
> movies and pictures, and loosing one of the three makes them a bit...
> loud ^^
>
> --
> The program 'f-spot' received an X Window System error
> https://bugs.launchpad.net/bugs/286544
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "f-spot" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: f-spot
>
> At the moment I can't open F-Spot at all. Same ultimate error if I move my
> ~/.gnome2/f-spot folder.
>
> Version: 0.5.0.3-0ubuntu1
>
> andrew:~ f-spot --debug -v Desktop/virus.png
> ** Running f-spot in Debug Mode **
> ** Running Mono with --debug **
> [Info 14:05:22.563] Initializing DBus
> [Debug 14:05:22.804] DBusInitialization took 0.195818s
> [Info 14:05:22.805] Initializing Mono.Addins
> [Debug 14:05:23.164] Mono.Addins Initialization took 0.359255s
> [Info 14:05:23.179] Starting new FSpot server
> uri = file:///home/andrew/Desktop/virus.png
> 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 436 error_code 1 request_code 143 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.)
>
> andrew:~ f-spot --debug
> ** Running f-spot in Debug Mode **
> ** Running Mono with --debug **
> [Info 14:10:30.604] Initializing DBus
> [Debug 14:10:30.844] DBusInitialization took 0.218779s
> [Info 14:10:30.844] Initializing Mono.Addins
> [Debug 14:10:31.200] Mono.Addins Initialization took 0.3552s
> [Info 14:10:31.214] Starting new FSpot server
> [Debug 14:10:31.745] Db Initialization took 0.418179s
> [Debug 14:10:32.606] QueryToTemp took 0.102026s : SELECT id, time, uri,
> description, roll_id, default_version_id, rating, md5_sum FROM photos ORDER
> BY time DESC
> [Debug 14:10:33.033] PhotosPerMonth took 0.144338s
> [Debug 14:10:33.036] TimeAdaptor REAL Reload took 0.356263s
> [Debug 14:10:33.143] Query took 0.030657s : SELECT * FROM photoquery_temp_0
> LIMIT 100 OFFSET 0
> 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 332 error_code 1 request_code 143 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...

Is there a fix for this bug?

I have just upgraded to Jaunty alpha6 ( http://www.ubuntu.com/testing/jaunty/alpha6 ) and have found that f-spot is now working again.

Same error under jaunty - running an ATI card with radeonhd drivers with probably uncleanly uninstalled fglrx drivers. I'll switch to an NVIDIA card this week - if the problem goes away then, it's definitely ATI related.

~$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 00:26:35.076] Initializing DBus
[Debug 00:26:35.202] DBusInitialization took 0,112556s
[Info 00:26:35.202] Initializing Mono.Addins
[Debug 00:26:35.411] Mono.Addins Initialization took 0,209153s
[Info 00:26:35.420] Starting new FSpot server
[Debug 00:26:35.630] Db Initialization took 0,094214s
[Debug 00:26:36.077] QueryToTemp took 0,005638s : 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 00:26:36.304] PhotosPerMonth took 0,005695s
[Debug 00:26:36.307] TimeAdaptor REAL Reload took 0,213518s
[Debug 00:26:36.337] Query took 0,036138s : SELECT * FROM photoquery_temp_0 LIMIT 100 OFFSET 0
The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 421 error_code 2 request_code 153 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.)

Same with me, but have just upgraded to Ubuntu 9.10. Also using a NVIDIA 7600GS card.

~$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 22:12:55.822] Initializing DBus
[Debug 22:12:56.077] DBusInitialization took 0.230039s
[Info 22:12:56.078] Initializing Mono.Addins
[Debug 22:12:56.400] Mono.Addins Initialization took 0.321732s
[Info 22:12:56.423] Starting new FSpot server (f-spot 0.6.1.4)
[Debug 22:12:56.750] Db Initialization took 0.203674s

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

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

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

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

** (f-spot:3446): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Debug 22:12:57.297] 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:12:57.302] QueryToTemp took 0.004988s : 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:12:57.302] Reloading the query took 0.010374s
[Debug 22:12:57.580] PhotosPerMonth took 0.011306s
[Debug 22:12:57.583] TimeAdaptor REAL Reload took 0.223997s
[Debug 22:12:57.886] 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:12:57.893] QueryToTemp took 0.006553s : 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:12:58.003] Reloading the query took 0.117038s
[Debug 22:12:58.008] 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:12:58.009] QueryToTemp took 0.001278s : 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:12:58.028] Reloading the query took 0.020703s
[Info 22:12:58.038] Starting BeagleService
[Debug 22:12:58.039] BeagleService startup took 2.1E-05s
[Info 22:12:58.095] Hack for gnome-settings-daemon engaged

(f-spot:3446): 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:12:58.162] PhotosPerMonth took 0.040602s
[Debug 22:12:58.162] TimeAdaptor REAL Reload took 0.153003s
[Debug 22:12:58.236] PhotosPerMonth took 0.019999s
[Debug 22:12:58.237] TimeAdaptor REAL Reload took 0.227247s
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 3892 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the...

what theme do you use?

Hi,

I am using a geforce 6600GT graphic card. I experimented the same bug still I installed Ubuntu 9.10
At run command:

[Info 10:20:03.436] Initializing DBus
[Info 10:20:03.659] Initializing Mono.Addins
[Info 10:20:03.961] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (f-spot:1901): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 10:20:05.781] Starting BeagleService
[Info 10:20:05.820] Hack for gnome-settings-daemon engaged

(f-spot:1901): 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 5096 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.)

Just after installing a fully fresh Ubuntu 9.10, I changed the Theme to be "New wave". After some time, I tried to open F-Spot for first time, and crash, same error as Roussillon's.

I change the theme back to default "Human", started F-Spot and voilà, it worked.

I changed the theme again to "New wave", and re-voilà, it also works now...

Not quite familiar with mono-based stuff, so can't tell why I got it solved just changing the Theme...

Oh wait... no, still happening here with the "New wave" theme... It seems I need to keep the "Human" theme to have it working properly...

I confirm what Aleksander Morgado just said.
F-Spot works with "Human" theme, but not with "New Wave".

the new wave theme issue is a known one, is everybody there using this one?

duplicate bug #411941

for some time now I have been receiving these emails. However I became
connected with the Bug, I am not sure. I am sure, however, that I do not
have the technical expertise to cope with the issues. Please, therefore,
arrange for me to be taken form the list.

Thank you

John Tearnan