In a spot with F-Spot

F-Spot is my tool of choice when uploading pictures to my albums. Yesterday, I managed, through my sheer idiocy, to mess things up.

Here’s what I did. I had a couple of ‘must upload’ pictures in a folder under another user’s $home on the laptop. So, I

  1. copied them across to my normal user
  2. changed the ownership appropriately
  3. imported the pictures via f-spot
  4. selected a few and uploaded them
  5. deleted the folder containing the pictures

A short while later, I figured that I had to upload a few more pictures from the same folder so, I

  1. copied them across to my normal user
  2. begun to import the pictures via f-spot
  3. saw f-spot crash on me

Anyone can see that during the second time, I forgot to change the ownership. So, figuring that was the issue, I followed the earlier steps, this time remembering to change ownership and, executed the application. It still crashed. So, I have a couple of questions:

  • is this worth filing a bug ? (Given that I did this through my own inexactness)
  • can I fix this so that the application will eventually start and, I can continue using it ? (I don’t want to clean the system of all traces of the application and re-install)

I am currently using f-spot- on Fedora 10

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/sankarshan/ on line 3031

8 thoughts on “In a spot with F-Spot”

  1. 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.

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

  3. 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!

  4. 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 🙂

  5. 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.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.