crashes when opened

Bug #477953 reported by xjoshdenx
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: f-spot

[Info 00:37:07.191] Initializing DBus
[Info 00:37:07.375] Initializing Mono.Addins
[Info 00:37:07.628] Starting new FSpot server (f-spot 0.6.1.4)

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

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

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

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

** (f-spot:3515): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 00:37:08.907] Starting BeagleService
[Info 00:37:08.936] Hack for gnome-settings-daemon engaged

(f-spot:3515): 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 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: Sun Nov 8 00:39:09 2009
DistroRelease: Ubuntu 9.10
Package: f-spot 0.6.1.4-0ubuntu1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: f-spot
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
xjoshdenx (kentgrungeruk) wrote :
summary: - KAMIC F-Spot crashes when opened
+ [karmic] F-Spot crashes when opened
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote : Re: [karmic] F-Spot crashes when opened

Hi xjoshdenx
I am unable to reproduce this on my system. Can you provide us with a backtrace please?
There are instructions on how to get the debugging version of the program at https://wiki.ubuntu.com/DebuggingProgramCrash
You will need to install these to provide a backtrace, which you can get full instructions for at https://wiki.ubuntu.com/Backtrace
Just follow these step by step and if you get stuck let us know.
Thank you. :)

Changed in f-spot (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Sorry f-spot is a mono application I forgot, you just need to run
mono --debug /usr/lib/f-spot/f-spot.exe
Thank you.

Revision history for this message
xjoshdenx (kentgrungeruk) wrote :

denva@denva-laptop:~$ mono --debug /usr/lib/f-spot/f-spot.exe
[Info 01:14:10.559] Initializing DBus
[Info 01:14:10.780] Initializing Mono.Addins
[Info 01:14:11.137] Starting new FSpot server (f-spot 0.6.1.4)

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

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

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

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

** (f-spot:1931): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 01:14:12.450] Starting BeagleService
[Info 01:14:12.485] Hack for gnome-settings-daemon engaged

(f-spot:1931): 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 2951 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.)

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

It seems to be the same output, but you have provided enough information to step this bug report up to the Triaged status. I shall mark this as such and let the developers handle it from here. Once again thank you for this bug report.

Changed in f-spot (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

What theme do you use?

Changed in f-spot (Ubuntu):
status: Triaged → Incomplete
summary: - [karmic] F-Spot crashes when opened
+ crashes when opened
Revision history for this message
meist3r (meist3r) wrote :

Same behavior here on fresh Karmic install (updates as of 13-11-2009) / f-spot 0.6.1.5-0ubuntu1

Kernel 2.6.31-14-generic
Theme used: New Wave (Dark Menus)

$ mono --debug /usr/lib/f-spot/f-spot.exe
[Info 03:02:17.493] Initializing DBus
[Info 03:02:17.701] Initializing Mono.Addins
[Info 03:02:18.043] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

** (f-spot:14447): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Info 03:02:19.237] Starting BeagleService
[Info 03:02:19.269] Hack for gnome-settings-daemon engaged

(f-spot:14447): 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 2866 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.)

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

the new wave issue is bug #411941

Revision history for this message
Mary Strimel (mary-strimel) wrote :
Download full text (6.1 KiB)

hello,
I don't use New Wave but I am also getting this crash in Mythbuntu RC1 AMD64. If I delete photos.db then f-spot will run; however I have 6 years worth of tagged photos in the database so I really need it to work with my photos.db. The terminal output of f-spot --debug is below:

mary@mythbox:~/.config/f-spot$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 19:53:53.675] Initializing DBus
[Debug 19:53:53.775] DBusInitialization took 0.092495s
[Info 19:53:53.775] Initializing Mono.Addins
[Debug 19:53:53.911] Mono.Addins Initialization took 0.136071s
[Info 19:53:53.916] Starting new FSpot server (f-spot 0.6.1.5)
[Debug 19:53:54.150] Db Initialization took 0.18078s

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

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

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

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

** (f-spot:5255): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[Warn 19:53:54.547] Caught an exception - URI scheme must start with a letter and must consist of one of alphabet, digits, '+', '-' or '.' character. (in `System')
  at System.Uri.Parse (UriKind kind, System.String uriString) [0x00000]
  at System.Uri.ParseUri (UriKind kind) [0x00000]
  at System.Uri..ctor (System.Uri baseUri, System.String relativeUri, Boolean dontEscape) [0x00000]
  at System.Uri..ctor (System.Uri baseUri, System.String relativeUri) [0x00000]
  at FSpot.Widgets.FolderTreeModel.UpdateFolderTree () [0x00000]
  at FSpot.Widgets.FolderTreeModel..ctor () [0x00000]
  at FSpot.Widgets.FolderTreeView..ctor () [0x00000]
  at FSpot.Widgets.FolderTreePage..ctor () [0x00000]
  at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (object,object[],System.Exception&)
  at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
Exception has been thrown by the target of an invocation. (in `mscorlib')
  at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000]
  at System.Activator.CreateInstance (System.Type type, Boolean nonPublic) [0x00000]
  at Mono.Addins.RuntimeAddin.CreateInstance (System.String typeName, Boolean throwIfNotFound) [0x00000]
  at Mono.Addins.RuntimeAddin.CreateInstance (System.String typeName) [0x00000]
  at FSpot.Widgets.SidebarPageNode.GetSidebarPage () [0x00000]
  at MainWindow.OnSidebarExtensionChanged (System.Object s, Mono.Addins.ExtensionNodeEventArgs args) [0x00000]
  at Mono.Addins.ExtensionNode.OnChildNodeAd...

Read more...

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.