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 582632 - Import wizard defaults to home directory and doesn't create folder structure
Import wizard defaults to home directory and doesn't create folder structure
Status: RESOLVED DUPLICATE of bug 579340
Product: f-spot
Classification: Other
Component: Import
0.5.x
Other All
: Normal minor
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-14 15:54 UTC by c_keil
Modified: 2009-05-14 18:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description c_keil 2009-05-14 15:54:38 UTC
Please describe the problem:
Using the import dialog coming up after mounting a medium (e.g., inserting an SD card) and starting f-spot from the popup, the settings for the import folder are not used. The default target location is the user's home directory. In addition the imported photos are just copied to the target folder, not to a subfolder structure yyyy/mm/dd (date of the photo).
Starting f-spot in the first place and clicking Import, the photos are copied to the appropriate subfolder of the set import directory.

Steps to reproduce:
1. Mount a medium (e.g., insert an SD card with photos)
2. Start f-spot from the upcoming dialog ("Open F-Spot Photo Manager")
3. Import photos via the upcoming import dialog


Actual results:
The imported photos are copied directly to the target directory.

Expected results:
The default target directory should probably be the set import directory.
The imported photos should be copied to a yyyy/mm/dd/ subdirectory structure of the set target directory.

Does this happen every time?
Yes.

Other information:
This is filed as Ubuntu bug #367830
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/367830
Comment 1 Maxxer 2009-05-14 18:43:54 UTC

*** This bug has been marked as a duplicate of 579340 ***