[ubuntu-mono] [Bug 474960] Re: F-Spot Crashes on Startup on Dell Mini 10v

[ThePol]

I am using New Wave. This is a theme that came with the standard 9.10
install. Why would this matter and cause F-Spot to crash?

** Description changed:

  Binary package hint: f-spot
  
- F-Spot won't start. I am running Ubuntu 9.10 and version 0.6.1.4-0ubuntu1 of F-Spot. The Dell Mini 10v has the 950 GMA graphic chipset (if that helps). I'm running the stock drivers.
+ F-Spot won't start. I am running Ubuntu 9.10 and version
+ 0.6.1.4-0ubuntu1 of F-Spot. The Dell Mini 10v has the 950 GMA graphic
+ chipset (if that helps). I'm running the stock drivers.
+ 
+ I am using New Wave as my theme.
+ 
  -------------------------------------------------------------------------
  [Info  20:04:41.449] Initializing DBus
  [Info  20:04:41.765] Initializing Mono.Addins
  [Info  20:04:42.196] Starting new FSpot server (f-spot 0.6.1.4)
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
  [Info  20:04:44.417] Starting BeagleService
  [Info  20:04:44.466] Hack for gnome-settings-daemon engaged
  
  (f-spot:3231): 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 2948 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.)
+   (Details: serial 2948 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 Nov  4 19:59:15 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: wl
  Package: f-spot 0.6.1.4-0ubuntu1
  ProcEnviron:
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: f-spot
  Uname: Linux 2.6.31-14-generic i686

** Description changed:

  Binary package hint: f-spot
  
  F-Spot won't start. I am running Ubuntu 9.10 and version
  0.6.1.4-0ubuntu1 of F-Spot. The Dell Mini 10v has the 950 GMA graphic
- chipset (if that helps). I'm running the stock drivers.
- 
- I am using New Wave as my theme.
+ chipset (if that helps). I'm running the stock video drivers. I am using
+ New Wave as my theme.
  
  -------------------------------------------------------------------------
  [Info  20:04:41.449] Initializing DBus
  [Info  20:04:41.765] Initializing Mono.Addins
  [Info  20:04:42.196] Starting new FSpot server (f-spot 0.6.1.4)
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name !=
  NULL' failed
  
  ** (f-spot:3231): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
  [Info  20:04:44.417] Starting BeagleService
  [Info  20:04:44.466] Hack for gnome-settings-daemon engaged
  
  (f-spot:3231): 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 2948 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 Nov  4 19:59:15 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: wl
  Package: f-spot 0.6.1.4-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: f-spot
  Uname: Linux 2.6.31-14-generic i686

-- 
F-Spot Crashes on Startup on Dell Mini 10v
https://bugs.launchpad.net/bugs/474960
You received this bug notification because you are a member of MOTU Mono
Team, which is subscribed to f-spot in ubuntu.