After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 338570 - Delete raw image from drive only deletes .raw not .thm
Delete raw image from drive only deletes .raw not .thm
Status: RESOLVED WONTFIX
Product: f-spot
Classification: Other
Component: General
0.1.11
Other All
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-04-15 09:59 UTC by ghasd
Modified: 2018-07-01 09:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description ghasd 2006-04-15 09:59:33 UTC
Please describe the problem:
Two issues when you use the deletion of photos from drive:

1. Issue (more important than second issue)
For raw files you have a crw file and a thm file. If I delete the crw file I
don't need the thm file anymore. f-spot only deletes the crw file, can you
please delete the thm file as well? (I don't import the pictures into the photo
folder)

2. If the photos exist inside the Photo folder only in that location they get
deleted. Would be good to have a option to delete it in the original place as well.

Steps to reproduce:
see above


Actual results:


Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Pavel Šefránek 2006-05-08 20:58:50 UTC
I say a good word for adding an option (checkbox) to delete original images (from folder or camera) in import window. It's unnecessary to store images in two different locations. gThumb supports this.
Comment 2 Bengt Thuree 2006-06-01 02:46:09 UTC
I would like to see only one problem/suggestion per bug. Makes it much easier to track that way.

Changing title to reflect item 1) which is the main issue in this bug.

As for item 2)
F-Spot do not keep track of where the original is, when you copy the photo to the ~/Photos location. So, when you delete from Drive, F-Spot will only delete the photo it knows about. Either the copied version in ~/Photos, or the linked version in whatever location it resides in.
Most common way to import photos, is directly from Camera or from USB stick. In either case, the photo will in practise only reside in one place, since the other is a removable storage unit.

I am not clear of what you want? Perhaps you could explain a bit more in a new bug?

As for comment #1. I created a new enhancement request for that one (bug #343553)
Comment 3 Bengt Thuree 2006-06-01 08:33:22 UTC
Related to bug #325366 as well as to bug #342892
Comment 4 André Klapper 2018-07-01 09:04:48 UTC
f-spot is not under active development anymore, has not seen code changes for five years, and saw its last tarball release in the year 2010.
Its codebase has been archived: https://gitlab.gnome.org/Archive/f-spot/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.