Ok, the repro scenario is really easy:  I started from the command line
as you describe ("f-spot --debug &> fspot-log.txt").  Then click the
File menu, then select Quit.  It dies with a segv.  The fspot-log.txt
file is attached.

** Attachment added: "fspot-log.txt"
   http://launchpadlibrarian.net/13443364/fspot-log.txt

-- 
f-spot.exe crashed with SIGSEGV
https://bugs.launchpad.net/bugs/217073
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to