Download Folder fails to follow symbolic links, is sometimes ineffective
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rapid Photo Downloader |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm running RPD 0.4.10 on Ubuntu 14.04 64-bit --
though I've had this problem over the past year or so
when running earlier versions of Ubuntu.
I walk up to my computer, plug in a SD/USB card,
and depending on if RPD shows NEF or JPG files,
I want to download them to different places.
(btw, wouldn't it be nice if RPD would remember different destinations
for .JPG and .NEF files?, like it does for Pictures/Videos?)
On the main display under the "To", there is a menu for "Photos:"
One of the selections is /NEF, which is a symbolic link
to a big fat disk where I write the NEF files.
But ASP is unable to follow that link, and it complains:
Invalid cross-device link
File: /media/lenb/NIKON D600/DCIM/
A 2nd problem, possibly not related...
File/Preference
also has a "Download folder:" with the same selection of locations
as above.
When I change that destination, it is effective, but it is NOT
reflected on the main page in the "Photos" destination -- which
leads to puzzling results of photos on the main page being
downloaded, but not put in the location shown on the main page.
Many times I've downloaded my NEF into JPG, or JPG into NEF
because of this, and had to manually move the files to
their intended destination.
Changed in rapid: | |
status: | New → Incomplete |
an additional observation...
After a file fails to download, it is marked with a little red icon instead of a little green icon.
It does not seem to be possible to somehow un-select/re-select that photo
for download to a new destination. I have to re-start the tool in order to
try to access that photo.
This applies also to photos what have been successfully downloaded too.
it seems to be impossible to somehow change their state from "downloaded"
to be eligible for downloading again without re-starting the tool.
This use-case comes up, say, when I start downloading a batch to the wrong place,
and i stop it and want to download to the right place (eg. due to 2nd issue
with ineffective change to download location mentioned above)
I suppose somebody might also want to download more than once
to an archive location, and they'd run into that challenge too.