Skip to main content
Adobe Photoshop Family

11 Messages

 • 

184 Points

Fri, Aug 5, 2011 10:58 PM

Closed

Acknowledged

Lightroom: Multiple image move operation bug

1. change to Library mode -> Grid view (press 'g')
2. select > 10 images
3. drag and drop images into any folder - notice the image that is highlighted!
4. error dialog "Error While Moving Files" is displayed that the highlighted image was unable to be moved - see screenshot #2
5. manually drag and drop last file into folder :(

This is not 100% reproducible but on my current system (i7, SSD, 12gb RAM) when sorting panoramas into sub-directories, I get this error about 75% of the time. Also on my old system (AMD Phenom x4 w/ 6gb RAM) I would get this error even more frequently.

Win7 x64. Lightroom v3.4.1 (however this bug has been around since at least v2).



This conversation has been merged. Please refer the main conversation:

Responses

Official Solution

Adobe Administrator

 • 

15.5K Messages

 • 

291.9K Points

6 years ago

This should be fixed in Lightroom CC/Lightroom 6.

Sr. Product Manager, Adobe Digital Imaging

946 Messages

 • 

13.8K Points

9 years ago

Yep...I've seen this before. Can't seem to nail it down.

Employee

 • 

475 Messages

 • 

10.7K Points

9 years ago

Hi Glenn,

I'm not able to reproduce this problem. Are you moving photos between folders on the same drive, or between different drives? And just so I'm clear, one of the files fails to move, but then when you dismiss the error message and try moving the photo again, it works?

Thanks,
Ben

946 Messages

 • 

13.8K Points

Ben, I've had this happen at least 50 times during the 3.x cycle, moving images from folder-to-folder. And, yes, the image left behind moves on the second try every time. It seems to me that it requires a lot of images (perhaps 50 to 100 at least).

Employee

 • 

475 Messages

 • 

10.7K Points

Not sayin' it doesn't happen. Just sayin' it doesn't happen for me. :-) So I'm trying to get some more info. Are your moves between drives, or on the same drive? Network drive or local drive? Any particular file type or size? Do you have the "Automatically write changes into XMP" preference turned on? Anything distinguishing you can recall about the times it succeeds vs. the times it fails?

It happens for me not at all. It's happened for you 50 times in the last year-plus, and requires moves of at least 50-100 photos. It happens to Glenn 75% of the time, with moves of only 10 photos. Clearly there's some variability here, so any additional info you can think of that might be relevant would help.

Thanks,
Ben

946 Messages

 • 

13.8K Points

Same drive, local drives, all file types, no auto-write, XP and Win 7 64-bit, move by drag or by context menu.

11 Messages

 • 

184 Points

@Ben:
Always moving between the same drive. I tend to shoot several hundred panoramas, with a black frame in-between for fast sorting. Afterwards I manually create folders (because LR ignores importing empty ones) e.g. pan01, pan02, and so on. Then I proceed to move the 8-20 images between black frames into the subsequent folders.

After I dismiss the error dialog, it works fine. That's what makes this so weird, it can't move the _highlighted_ image (of the batch) right this moment (locked by LR?) but immediately after I click the the away I can move it without a hitch. It seems to happen more often when i highlight the first image in the batch and then do the move.

btw i've tried this on an OCZ SSD, USB 3.0 (~80-100 MB/s), USB 2.0 (~20 MB/s) internal SATA II drives in single and RAID 0/1/0+1/1+0/5 (60-180 MB/s) configurations.

@Lee: only 50? I just had it happen around 50 times out of 75 attempts :( it's something i deal with on a weekly, if not daily basis.

Champion

 • 

2.6K Messages

 • 

33.7K Points

I think the file is still being accessed by some other LR thread that can't easily be told to stop mid-access, like computing a preview or comparing metadata or whatever, and if you let it sit a little longer, it'll work more often, and the faster the computer/hard-drive the sooner it's finished, too.

LR has to move the file, any XMP sidecar and possibly the preview so there may be more files and time involved that what would seem obvious. It would be nice if LR would retry the move of any failed files, again, at the end.

11 Messages

 • 

184 Points

I've thought the same, except speed of my drives hasn't seemed to matter at all. Also I don't shoot previews anymore, which has definitely helped speed things up a bit in general.

+1 to this: "It would be nice if LR would retry the move of any failed files, again, at the end".

Champion

 • 

2.6K Messages

 • 

33.7K Points

Someone else has complained that their image's file-modifacation date gets updated to the current time whenever they click onto an image and have auto-XMP-writing turned on, and this cause Time-Machine to make a new backup copy even though nothing substantive was changed.

I wouldn't be surprised if LR opens the current file in read-write mode in case it needs to update the metadata (perhaps in the XMP file not the main RAW so the file i/o is not a factor) and then goes and checks the database version of the metadata before deciding not to do anything, but for the duration of the checking, the file can't be moved, anywhere. I have this problem when I move whole folder trees at the end of every month, and purposely put LR in Loup view and hide the thumbnail bar or make the thumbnails large so there are fewer, so a minimal number of files are being looked at and I just wait until the Loading... has stopped on the preview and there are no little dots on any thumbnails before trying to move the folders, but I'm dragging folders at the left, not individual images so I don't have to have grid-view or a row of thumbnails selected.

11 Messages

 • 

184 Points

I share your speculation and experiences!

Moving folders is a whole other bowl of fruit for me that I won't get into. But similarly, to help alleviate slow moving of images (30+), I usually click on some other folder as fast as possible and watch the Moving Images status bar change from 10sec ETA to being complete. If grid view has to shuffle thumbnails as images are moved to/from the folder you're viewing, you might as well go take a coffee break.

Oddly enough, I can't say I've seen this behavior on OS X boxes.

Employee

 • 

475 Messages

 • 

10.7K Points

9 years ago

Hooray, hooray. I have been able to reproduce this problem, and have entered the issue in our bug database. I should note that I have only been able to reproduce the problem on Windows, not on Mac. If anyone is experiencing this problem on Mac, please let me know.

Thanks,
Ben

19 Messages

 • 

320 Points

Thanks for this, but the problem still exists in LR4. See my suggestions below.

25 Messages

 • 

426 Points

And in LR 5... Surprisingly, after 2 years :)

Champion

 • 

2.6K Messages

 • 

33.7K Points

9 years ago

Have you tried things with LR 3.5 RC that was released a couple days ago:
http://labs.adobe.com/

Adobe Administrator

 • 

15.5K Messages

 • 

291.9K Points

I think you may have meant to say "3.6"

Sr. Product Manager, Adobe Digital Imaging

Employee

 • 

475 Messages

 • 

10.7K Points

I don't expect it to be fixed in 3.6. The bug is still at Open/To Fix in our bug database.

-Ben

Champion

 • 

2.6K Messages

 • 

33.7K Points

I had 3.6 until I re-ordered my sentence and now I can't edit the post. Thanks for correcting things.

1 Message

 • 

70 Points

I have only had LR for a week so am still settling in. Shall stick with 3.5 for the moment. Thanks for the update Ben

11 Messages

 • 

184 Points

3.6 doesn't help, nevermind that it also adds all sorts of annoying quirks. After a couple weeks of frustration I went back to 3.5.

19 Messages

 • 

320 Points

9 years ago

LR4 still has this problem - it is likely caused by the fact that Lightroom itself is "loading" one of the images that are about to be moved.

In other words, the "load file thread" is agnostic of what the "move file thread" is doing, this causes a locking issue somewhere inside the OS.

Even if you can't fix the bug properly, at least GIVE US THE OPTION TO RETRY THE MOVE. You already have the dialog, how hard can it be to add a "retry" button to it.

Thank you.

11 Messages

 • 

184 Points

Why can't the move thread just note the error, and retry automatically once or twice with a small (e.g. 250ms) delay between? Even less work and no need for an extra dialog.

19 Messages

 • 

320 Points

Also fine, but I don't think the problem is that we don't know how to fix it :-)

513 Messages

 • 

11.1K Points

9 years ago

Lambert, the issue with the temporary eraser brush keyboard control is affecting me a lot more often and should be infinitely easier to fix.

Has it been fixed yet, after a year of reporting?

No.

I guess you have to adjust your expectations.

BTW, I'm advising against using workarounds / patches (like using an internal repeat try or exposing the problem in the user interface). A bug needs a proper fix. Everything else just creates a big mess over time.

19 Messages

 • 

320 Points

9 years ago

What can we do to raise Adobe's awareness of our dissatisfaction?

If this doesn't change I would be tempted to use LinkedIn to send "please fix this bug" messages to the actual developers that are listed in the splash window / about box in Lightroom

Adobe Administrator

 • 

15.5K Messages

 • 

291.9K Points

Thanks. The engineer is aware of the issue and bug is still active. (there's a recent comment in the bug report) It just hasn't risen up to the top of the priority list. I added a comment to the bug report as well pointing to this thread.

Sr. Product Manager, Adobe Digital Imaging

19 Messages

 • 

320 Points

Please, the issue has been reported 9 months ago. It's very annoying and it's easy to fix.

This is typical "low hanging fruit", I would say.

25 Messages

 • 

426 Points

7 years ago

Problem still exists in LightRoom 5... Surprisingly, after 2 years of development :)

11 Messages

 • 

184 Points

7 years ago

Yes, also confirmed here with latest version. Why do I keep paying for upgrades when they don't fix features that affect me on a nearly daily basis?

248 Messages

 • 

4.1K Points

7 years ago

Misery loves company. I have been seeing this error as well on Win 7.

2 Messages

 • 

90 Points

7 years ago

Just posted this problem in the forums and got a reply and a link to this page. I can't believe that it has been known about for 2 years!! Why is this not fixed yet? Using Lightroom 4. Sort it out please Adobe.

1 Message

 • 

60 Points

7 years ago

I'm a new Lightroom user. Very disapointed in this bug as it appears to have been brought to Adobe's attention years ago and still no fix! I'm not impressed at all.

For what it's worth, I'm running Lightroom 5 on Win7 64bit.

25 Messages

 • 

426 Points

7 years ago

Today in 2nd of June 2014, 21st century, as you may have noticed.

I use Lightroom version 5.4

And I still see this bug.

There is nothing better in this world than stability :)

19 Messages

 • 

320 Points

6 years ago

Let's all join in celebrating the third anniversity of this fine bug.

https://twitter.com/lambertwm/status/...

And may I recommend that Jeffrey Tranberry (Chief Customer Advocate) be promoted to Senior Master Bug Conservation Officer (First Class).