Comments on: In a spot with F-Spot

By: Marius Gedminas

Marius Gedminas — Fri, 27 Mar 2009 12:33:42 +0000

If the pictures are unreadable because of file ownership/permissions, F-Spot should tell you that, not crash. Applications should never crash. Definitely file a bug.

By: Jeffrey Stedfast

Jeffrey Stedfast — Fri, 27 Mar 2009 12:13:23 +0000

I’m of the opinion that any crash is a bug, no matter what caused it (well, short of doing a kill[all] or something).

So yea, I’d say please file a bug report. I’m sure that the f-spot devs feel the same way 🙂

By: Spider

Spider — Fri, 27 Mar 2009 11:52:10 +0000

oh heck yes. I end up with similar bugs a lot of the time ( copy something from one machine to another where you have different usernames on both and you’ll see funky stuff ) and this is _never_ appropiate to crash and burn when you get read issues.

Simple, crash&burn when anything goes “strange” is a good QA measure, but it’s absolutely worthless if things do not actually get fixed then. File bugs!

By: Robin

Robin — Fri, 27 Mar 2009 11:38:53 +0000

That’s definitely a bug, a program should never crash on “invalid user input”. Please file a bug report!

By: triton

triton — Fri, 27 Mar 2009 09:29:29 +0000

If it’s a crash it doesn’t matter what you did. The software is broken.

By: Dougal Stanton

Dougal Stanton — Fri, 27 Mar 2009 09:12:47 +0000

I hope that’s a rhetorical question!

A simple fault that causes a crash which then can’t be recovered. That’s seriously bad.

By: Stephane

Stephane — Fri, 27 Mar 2009 08:16:27 +0000

– Worth filing a bug ? : yeah

– Pay a visit to #f-spot, we’ll help you on fixing your collection.

By: Darwin Survivor

Darwin Survivor — Fri, 27 Mar 2009 05:02:43 +0000

Have you tried running F-Spot as a separate user?
“sudo -u f-spot” should do it.

If that works, it is most likely some settings inside your home folder. Delete the folder “~/.gnome2/f-spot” and it should remove any bad settings f-spot has saved.