Ubuntu
f-spot package

F-Spot fails to run

Bug #503870 reported by Steve Cole
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: f-spot

Get following output when launching F-Spot from command line in Ubuntu 9.10 -

(/usr/lib/f-spot/f-spot.exe:3068): GLib-WARNING **: g_set_prgname() called multiple times
[Info 16:40:02.813] Initializing DBus
[Info 16:40:03.004] Initializing Mono.Addins
[Info 16:40:03.339] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 16:40:04.702] Starting BeagleService
[Info 16:40:04.733] Hack for gnome-settings-daemon engaged

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

ProblemType: Bug
Architecture: i386
Date: Wed Jan 6 16:47:44 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Package: f-spot 0.6.1.5-0ubuntu1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: f-spot
Uname: Linux 2.6.31-16-generic i686

Revision history for this message
Steve Cole (sjrkcole) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Changed in f-spot (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Steve Cole (sjrkcole) wrote : Re: [Bug 503870] Re: F-Spot fails to run

I've been using New Wave. Just tried 'Dust', and F-Spot works. What
precisely is the cause of the problem?

Steve

2010/1/7 Sebastien Bacher <email address hidden>

> Thank you for your bug report, what gtk theme do you use?
>
> ** Changed in: f-spot (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: f-spot (Ubuntu)
> Status: New => Incomplete
>
> --
> F-Spot fails to run
> https://bugs.launchpad.net/bugs/503870
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “f-spot” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: f-spot
>
> Get following output when launching F-Spot from command line in Ubuntu 9.10
> -
>
> (/usr/lib/f-spot/f-spot.exe:3068): GLib-WARNING **: g_set_prgname() called
> multiple times
> [Info 16:40:02.813] Initializing DBus
> [Info 16:40:03.004] Initializing Mono.Addins
> [Info 16:40:03.339] Starting new FSpot server (f-spot 0.6.1.5)
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
> [Info 16:40:04.702] Starting BeagleService
> [Info 16:40:04.733] Hack for gnome-settings-daemon engaged
>
> (/usr/lib/f-spot/f-spot.exe:3068): 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 2943 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.)
>
> ProblemType: Bug
> Architecture: i386
> Date: Wed Jan 6 16:47:44 2010
> DistroRelease: Ubuntu 9.10
> InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386
> (20091020.3)
> Package: f-spot 0.6.1.5-0ubuntu1
> ProcEnviron:
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
> SourcePackage: f-spot
> Uname: Linux 2.6.31-16-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/503870/+subscribe
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

that's a known issue with this theme, see bug #411941

Changed in f-spot (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Steve Cole (sjrkcole) wrote :

Just to say that F-Spot is a superb application - thanks for your efforts!

Steve

2010/1/7 Sebastien Bacher <email address hidden>

> *** This bug is a duplicate of bug 411941 ***
> https://bugs.launchpad.net/bugs/411941
>
> that's a known issue with this theme, see bug #411941
>
> ** Changed in: f-spot (Ubuntu)
> Status: Incomplete => Invalid
>
> ** This bug has been marked a duplicate of bug 411941
> f-spot.exe crashes when using new wave theme
>
> --
> F-Spot fails to run
> https://bugs.launchpad.net/bugs/503870
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “f-spot” package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: f-spot
>
> Get following output when launching F-Spot from command line in Ubuntu 9.10
> -
>
> (/usr/lib/f-spot/f-spot.exe:3068): GLib-WARNING **: g_set_prgname() called
> multiple times
> [Info 16:40:02.813] Initializing DBus
> [Info 16:40:03.004] Initializing Mono.Addins
> [Info 16:40:03.339] Starting new FSpot server (f-spot 0.6.1.5)
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
>
> ** (/usr/lib/f-spot/f-spot.exe:3068): CRITICAL **: atk_object_set_name:
> assertion `name != NULL' failed
> [Info 16:40:04.702] Starting BeagleService
> [Info 16:40:04.733] Hack for gnome-settings-daemon engaged
>
> (/usr/lib/f-spot/f-spot.exe:3068): 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 2943 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.)
>
> ProblemType: Bug
> Architecture: i386
> Date: Wed Jan 6 16:47:44 2010
> DistroRelease: Ubuntu 9.10
> InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386
> (20091020.3)
> Package: f-spot 0.6.1.5-0ubuntu1
> ProcEnviron:
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
> SourcePackage: f-spot
> Uname: Linux 2.6.31-16-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/503870/+subscribe
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.