F-Spot crashes immediately after start

Bug #529948 reported by Siddharth Fadnis
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: f-spot

This bug is similar to other "F-Spot Crash" event logged already. However, I tried running F-Spot from console, and found errors I have been receiving are different than given in support forums. Complete removal and re-install did not help either.

Here is message after issuing command f-spot from console
-----------------------------
(/usr/lib/f-spot/f-spot.exe:21652): GLib-WARNING **: g_set_prgname() called multiple times
[Info 15:59:09.892] Initializing DBus
[Info 15:59:10.034] Initializing Mono.Addins
[Info 15:59:10.239] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (/usr/lib/f-spot/f-spot.exe:21652): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 15:59:11.157] Starting BeagleService
[Info 15:59:11.187] Hack for gnome-settings-daemon engaged

(/usr/lib/f-spot/f-spot.exe:21652): 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 2904 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.)
--------------------------------------------
Here is message after issuing command gksudo f-spot from console:
------------------------------------------------
** No session dbus found. Starting one **
[Info 16:00:25.323] Initializing DBus
[Info 16:00:25.499] Initializing Mono.Addins
[Info 16:00:25.703] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

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

(/usr/lib/f-spot/f-spot.exe:21665): 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 2942 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: Mon Mar 1 15:56:42 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: f-spot 0.6.1.5-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: f-spot
Uname: Linux 2.6.31-19-generic i686

Revision history for this message
Siddharth Fadnis (sidfadnis) 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 → Medium
status: New → Incomplete
Revision history for this message
Siddharth Fadnis (sidfadnis) wrote :

Sorry I am not well versed with ubuntu/linux technical terms. By gtk theme, would you mean which flavour/version of ubuntu I have? If yes then I am running i386 desktop edition of ubuntu version 9.10 karmin koala. It is gnome based.

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

the gtk theme is the control theme set in the appearance dialog

Revision history for this message
Siddharth Fadnis (sidfadnis) wrote :

Providing backtrace As learnt from web page "https://wiki.ubuntu.com/Backtrace"
ran the command, mono --debug /usr/lib/f-spot/f-spot.exe
got the output :
--------------------
(/usr/lib/f-spot/f-spot.exe:30077): GLib-WARNING **: g_set_prgname() called multiple times
[Info 19:10:27.550] Initializing DBus
[Info 19:10:27.757] Initializing Mono.Addins
[Info 19:10:28.239] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (/usr/lib/f-spot/f-spot.exe:30077): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 19:10:30.230] Starting BeagleService
[Info 19:10:30.261] Hack for gnome-settings-daemon engaged

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

Please let me know if anything else that I can do. Thanks for your support.

Revision history for this message
Siddharth Fadnis (sidfadnis) wrote :

@Sebastien Bacher, thanks for the info ! I am using "New Wave" theme.

Revision history for this message
Siddharth Fadnis (sidfadnis) wrote :

********* IMP INFO *************************
Hi, I changed the theme to "Human" and now F-Spot is working just fine.

Revision history for this message
Sebastien Bacher (seb128) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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