P: Unable to advance to the next photo

@vitalyn38151610 This issue WAS present in 12.5 . If you go back through my posts (heaven knows how - I have trouble finding them myself!) you'll see I posted this issue while I was running 12.5. I'm now running 13.0.1 but it's still an issue.

Sorry @johnrellis, not to be argumentative but to confirm factual things... this is an exact copy/paste from the original issue. There is NO mention of marking photos for removal, simply switching between photos (and between library and develop modules). It should also be noted that this issue does NOT happen in library, only in develop mode.

"I've been working on a relatively recent installation of Lightroom (see system info below) and have encountered a problem which I believe began after the latest update. It's difficult to reconstruct the sequence of actions that leads to the problem, but after doing some photo editing and switching back and forth from the Library and the Develop module, an extraneous photo gets "stuck" in the display pane of the Develop Module. Also, mousing over the filmstrip there results in incorrect or incorrectly oriented photos being displayed in the Navigation pane.

The problem is resolved temporarily by restarting Lightroom. It reappears soon after a fair amount of editing. I'm not sure, but deleting photos (using the LR interface, not the file system of course) seems to precede the appearance of the problem. For what it's worth, there are no issues reported about the consistency or integrity of the catalog when backing up.

Is this a known issue with a recent release or might it be something related to my particular installation. Any help would be much appreciated!

Thanks,

Marc"

@johnrellis I agree with you, prior to version 13 there were no problems with the program. So we are all waiting for the elimination of this global problem in version 13.0.1 

@TomT60, "We are all experiencing an issue from 2018 that has not been fixed."

That previous thread was from Dec 2016, with about a dozen people reporting similar symptoms associated with marking photos as rejected and then deleting them while in Develop.  After Feb 2017, there were no more reports about that.  

Seven years later, with no additional reports on that thread, and now many, many more people in this thread are reporting symptoms of stuck images in Loupe, with no reports of the symptoms occurring after deleting and rejecting photos. All except one reported this started with LR 13.

So pretty weak evidence to conclude it has the same cause as the 2016 problem.

Regardless, it's a nasty bug that needs fixing.

@vitalyn38151610 Using the mouse or touchpad DOES still experience the same issue.

@kbarre I'm just concerned that Adobe being "aware of the issue" is unfortunately not very reassuring at all. If you check my previous posts you might be able to find the one where I refer to the issue being reported in 2018! Around here, it was again posted that "Adobe is aware of the issue and are working on a fix". My post recently pointed out that the "fix" has not come after 4 years, and is now persisting through more users than ever!

@Sarah3299064606bz @GoldingD I have the same issue with keyboard OR mouse. Admittedly I haven't reverted and don't plan to unless a) I get even MORE annoyed with the issue and can't put up with it any more (for now I'm soldiering through!) or b) I want to test this advice to see if it works. I have a feeling it wouldn't make a difference.

@mijbil250456 Agreed - I recently wiped my entire PC and started from scratch. The problem persists.

@johnrellis I am now experiencing the issue on the newer 13.0.1 version, therefore I am almost definitely not experiencing a different cause as these others. We are al experiencing an issue from 2018 that has not been fixed.

@Sameer K - The "Use Smart Previews instead of Original for image Editing" option is already off for me - as it is for at least one other person in the forum - and it makes no difference.

@Rafael _ Oz Using the 12.5 version is NOT a fix. When I originally reported this problem from 2018 is STILL happening, I was using 12.5

Wim, that's not a Pallette issue. It's a Lightroom bug. It happens with those of us using Loupedeck editing consoles also because this issue originates with Lightroom.  Those using Lightroom keyboard shortcuts are impacted by this as well.

To recap the almost 200 posts in this thread about the problem:  it's a consistent, reproducible bug affecting many of us, Adobe is taking its sweet time releasing a fix, and seems to believe that keeping silent about the bug and timeline for a potential fix is in its best interest.

Many of us are pretty fired up about the impact on our productivity and how poorly Adobe is handling this.

Hello everyone,

Since the LR 13.0.1 update, it has been almost impossible to finish a series of photos.
Every time I browse through my catalog with the arrows and change something, f
or example the white balance, and go to the next photo,
the previous one simply remains there while it continues to scroll at the bottom of the bar.
In the meantime I have also found the problem: I use a Palette Gear. 
As soon as I disconnect it and, for example, adjust the white balance with the sliders, it works perfectly.
This is only from the new update.

My colleague has the same problem.
I use Mac and he uses Windows, so it has nothing to do with that.

Anyone else with this problem? 
Thank you 
Wim

Olá.
Boa tarde!
Essa semana fiz a atualização em meu Lightroom Classic. Depois disso ele está travando quando eu passo a foto para frente, Ele não muda na visualização. Na tira de filme mostra que passou para a foto seguinte mais a viualização continua na foto anteriro.
Isso no modo revelação, onde faço os ajustes da foto.
O que devo fazer nesse caso?
Qual seria a solução?

@PatrickInSeattle, thanks for sharing your experience -- when faced with nasty bugs that only some experience, more information helps to narrow down causes and workarounds quicker. Your post didn't in the slightest imply that your experience would necessarily apply to others. (And no, I'm not an Adobe apologist.)