Bug Reports

Lightroom Classic version : 11.4.1 Lightroom Mobile version: 7.4.1 MacOS Version: 12.4   When I try to sync a photo from LR Classic to LR CC, in grid view the thumbnail is displayed as an icon of a cloud w/ an exclamation point, on iPhone, iPad and Web views. Additionally, when I hover over a thumbnail on Web, it displays a message of "Open Lightroom on [computer name] to continue syncing." despite both Lightroom Classic and Lightroom CC being open on the computer.   The thumbnail is displayed correctly in the desktop app. If I make an edit to a photo, the thumbnail then shows up correctly on all platforms.   If I roll back to 11.4 and sync photos, their thumbnails are displayed correctly.   Steps to reproduce: 1. Click the sync icon next to an album in LR Classic, or add a photo from the catalog to an album that has Sync enabled. 2. Wait for the Cloud icon in the upper right corner to display a green checkmark. 3. Open Lightroom on iPhone, iPad, or Web. 4. Look at

Hello... I am finding that the Amount Slider defaults to "100" and grays out when I set the amount to 115 when I use PG02 in the "Portraits Group" presets. It seems to happen at only that preset, and only that amount.   LrC v. 11.4 Windows 10

Issue: Converting to DNG removes star rating   Lightroom Classic 11.4 MacOS 12.4   Steps to reproduce: Rate files with 1 star Convert Sony A1 raw files to DNG with the following settings: Only Convert Raw files Delete originals after successful conversion File extension DNG JPEG preview medium Embed Fast Load Data Use Lossy Compression   Expected result: new DNG files should maintain the star rating as they have done in previous versions of LR Acutal result: as soon as the Raw file is converted to a DNG, the star rating disappears

Issue: Lightroom Classic 11.4 does not render local adjustments for older files unless they are first opened in Develop   Lightroom Classic Version Number: 11.4 OS Version Number: macOS 11.4 (Intel) Steps to reproduce: find an older file that has local adjustments, export from Library view file is rendered without local adjustments (Masks) open file in Develop module, without doing anything, export again file is now rendered correctly, WITH local adjustments (Masks)   Expected result: file will be rendered with masks, in step 1Actual result: file is rendered without masks, at all, in step 2   Video: https://www.dropbox.com/s/7wukaii7gbp4ml0/lrc11-4-export-bug-demo.mp4?dl=0

Using LR Classic CC.I just transitioned from a 6 year old Lenovo W510 laptop to a Dell XPS 15 Touch. I immediately noticed that Collections and Publish Services were missing in LR on the Dell. Just gone. There is a huge black space instead. I reached out to adobe.forum for help and tinkered while waiting. Meanwhile, I stumbled across an interesting behavior: If I closed Folders, Collections and Publish Services appeared! Yay! But when I re-opened Folders, Collections and Publish Services vanished again. I use all of these extensively, so this is a huge annoyance and inconvenience.I was advised to removed/re-install LR, but there was no change in behavior. It turns out that LR has some inexplicable/undocumented limit as to how many folders it can show (!). How I know: I have 627 folders and about 15 or more were expanded. That is, each was showing their numerous sub-folders. I closed all the sub-folders so that only the 627 main folders were listed under Folders and Collection

When a plugin attempts to set a photo's PerspectiveVertical to a non-zero value and PerspectiveHorizontal to 0, LR throws   "An internal error has occurred. ?:0: attempt to index a nil value"   If both of those settings are non-zero, or if ConstrainToCrop is 1, no error is raised.   To reproduce, run this script:   local LrApplication = import "LrApplication" local LrTasks = import "LrTasks" local catalog = LrApplication.activeCatalog () local photo = catalog:getTargetPhoto () local settings = { CropConstrainToWarp = 0, PerspectiveAspect = 0, PerspectiveHorizontal = 33, PerspectiveRotate = 0, PerspectiveScale = 100, PerspectiveVertical = 0, PerspectiveX = 0, PerspectiveY = 0} LrTasks.startAsyncTask (function () catalog:withWriteAccessDo ("Update", function () photo:applyDevelopSettings (settings) end) end)     Tested on LR 11.0.1 / Mac OS 11.6.

The SDK methods photo:rotateLeft() and :rotateRight() have a disastrous bug -- they can rotate all the photos in the catalog. To reproduce:   1. Save the script below into "rotate-bug.lua" in the Scripts folder.   2. Open a test catalog with at least 10 JPEGs.   3. Rename one of the photos to be "xyz321.jpg".   4. Run the script "rotate-bug.lua".   5. Observe that just that one photo gets rotated.   6. Set the filter "Filename Doesn't Contain xyz321.jpg" and observe that file is no longer visible in Grid view.   7. Run the script "rotate-bug.lua".   8. Observe that all the photos in Grid view get rotated!   Underlying this bug is another (old) bug: photo:rotateLeft() and photo:rotateRight() rotate all the photos in the current selection, rather than "photo" (and only "photo"). To work around this old bug, a plugin must use catalog:setSelectedPhotos() to select the photo it wants to rotate. But as this bug report demonstrates, if that ph

Images that are exported from LRC 11.2 and then uploaded to Adobe Stock lose the exported synonym keywords. This also occurs using the LRC Adobe Stock Publish App. Issue:  Lightroom Classic Version Number: 11.2 OS Version Number: Windows 11 64 bit Steps to reproduce: Include synonyms with your keyword tag. Check that the synonyms are to be exported. Assign the keyword to the image. Export the image. Verify that the synonyms were also exported .  Upload to Adobe Stock. Expected result: All of the keywords and synonyms should be recognized and uploaded.Actual result: Only the keyword without synonyms is recogniozed.

Hi,For some years I have been keywording my images in Lightroom, using keyword hierarchies to manage them. Recently, when I try to upload to Adobe Stock, it only takes the bottom level keywords, and none of the hierarchy keywords they are in. This happens if I use the Stock plugin, or export and upload directly or via FTP.  This problem doesn't occur for other agencies, and the keywords are correctly embedded in the JPG file details, so I'm at a loss as to why adobe Stock doesn't see them - any suggestions as to what i am doing wrong ??ThnaksRoger

I have never had this issue in previous versions of Lightroom (or Photoshop, if it's a Photoshop problem), but whenever I open an image (jpg, psd, tiff) from Lightroom into Photoshop and do some editing there, when I get back to Lightroom the [+/-] icon appear on the image ("Photo has development adjustments") and on the Quick develop panel, next to "Saved preset", appears "Custom".   As I said, I have never seen this behaviour before.   Thank you for your consideration.   -------------------------------------------------------------- Thread moved to Lightroom Classic 'Bugs' forum

When you do Preferences > Presets and check Override Global Setting [sic] For Specific Cameras in a catalog that contains no raws, the message "Please wait while loading camera models" incorrectly appears and never goes away. This fools some users into thinking that LR is just slow and that camera models will (or should) eventually appear: https://community.adobe.com/t5/lightroom-classic-discussions/please-wait-while-loading-camera-models-new-lightroom-installation/td-p/12889593   When there are no raws in the catalog, this message should be displayed: "The catalog contains no raw photos, so the list of cameras is empty."     Tested in LR 11.3.

The Metadata panel's Caption field doesn't correctly display the results of appending text to the captions of multiple selected photos. It works correctly in LR 11.2 and earlier but not in LR 11.3.1, and it appears to be another symptom of the change in LR 11.3 to cache metadata in <catalog> Helper.lrdarta.   Tested on LR 11.2 and 11.3.1, Mac OS 12.3.1.  Steps to reproduce (also see the screen recordings):   1. Make a new catalog and uncheck Catalog Settings > Metadata > Automatically Write Changes Into XMP.   2. Import three photos with no caption in their metadata.   3. Set the captions of the photos to "A", "B", and "C" respectively.   4. Select all three photos.   5. In the Metadata panel, with Selected Photos highlighted, observe that Caption displays "< mixed >".   6. Set the input cursor after the ">" and type "X" and then return. Observe that Caption now displays "< mixed >X".   7. Select just the first pho

Cropped size in pixels is now missing in Library, the full original size is just repeated

  Content moved to correct post    

Hello, Been able to repro the following: 1. Enter the Develop module 2. Add a positive or negative Temperature correction (e.g. +5) 3. Add Masking (Shift+W) then "Select Sky" Result: A +1 Tint correction is added to the picture. This is not recorded in the History panel. Can anyone repro this too?

I just was importing ~480 photos and I noticed that 6 or so of these photos were grayed out because they were "suspected duplicates".   They are definitely not duplicates. I made these photos today. I checked that the catalogue does not have any old photos incorrectly stamped with today's date.   I would assume that suspected duplicates at least involve comparing hashes of photos. For 6 out of 480 false poistives it should be a very weak hash even taking in account that I have ~300K photos in my catalog. So really sounds like a bug for me. Also I don't remember seeing anything like this in ~10 years that I use Lightroom. 

The first menu item in the context menu for photos in Survey view is Remove From Selection.  In English, it correctly shows / as the keyboard shortcut. But in German, Spanish, French, Italian, Portuguese, and Swedish the shortcut is different, even though the menu shows it as /. For example:     de.lproj/TranslatedStrings_Lr_de_DE.txt:"$$$/AgLibrary/Menu/File/Edit/DeselectActive/Key=Shift+d"es.lproj/TranslatedStrings_Lr_es_ES.txt:"$$$/AgLibrary/Menu/File/Edit/DeselectActive/Key=Shift+d"fr.lproj/TranslatedStrings_Lr_fr_FR.txt:"$$$/AgLibrary/Menu/File/Edit/DeselectActive/Key=("it.lproj/TranslatedStrings_Lr_it_IT.txt:"$$$/AgLibrary/Menu/File/Edit/DeselectActive/Key=Shift+d"pt.lproj/TranslatedStrings_Lr_pt_BR.txt:"$$$/AgLibrary/Menu/File/Edit/DeselectActive/Key=Shift+d"sv.lproj/TranslatedStrings_Lr_sv_SE.txt:"$$$/AgLibrary/Menu/File/Edit/DeselectActive/Key=Shift+d"

Captions (or any field in the Metadata panel, including GPS) containing double quotes disappear from the Metadata panel. Setting the option Catalog Settings > Metadata > Automatically Write Changes Into XMP works around this bug.  The programmer probably forget to properly escape double quotes when constructing a SQL update query. To reproduce: 1. Create a new catalog. 2. Disable the option Catalog Settings > Metadata > Automatically Write Changes Into XMP. 3. Import a single photo. 4. In the Metadata panel, enter this into the Caption field:  a"b   5. Do Edit > Select None. 6. Select the photo and observe that the Caption field is incorrectly blank. 8. Use the Show Catalog Metadata plugin's Show command to see all the photo's metadata as recorded in the catalog. Observe the line:  caption = "a\"b",   indicating that the caption actually got recorded in the catalog. 9. Do Metad

Metadata Auto Sync doesn't correctly update the display of  copied metadata fields like Caption in the Metadata panel, another problem with the 11.3's caching of metadata in "<catalog> Helper.lrdata". You can work around this bug by enabling Catalog Settings > Metadata > Automatically Write Changes Into XMP.   Note that this is a different bug than the one reported for Sync Settings not displaying correct Cropped dimensions.  Sync does correctly display the copied caption -- it's just Auto Sync that is broken.   Tested on LR 11.3.1, Mac OS 11.6.2 and Windows 10. To reproduce:   1. Make a new catalog.   2. Import two photos.   3. Turn off Catalog Settings > Metadata > Automatically Write Changes Into XMP.   4. Select both photos.   5. In the Metadata panel, select Target Photo.   6. Enable the menu item Metadata > Enable Auto Sync.   7. Change Caption to "Hello".   8. Select the other photo and observe

After latest Lightroom Classic CC I almost can't work in Lightroom during export as it's using around 90% off mu CPU. Maybe exporting itself is a bit faster but when exporting 2000 pics I'm unable to work for about half an hour as there are huge lags. In the end I would rather prefer slower export working in a background and still have ability to work with pics without such noticable slow down. It was much better balanced before updating to Classic CC.My CPU: Intel Core i7-6700K (4 cores, od 4.00 GHz do 4.20 GHz, 8 MB cache)

I've seen there is a post regarding similar issues with the S21 with several replies and comments, including someone who mentions that NR is also not working on S20FE, this is happening to me also with LR Classic and LR Mobile. I can't seem to reply to that post so I'm starting one here. Here are all the app versions where it's not working:   LR Classic 11.3.1 on Windows 11 Photoshop LR 5.3 on Windows 11 LR Android 7.3.1 on Lenovo P11 Tab Pro   All noise reduction settings have no effect. Very frustrating because obvioulsy this mobile has been around since Oct 2020, surely this must have been noticed and reported before!? Here are a couple of images with NR settings whacked up to 100 with no effect on the image:   LR CLASSIC   LR MOBILE   Thanks.

Hi,Under many circumstances, whenever your copy of LR crashes, freezes, doesn't start,... the most frequent answer you'll get from the support is "Reset your preferences". And in many cases, that works. But 1) you have to re-configure LR again and 2) this will not fix the bug generating the problem so, it will happen again . Should we be happy with this ? No.If resetting the Preferences file(s) solves a problem, that's only because - The piece of LR code reading or writing from or to this file is buggyOR-  A particular combination of parameters generates a problem.Do not accept the idea that the Preferences file was corrupted. If it's corrupted, it's by LR itself. Spontaneous file corruption does not occur that often.Since the developers at Adobe don't seem ready to investigate this case more deeply, I guess it's time to help ourselves and to collect information that could help them debug this issue. There's a few things that are easy to do :1. Make a backup copy of your Preferenc

I have an image I want to print on 4x6 paper, actually, issue is present with any image. In the print module, with 'Zoom to Fill' checked, I select and drag/move the image to the composition I'd like... let's say the top part of the image, so that the bottom is cropped/not printed. When it prints, it prints including the bottom part of the image not in the visible cell on screen, cropping/not printing the top of the image that is visible in the cell on screen. In other words, the opposite of what I wanted.   Here's the odd part: if I drag the image in the opposite direction such that the bottom part is in the cell (so the top is cropped), it prints the image with the 'out of cell' top instead (it crops the bottom). In other words, the image that is actually sent to print is 'reverse' from what I want composed in the print cell.   This occurs on any of my printers (multiple brands), and also occurs if I print to Printer (send to printer or save as PDF) or JPG file.  

Ever since upgrading to the latest version I've had Metadata conflicts - little exclamation mark in Grid view. I even deleted my catalog of more than 200k images and started again to no avail.  I also synched all of my folders and no difference.   When I click on the exclamation mark I get the message that says that metadata has been changed by another program and Lightroom, even when I have only used Lightroom. When I click to upate the metadata the exclamtion dissapears but comes back very quickly. I made a Quick Collection of all metadata conflict shots - over 6000 - and syched them. The number dropped by a third but then came back to the original total within minutes.   I have lost all of the displayed colored flags in Grid View but can still select various colors in the Metadata panel at the top and get the appropriate shots. When clicking on an individial cell in Grid View I get a thin colored line around the shot which then dissapears when I click on another shot.

After updating LR today from the Cloud app on my PC it now fails with an error every time I open it. I have tried updating graphic card drivers, uninstalled and reinstalled LR itself but the problem persists. Was working fine yesterday. It is now unusable as the error occurs on starting up the software. Have sent crash reports via the error popup. Urgent help requested!