Skip to main content
Adobe Photoshop Family

587 Messages

 • 

11.2K Points

Mon, Aug 8, 2016 10:15 AM

Closed

Lightroom: Library/collections view issue

Hi,

[Using Windows]

Here is how to reproduce:

1. Library module | Grid View. Go to a collection and select an image.
2.
Right-click on it and "Go to Folder in Library". LR displays the contents of the folder.
3. Do what you have to do in that folder and return to the Collections panel.
4.
Since the selected image already belongs to the already selected collection, LR doesn't change anything to the display. It is still showing the contents of the folder. Now you can start making big mistakes since you think you are working in the collection but you are actually working with the folder.
5. To fix the problem, you have to select another collection and then return to the target collection.

Already reported multiple times since 2 or 3 years. They still don't care. I'm still upset because I'm continuously making mistakes because of this. Fixing this bug would take about a few minutes, I guess. This is probably not challenging enough to raise the interest of any developer at Adobe.

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

Responses

587 Messages

 • 

11.2K Points

4 years ago

It is worth noting that there's the same kind of issue when switching between collections and albums. Actually, when landing in the collection or publishing panel having an already selected collection or album (from a previous visit)  from a folder, album or collection that has selected images belonging to the target collection or album, the grid is not refreshed. The result is that we are then in a mixed mode where the displayed images do not correspond to the currently selected collection or album.

529 Messages

 • 

10.5K Points

4 years ago

Perhaps I'm not understanding or I'm on a different version, but I can't replicate what you're saying in Lr CC 2015.6.1 on Windows 10.  When I return to the collection in step 4, Lr changes the view back to contents of the collection, just as I'd expect.

2.6K Messages

 • 

33.7K Points

4 years ago

I can't replicate this, either, with LR CC 2015.6.1 on Windows 10. 

What do you mean by "return to the Collections panel"?  Do you mean you click on the same collection, again, and the thumbnails of the previously selected folder are still shown?

For me, when I re-click on the collection, the grid refreshes with image(s) that the collection holds. 

587 Messages

 • 

11.2K Points

4 years ago

OK. I have not been accurate enough and more details are needed.

Actually, the problem is that when I leave the collection panel by using the "Go to folder in Library" command, the current collection remains selected in the Collections panel. When I return from the Folders panel by clicking on Collections again (I'm using solo mode), the collection is already selected. Clicking on it has no effect because LR thinks it has already updated the display with the relevant images, which is not the case. That's why I still see the images from the folder.

Sometimes, after a while, I don't know exactly why and when, this behavior stops and the currently selected collection is deselected when leaving the Collections panel. In that case, when returning from the Folders panel, there's no problem because I have to click on the collection name to select it. So, the images are updated.

I don't know how to systematically reproduce the wrong behavior. However, this problem has already been reported many times.

529 Messages

 • 

10.5K Points

4 years ago

Same deal, I'm afraid.  Still can't replicate it.  Once I click on "Go to Folder in Library", focus moves to the Folders panel and the collection I was in becomes deselected.

This is stuff I do pretty regularly and don't remember ever experiencing the behavior you're describing, so I'd have to guess that it's a fairly odd bug that somebody's going to have to figure out how to replicate before there's any hope of squashing it.

Which version of Lr are you running?

587 Messages

 • 

11.2K Points

Always the latest.

470 Messages

 • 

12.2K Points

Yes,  I've had same problem for several versions.  it's annoying but had to get used to the "click on some other collection, then click on desired collection" workaround to get the grid to show the desired collection.  

587 Messages

 • 

11.2K Points

4 years ago

Here is a screen capture showing the problem (after disabling Solo Mode)...

I was initially displaying the "D'Allemagne_couleur" album. I right-clicked the selected image and "Went to Folder in Library". This opened my "Dortmund" folder where that image is stored. Note that the "D'Allemagne_couleur" album is still selected. So both items are simultaneously selected in LR which is inconsistent. You can't visualize a folder and a collection at the same time.

Now, if I want to return to the "D'Allemagne_couleur" album by clicking on it, nothing happens. LR keeps displaying the folder images. I have to click on another album and then click again on the "D'Allemagne_couleur" album in order to make LR refresh the display.

The very same problem occurs with Collections.

7.9K Messages

 • 

114.4K Points

I also cannot duplicate this. Regardless of whether I am in Solo mode or not, when the Folder where the image is becomes active, the collection becomes in inactive and deselects. 

You might consider resetting your preference file. http://www.lightroomforums.net/threads/resetting-or-trashing-the-lightroom-preferences-file.14226/ 

Adobe Photography Products
Quality Engineer: Customer Advocacy

2.6K Messages

 • 

33.7K Points

What kind of collection:  Smart, Adobe-created, quick-collection, user-drag-and-drop created?

If you create a new catalog, import 2 images, add one to a collection, manually, then do your sequence, does the issue happen or not?

2.6K Messages

 • 

33.7K Points

And what precise version of LR and Windows are you running?  Not "the latest" what version number of LR from Help / System Info, and what version of Windows, where Windows 10 1607 is the latest as of the last few days.

587 Messages

 • 

11.2K Points

The problem occurs with any kind of collection or album. I'm running LR CC 2015.6.1 and Windows 10.0.10586. As already mentioned twice above, the problem occurs with  all versions of LR and Windows I have run since at least 3 years. It is not version dependent. Preferences have been reset multiple times during this period. I'm sure Adobe can find multiple reports about this issue that has already been reported multiple times here and on the Adobe forum.
If you create a new catalog, import 2 images, add one to a collection, manually, then do your sequence, does the issue happen or not?
Since the problem may not appear immediately, it's hard to answer this question. For the moment, the answer is no.

At least, the fact that LR can have have a collection and a folder simultaneously selected is now proven and also confirmed by someone else. The developer should be able to determine why and when this is possible.

2.6K Messages

 • 

33.7K Points

"Since the problem may not occur immediately" means it could be some sort of corruption or particular condition of your catalog. 

Try importing your entirely current catalog into a new catalog and see if it occurs. 

7.9K Messages

 • 

114.4K Points

4 years ago

Patrick, 

I can understand you are upset with the behavior of your system however we need much more to go on in order to investigate and potentially fix. 

The first thing we need is complete system information - I see from subsequent posts that you are Win 10 and LR CC2015.6.1. What else can you tell us about your system, particularly any mouse/tablet/ devices and their driver versions? 

The second thing we need is a set of repeatable steps that can reproduce the behavior.  I have tested your steps on Win10 with Collections, Synced Collections, Smart Collections in Solo Mode and in Standard Panel mode. I have tested the same on Mac El Capitan OS. I have not been able to reproduce on either OS.  I have also tested in Lightroom 5.7.1 and do not see this behavior there either. 

Either there is a hardware/system specific issue at work here or there is some subtle step that is missing from the instructions that allows us to see the same behavior as you. Until we can discover which is the case it will be difficult for the engineers to isolate the cause and effect a repair. 

Which method are you using to reset your preferences file? The procedure changed in LR 6.x/CC2015.x. Close Lightroom. Hold down [Alt]+[Shift] and relaunch Lightroom. Overwrite the preferences when prompted. 

Adobe Photography Products
Quality Engineer: Customer Advocacy

587 Messages

 • 

11.2K Points

Rikk,
What else can you tell us about your system, particularly any mouse/tablet/ devices and their driver versions?
There's nothing particular with my system and, as explained above, I have observed this problem on various systems, various versions of LR and various versions of Windows since years. So there's no reason to spend time on this.

My system info is here :  https://dl.dropboxusercontent.com/u/55479279/systeminfo.txt
there is some subtle step that is missing from the instructions that allows us to see the same behavior as you. Until we can discover which is the case it will be difficult for the engineers to isolate the cause and effect a repair.
This kind of problem often occurs because of uninitialized variables or dangling pointers in the code. In such cases, it's almost impossible for the user to precisely determine under which circumstances the problem shows up because it's just random.

One thing is for sure : that bug is proven (see screen capture) and should be reported to the developers anyway. At a given moment, 2 items in the left pane of the Library module can be selected simultaneously. I guess this is caused by a problem in the UI management. As I already explained above, once the developers know that such a situation is possible, even if the cause is not identified, fixing the problem is rather easy. I repeat :  when selecting an item in the Library left panel, the code should make sure that all other items in the various lists are deselected without making any assumption about the current state of the UI. This can be handled by a very simple routine.

Finding this kind of bugs is part of the developer's job. After all, I have not written this code, they did, and Adobe sold it to me. This shouldn't be forgotten.  Why always transfer the problems to the users ? I have written a lot of software in my life, and I fixed many bugs for which the user was totally unable to precisely describe how to make it appear.  I never answered to a customer that a bug wouldn't be fixed because it was too hard to spot. My mistake, my problem, my job to fix it.

I understand that you may have instructions to not forward bug reports to the developers if you don't have a procedure allowing to reproduce the problem immediately but I think that it's not the correct attitude. That's the easy way to reduce the workload in the maintenance dpt. but that's not fair. Adobe sold me a software, they are responsible for its quality and the workload to guarantee it is not on my side.

My statements might seem aggressive but the problem is the accumulation of such situations. If I had to provide accurate instructions to reproduce all these allegedly "minor"  bugs that are annoying me in Lightroom since version 1, I wouldn't have any time left to handle my photos. Adobe obviously have a problem with coding quality. Any experienced developer can see that, even without any access to the source code, just by looking at the program behavior and at the incredible mess it creates on the system (especially in the Windows registry) . I can give you examples if you want.

Now, I'm no longer coding or debugging software. I want to spend time on my photos. I have demonstrated the presence of an annoying bug that might generate big mistakes when handling images. That's already a good work for a customer. I have already explained above what I think Adobe should do about that.

Champion

 • 

5K Messages

 • 

91.6K Points

4 years ago

This bug was first reported for LR 5.7.1, and at least 5 people (including me) have reported it.  I'll merge this topic into the existing bug report.