when I try to open f-stop, it starts to open then stops, it won't open all the way

To know why a software is crashing, it's always interesting to run it from the command line:
open a terminal in "Accessories", then type "f-stop"
It will run F-spot, make it crash, then check if you see anything interesting in the terminal window.

Thanks, here is the response I got:
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 3786 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

> Your question #129436 on nautilus in ubuntu changed:
> https://answers.edge.launchpad.net/ubuntu/+source/nautilus/+question/129436
>
> Status: Open => Needs information
>
> François Tissandier requested for more information:
> To know why a software is crashing, it's always interesting to run it from
> the command line:
> open a terminal in "Accessories", then type "f-stop"
> It will run F-spot, make it crash, then check if you see anything
> interesting in the terminal window.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.edge.launchpad.net/ubuntu/+source/nautilus/+question/129436
>
> You received this question notification because you are a direct
> subscriber of the question.
>
>

Don't you mean f-spot ?

Thanks, here is the response I got:
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 3786 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
Any advice on what to do next? (I did run f-spot, not f-stop)

> Your question #129436 on nautilus in ubuntu changed:
> https://answers.edge.launchpad.net/ubuntu/+source/nautilus/+question/129436
>
> Status: Open => Needs information
>
> François Tissandier requested for more information:
> To know why a software is crashing, it's always interesting to run it
from the command line:
> open a terminal in "Accessories", then type "f-stop"
> It will run F-spot, make it crash, then check if you see anything
interesting in the terminal window.
>
> --
> To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
> https://answers.edge.launchpad.net/ubuntu/+source/nautilus/+question/129436
>
> You received this question notification because you are a direct
subscriber of the question.
>
>

If you are using Lucid you can run:

sudo add-apt-repository ppa:f-spot/f-spot-ppa; sudo apt-get update; sudo apt-get upgrade

what is Lucid, I can't find it on my computer. Any other suggestions?

What is the output of:

lsb_release -a

Thanks

I ran the commands above (sudo add-apt-repository ppa:f-spot/fspot-ppa; sudo apt-get update; sudo apt-get upgrade) in the terminal in accessories. F-spot is still starting to open then it closes. Is it possible that my computer isn't strong enough to run it? It is a small netbook (Eee PC).

F-Spot may be a bit slow on a netbook, but it should run.
What output do you get when you run "f-spot" in the terminal?

Hi, thank you for your response. Below you will see what I get when I run
f-spot in the terminal:
(/usr/lib/f-spot/f-spot.exe:1884): GLib-WARNING **: g_set_prgname() called
multiple times
[Info 10:22:08.326] Initializing DBus
[Info 10:22:08.729] Initializing Mono.Addins
[Info 10:22:09.614] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

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

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

> Your question #129436 on f-spot in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/f-spot/+question/129436
>
> Status: Open => Needs information
>
> Ulf Rompe requested for more information:
> F-Spot may be a bit slow on a netbook, but it should run.
> What output do you get when you run "f-spot" in the terminal?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/f-spot/+question/129436
>
> You received this question notification because you are a direct
> subscriber of the question.
>
>

(/usr/lib/f-spot/f-spot.exe:1884): GLib-WARNING **: g_set_prgname() called
multiple times
[Info 10:22:08.326] Initializing DBus
[Info 10:22:08.729] Initializing Mono.Addins
[Info 10:22:09.614] Starting new FSpot server (f-spot 0.6.1.5)

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

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

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

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

[Info 10:22:12.817] Starting BeagleService
[Info 10:22:12.876] Hack for gnome-settings-daemon engaged

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

Can anyone give me basic instructions on how to debug this program by "running it with the --sync command line option"? Or is there something else I need to do, do I need to bring my computer to a geek squad?

To run it with this option, open a terminal in the Accessories, then type "f-post --sync"

How many photos do you have ? I don't think it should be a problem, but who knows... F-Spot is not really lightweight.
If you are using Maverick, you could try Shotwell, it's supposed to be much lightweight.