Bug Reports

I updated to LrC 15.5 a few hours ago.  Since then LrC has problems with video files.  The first problem I noticed was that when I tried to synchronize a folder that had two new video files.  After a couple of minutes I got the error message “An unknown error occurred while reading the video file. (2)”.  I had just completed those files with DaVinci Resolve so I went back and produced the same files again to check if DR had made an error.  When I tried again with the new files but got the same errors.  I was able to play both videos without any issue using VLC Media Player, so they seem to be OK.  I then shutdown LrC and did a backup including optimizing the catalog, and then restarted it to see if that made any difference, but same error.  Then I started looking at other videos that were already in LrC and found that when browsing them in the Library module, most of them pop up a message “There was an error working with the video”.  They will not play in LrC but work fine with VLC Med

Installed this and my tethered camera setup no longer works.  It appears to work as before, but no images are transferred.  Canon R1, Windows 11.  Anyone else having tethering issues?

LR 15.5 made numerous inconsistent and incorrect changes to how the Delete and Backspace keys are  translated in Help > Library Module Shortcuts and Map Module Shortcuts. Prior to 15.5, LR followed the principle of using the names of the keys as they appeared on the most commonly used keyboards for that language. For example, on Spanish (ES) keyboards, the Delete key is labeled Supr, and LR's Help used Supr for the Mac shortcuts for Library > Remove From Library, Map > Delete GPS Coordinates, and Map > Delete All Location Metadata. This convention makes sense -- Help uses the names of the keys that are displayed on the user's keyboard. But in 15.5, the displayed names of the Delete key (Mac) were changed in all 15 non-English languages, for some but not all of the commands assigned Delete.  Similarly, the displayed names of the Backspace key (Win) were changed in 6 languages, for some but not all of the commands assigned Backspace. For example, in Spanish, the name for the

Auto updated to LrC 15.5 on my MacBook Pro M3 Max last night. Came home from shooting a concert and the import dialogue would appear to function normally, but after hitting the actual button to import, nothing happened. It went back to the grid view, briefly the import status bar appeared in the top left then just as quickly disappeared. I tried different ways of doing it, enabling full disk access (already was set), copy vs convert to dng, even created a whole new catalog and did a hard reset on my computer. Same issue every time. Decided to downgrade to 15.4.1 through the creative cloud as I was able to recently import and edit on that version. Opened Lightroom back up and viola, everything worked just fine. Gonna stick on this version and disable automatic updates until I hear adobe fixes this.

LR 15.2 introduced inconsistent names for the Backspace and Delete keys in the French in-program shortcut help. WindowsLibrary Help:Map Help:“Supprimer” is French for the Delete key. But on Windows, the Backspace key is called “Retour arrière”. MacLibrary HelpMap Help: On Mac, the Delete key is called “Supprimer”. So the two instances of “Arrière” should be replaced by “Supprimer”. 

After starting LR, clicking the GPS badge of a photo centers the map on the last-displayed location rather than the coordinates of the clicked photo. To reproduce on LR 15.5 / Mac OS 26.4.1: 1. Open the attached catalog. 2. Go to Map view. 3. In the filmstrip, click on the GPS badge of "miami.jpg". Observe the map centers on Miami (correct). 4. Go to Library. 5. Restart LR. 6. Click on the GPS badge of "san francisco.jpg". Observe that the module switches to Map view and the map centers on Miami rather than San Francisco (incorrect). 7. Go to Library. 8. Click on the GPS badge of "san francisco.jpg" and observe the map moves to San Francisco (correct).  

Hi everyone,I'm having an issue with the latest version of Lightroom CC on a MacBook M5 Pro running macOS Tahoe 26.5.1. (I was experiencing the same problem on 26.5 and decided to update hoping it would fix it, but unfortunately it didn't.)Since this morning, it's been impossible to to use Noise Reduction, even though my internet connection is working perfectly. I've already updated both Lightroom CC and macOS, cleared the cache, and optimized the catalog, but I keep getting this error screen whenever I try to use Noise Reduction.Has anyone experienced the same issue or knows how to fix it? Any help would be greatly appreciated. Thanks! 🙏 

What an awful release. Don't get me wrong, I'm glad to see new developments, but this Lightroom update is an absolute disaster. After culling just 5-10 images, the AI Assist culling tool completely hogs all my RAM, causing my Mac to freeze and throw memory errors. It’s a total nightmare.Culling images via the library module is practically impossible right now - everything just locks up. Even with previews pre-generated and trying to run AI Assist culling, the performance is still abysmal. On top of that, it frequently fails to even generate a Denoise. What is going on, Adobe?! This is absolutely unacceptable!P.S. The RAM management is completely broken and goes beyond any acceptable limits!  

Steps to Reproduce: 1. Select an Ai mask2. Move any of the Refinements sliders from form the current value to another one and back to the current value but NEVER releasing the slider.Actual Result: A step is recorded in history but nothing changed from step 1 and step 2, the value chosen in UI is the same.Expected Result: Moving AI masks "Feather" or "Edge" sliders DOES NOT record an history step when the UI value is the same as before.Addendum: There is floating point difference in the values when moving a slider back and forth to the same value but it should not matter.Feather at 30 Feather moved from 30 to 30 again 

When I want to skip through hundreds or thousands of photos in Lightroom Classic (Version 15.0.1) in the film strip I mostly get this very annoying problem: after holding the arrow key to the right or left for a few seconds it doesn't stop anymore to speed through the images though I'm no more holding the arrow key. Sometimes it's going on for "just" a couple of hundred further photos and sometimes even through thousands of photos until the very last photo in the strip. I can't even stop it.This first started three months ago when I updated on a new MacBook. On my old Macbook this never happened in years. Does someone got an Idea to fix this bug?

 EnvironmentAdobe Lightroom Classic 15.4 (also observed in earlier versions) Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() becomes the active window, but no control initially receives keyboard focus.As a result, standard keyboard interaction is unavailable immediately after the dialog opens. Pressing Enter, Esc, Space, or Shift+Tab has no effect. Keyboard navigation only begins after pressing Tab once (or after clicking any control with the mouse).The same reproducer behaves differently on macOS, where the first control immediately participates in keyboard navigation.Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run File > Plug-in Extras > Floating Dialog Keyboard Focus Reproduction Without using the mouse, press the following keys in order: Enter Esc Space Shift+Tab Finally, press Tab.A complete standalone reproducer plugin is attached. Expected Resu

Select a number of photos say about 200 on the film strip. auto sync on Hit auto to adjust the settings automatically. Can be done on library or develop module does not matter to the issueLightroom will adjust the settings automatically and you can go to different photos and the automatic settings would have been applied to all the photos.Now adjust one setting on one photo with auto sync on (eg. bring the vibrance or saturation down back to 0 or a different amount….in this case vibrance to -5)Browse the rest of the photos … The rest of the photos should now have auto adjustments applied + the vibrace slider to where you adjusted it manually. However when I do this other than some photos that are in immediate to left and right of the photo that was active while I did the vibrance adjustment the rest of the photos has the auto adjustments back down to 0 and the only vibrace is at -5. This seems to affect tone and vibrance saturation.. not presence (probably because auto does not affect

Letters in texts added in books in Book module are rotated in LrC 15.3. The rotation seems to happen per line as displayed (not per carriage return). Switching back to 15.2.1 put the letters correctly again, and upgrading to 15.3 rotates the letters.Attached two screenshots of the same page in a book in 15.2.1 and 15.3.15.2.115.3The letters are also rotated for a new book created in 15.3.

Just starting today the Map module is leaving behind markers for a photo or photos that have been moved. It also continues to show markers for photos that have been opened but are no longer in the directory being worked in. If I leave LRC and come back in, all is well but I've never had to do this before. It is more of an annoyance than a major issue, but it does clutter up my screen while moving things. I am in the process of locating old photos that have inaccurate or no geotagging and this behavior is slowing me down. I’m running 15.3 on a MacBook Air. Has anyone else seen this or have a suggestion of how to fix this behavior? 

When multiple videos are selected, Edit Capture Time incorrectly shows the message for a single photo selected, rather than a message that indicates the capture times of the other videos will be adjusted by the same amount as the first: When multiple photos and at least one video is selected, the message incorrectly states that videos will not be adjusted: But in these cases, the problem is just with the message being displayed. Clicking Change All correctly adjusts the capture times of the other videos by the same amount as the most-selected photo/video. Tested on LR 15.4.1 / Mac OS 26.4.1.

Lightroom Classic version 15.4Mac OS 26, Version 26.5.1Mac Studio M4 MaxPrior to the latest upgrade to Lightroom Classic I was backing up my catalog to my Synology drive. I now get the unable to write to drive error, check permissions and available space on the drives. I can backup the file locally on my MAC and then copy that over to the Synology drive. So it does not seem as though permissions is the issue. Have 16TB of storage on the Synology and 782 GB free on a 1 TB SSD on the Mac. Only started when after the latest upgrade to Lightroom Classic.

In LRC, I have many hierarchical keyword structures, amongst which are locations, i.e. Country/State/City and in some cases location or street name.  Since version 15.4.1, LRC deletes upper level location keywords (Country and State, or when there's a fourth level then it deletes the city too) after a photo has been synced to the cloud. The keywords still exist in the cloud. I have checked other hierarchical trees and the keywords are all syncing correctly. If I reenter the locations the save metadata to file, the keywords once again disappear.I'm running LRC 15.4.1 on a Windows 11 Pro computer with Admin rights. Lightroom, catalog and photos are all on (separate) local nvme ssds. Plenty of space, plenty of speed. 

EnvironmentAdobe Lightroom Classic 15.3 Lightroom SDK macOS 26.5.1 Standalone reproducer plugin attachedSummaryA floating dialog opened via `presentFloatingDialog()` does not reopen on the second screen. When the dialog is closed while positioned on a second monitor and then reopened, it always appears on the primary screen instead. Steps to Reproduce1. Connect a second monitor.2. Install the attached reproducer plugin via File > Plug-in Manager > Add.3. Run via Library > Plug-in Extras > Run Second Screen Dialog Bug Repro.4. Choose "Test Floating Dialog".5. Drag the dialog to the second screen.6. Click "Close and Reopen".A complete standalone reproducer plugin is attached. Expected ResultThe dialog reopens on the second screen at the position where it was last closed. Actual ResultThe dialog reopens on the primary screen. The position on the primary screen mirrors the saved coordinates — for example, a dialog closed at the top-left of the second screen reopens at the top-l

EnvironmentLightroom Classic 15.4.1 macOS 26.5.2 Wacom Intuos PT S CTH-490 Wacom Driver 6.4.9Steps to reproduceOpen Develop module. Select Masking → Brush. Paint using a pressure-sensitive Wacom pen. Vary pen pressure.Expected resultBrush size/pressure responds to pen pressure as in Lightroom Classic 15.3.1.Actual resultPen pressure is ignored. The brush behaves as if a mouse is used.Additional informationDowngrading to Lightroom Classic 15.3.1 immediately restores pen pressure functionality using the same hardware, driver and operating system.No changes were made to the Wacom driver, hardware or macOS. Only the Lightroom Classic version changed.Control test: The same Wacom tablet and pen work correctly in Photoshop on the same Mac. Pen pressure affects brush size as expected. The issue only occurs in Lightroom Classic 15.4.1.

Lightroom Classic Version 12.1  OS Name: Microsoft Windows 11 Home Version 10.0.22621 Build 22621   Importing a .MOV file from a NAS drive into lightroom .MOV file originally taken on an i-phone 12 720x960 0.7 MP Imported video is rotated by 180 - so upside down .MOV file originally taken on an i-phone 12 960x720 0.7 MP Video is imported correctly

Sync Settings with Upright Transforms checked doesn’t always check Copy automatically, as was intended by the undocumented change in LR 15.0.  To reproduce on LR 15.3 / Mac OS 26.2 (see the attached screen recording): 1. Save the attached file Upright-Transforms.lrtemplate (created in LR 14) to the Copy Paste Subsets subfolder of the Lightroom settings folder.  Restart LR. 2. Select two photos and do Sync Settings. Click Check None and click Synchronize. 3. Do Sync Settings again, select the subset Upright Transforms, and observe that Crop is checked (correct).  Click Synchronize. 4. Do Sync Settings again.Observe that the subset Upright Transforms is selected (correct) but that Crop is unchecked (incorrect). When you click Synchronize, the Crop is copied, even though it is unchecked.

Then I apply AI denoise, in LR Classic 15.3 it does it in the background which I really like, however once I apply it to let’s say 100 pictures, and start editing the ones that already editable, it is stopping at the last few images. It is toally random where it is stopping but all the AI denoise remains in a stuck position and I can’t edit those photos unless I restart LR Classic. Sometimes these are images that already have some AI denoise on them, I just don’t bother to select the ones that doesn’t have it, so I paste the settings to all. And usually it is stuck it one point of the process.It only goes through the process if I don’t start editing any other photos, just wait for the whole process to finish. Lightroom Classic version 15.3Mac OS Sequoia 15.7.5Maxed out M1 Max MacBook Pro with Apple Studio Display 5K.

The red-x Reject badges persist on thumbnails in the filmstrip even when all the Select and Reject checkboxes in Assisted Culling are unchecked.  To reproduce on LR 15.4.1 / Mac OS 26.4.1: 1. Download and open the attached catalog. 2. In the Assisted Culling panel, uncheck all the checkboxes. Observe that the red-x badges still appear on the filmstrip thumbnails:  I haven’t discovered any way to make them disappear, including by deleting the Helper.lrdata file.

This is core to my workflow, an absolutely necessary feature I use every single time I’m editing photos. In the Develop Module, under let’s say the “Basic” adjustments panel, one should be able to adjust values (such as Exposure, Contrast, Highlights, Shadows, Whites, Blacks, etc.) while hovering the mouse cursor over a section of the photo (in the Loupe View) and see RGB values changing under the histogram.In the latest version, the RGB values are no longer displayed under the histogram while those values are being adjusted. For example, I click the number next to the ‘Highlights’ slider and move my cursor over to a white part of the image. When I press the up arrow on my keyboard to increase the value of that number, the RGB values under the histogram *should* be displayed and also increasing. Instead, they are not displayed at all.I have downgraded to the previous version and the program’s behavior returns to expected. This is a brand new computer, fresh win 11, AMD Ryzen 7 7700X; 3