Comment 24 for bug 411941

I replicated the error on my son's machine (running Ubuntu 9.10). Here is
the error -

rowan@rowan-desktop:~$ f-spot

(/usr/lib/f-spot/f-spot.exe:
2038): GLib-WARNING **: g_set_prgname() called multiple times
[Info 18:48:02.630] Initializing DBus
[Info 18:48:02.835] Initializing Mono.Addins
[Info 18:48:03.149] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (/usr/lib/f-spot/f-spot.exe:2038): CRITICAL **: atk_object_set_name:
assertion `name != NULL' failed
[Info 18:48:04.765] Starting BeagleService
[Info 18:48:04.797] Hack for gnome-settings-daemon engaged

(/usr/lib/f-spot/f-spot.exe:2038): 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 2950 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.)

Hope this helps?

Steve

On 21 January 2010 17:40, Sebastien Bacher <email address hidden> wrote:

> Thanks for your bug report. This bug has been reported to the developers
> of the software. You can track it and make comments here:
> https://bugzilla.gnome.org/show_bug.cgi?id=607687
>
> ** Bug watch added: GNOME Bug Tracker #607687
> https://bugzilla.gnome.org/show_bug.cgi?id=607687
>
> ** Changed in: gtk+2.0 (Ubuntu)
> Status: Confirmed => Triaged
>
> ** Bug watch added: GNOME Bug Tracker #607687
> https://bugzilla.gnome.org/show_bug.cgi?id=607687
>
> ** Changed in: gtk
> Importance: Undecided => Unknown
>
> ** Changed in: gtk
> Status: New => Unknown
>
> ** Changed in: gtk
> Remote watch: None => GNOME Bug Tracker #607687
>
> --
> f-spot.exe crashes when using new wave theme
> https://bugs.launchpad.net/bugs/411941
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in GTK+ GUI Toolkit: Unknown
> Status in “gtk+2.0” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: f-spot
>
> Ubuntu 9.10 a3
> updated at 4pm CET 11.08.2009
> f-spot 0.6.0
> Crash at start
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Aug 11 16:01:47 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/lib/f-spot/f-spot.exe
> InterpreterPath: /usr/bin/mono
> NonfreeKernelModules: nvidia
> Package: f-spot 0.6.0.0-1~ubuntu1
> ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe
> ProcEnviron:
> SHELL=/bin/bash
> LANG=ru_RU.UTF-8
> ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
> Signal: 5
> SourcePackage: f-spot
> StacktraceTop:
> ?? () frhostname /usr/lib/libgdk-x11-2.0.so.0
> _XError () frhostname /usr/lib/libX11.so.6
> ?? () frhostname /usr/lib/libX11.so.6
> _XReply () frhostname /usr/lib/libX11.so.6
> XSync () frhostname /usr/lib/libX11.so.6
> Title: f-spot.exe crashed with signal 5 in _XError()
> Uname: Linux 2.6.31-5-generic i686
> UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gtk/+bug/411941/+subscribe
>