[Bug 224153] Re: f-spot won't start (SIGABRT)

** Changed in: f-spot Importance: Unknown => Critical -- f-spot won't start (SIGABRT) https://bugs.launchpad.net/bugs/224153 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com htt

[Bug 224153] Re: f-spot won't start (SIGABRT)

** Changed in: f-spot Status: Unknown => Fix Released -- f-spot won't start (SIGABRT) https://bugs.launchpad.net/bugs/224153 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 224153] Re: f-spot won't start (SIGABRT)

that's fixed on intrepid now with f-spot 0.4.4, thanks. ** Bug watch added: GNOME Bug Tracker #529380 http://bugzilla.gnome.org/show_bug.cgi?id=529380 ** Also affects: f-spot via http://bugzilla.gnome.org/show_bug.cgi?id=529380 Importance: Unknown Status: Unknown ** Changed in: f

[Bug 224153] Re: f-spot won't start (SIGABRT)

In the end I persevered and created a new f-spot database from scratch -- I then got my hands dirty in sqlite and inserted my old data, converting to the new database format as I went along. (I was sure that renaming my ~/.gnome2/f-spot still hadn't worked, but I must have been wrong). I have kep

[Bug 224153] Re: f-spot won't start (SIGABRT)

thanks for your report, may you run f-spot --debug &> f-spot-debug.txt, reproduce the crash and attach that file to the report? thanks. ** Changed in: f-spot (Ubuntu) Importance: Undecided => Medium Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs) Status: New => Incomple

[Bug 224153] Re: f-spot won't start (SIGABRT)

** Attachment added: "f-spot_err" http://launchpadlibrarian.net/14011577/f-spot_err -- f-spot won't start (SIGABRT) https://bugs.launchpad.net/bugs/224153 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list u