Skip to main content
Participant
December 3, 2016

P: Instead of deleting currently selected photo, deletes face tag from previous viewed photo

  • December 3, 2016
  • 2 replies
  • 202 views

The Delete key will sometimes delete a face region from a previously viewed photo, that is not currently selected

While working through recently added photos, if you tag a face on a photo, then move on to the next photo, and try to delete that photo, Lightroom will instead appear to do nothing but actually delete the face tag that you added to the previously viewed photo.

Specifically, the steps to reproduce this are:

View a single photo in the Library (Loupe view)
Add a face region to the current photo
Go to the next photo which does not have any face regions (Ctrl+Right)
Attempt to delete that photo by pressing the Delete key

Nothing appears to happen - the Confirm message doesn't appear and the photo isn't deleted

However, if you go back to the previous photo with Ctrl+Left, you'll see that the face region that you just added has been deleted.  Lightroom shouldn't do that to a photo that is not visible or selected.

(I'm using Lightroom CC 2015.7 on Windows 10)

This topic has been closed for replies.

2 replies

Rikk Flohr_Photography
Community Manager
March 7, 2017
Adobe released Lightroom 6.9/CC2015.9 today.

This issue should be corrected in this release. Please give it a try and let us know if you see any further issues. 

Complete information about this update can be found at the Lightroom Journal: http://blogs.adobe.com/lightroomjournal/2017/03/lightroom-cc-2015-9-now-available.html

If you don’t see the update in your Creative Cloud App, you can use the kbsc [Cmd/Ctrl]+[Opt/Alt]+[ R ]  to refresh your app. If you are a perpetual license holder, you can access the update via Help>Updates...

Refer to this for any installation issues: http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015
Rikk Flohr: Adobe Photography Org
Adobe Employee
December 5, 2016
Thanks Randy. I could reproduce the bug. It should be fixed in a future Lr release.