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 575871 - F-spot acts differently if import is done at camera plugin compared to import from program later
F-spot acts differently if import is done at camera plugin compared to import...
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: Import
0.5.x
Other All
: Normal normal
: 0.7.1
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-18 19:27 UTC by g11024342@trbvm.com
Modified: 2010-07-13 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description g11024342@trbvm.com 2009-03-18 19:27:32 UTC 
Please describe the problem:
I have found that F-spot acts differently if you import pictures from the dialog when you plug in your camera compared to if you start F-spot manually, then choose Photo > Import.

Steps to reproduce:
Import some pictures by plugging in your camera and follow the "wizard". This is case #1.

Import some other pictures by doing Photo > Import while already in F-spot. This is case #2.

Actual results:

In case #1 you get filenames with lower case (dsc010101.jpg) + permissions set to 644.

In case #2 you get filenames which are untouched (DSC010101.JPG) + permissions set to 700.

Expected results:
Filenames should be untouched and permissions should be (IMHO) 644. This ought to be configurable from preferences.

Does this happen every time?
Yes

Other information:
This is related to Gnome bug #544193.

This is also in Ubuntu, https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/344992

The related bug is also in Ubuntu, https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/249230
Comment 1 Ruben Vermeersch 2010-07-13 15:00:24 UTC 
This is fixed with the new import.