Bug Reports

Synchronize Folder sometimes shows photos as missing when they're not. To reproduce in LR 14.4 / Mac OS 15.5.   There was a previously reported bug with similar symptoms fixed in LR 13.5, but that one was related to the option Treat JPEG Files Next To Raw Files As Separate Photos, whereas this instance isn't: https://community.adobe.com/t5/lightroom-classic-bugs/p-synchronize-folder-incorrectly-shows-photos-as-missing/idi-p/14191413   Another person just reported these symptoms as well in LR 14.4 / Mac OS 15: https://www.lightroomqueen.com/community/threads/synchronising-missing-files-are-not-missing.53034/   1. Download and open this catalog: https://www.dropbox.com/scl/fi/9tefvumd9k9efjhd9dlyt/sync-folders-bug.2025-06-23.zip?rlkey=brpd83m87qs4xk3lb1ugy759d&dl=0    2. In the Folders panel, right-click the folder "test-pics" and do Synchronize Folder. Observe that it reports 1 missing photo:   3. Click Show Missing Photos and observe the special

Lens corrections don't work with Photo Merge HDRs merged from DNGs. They do work correctly with DNGs not produced by Photo Merge.   Tested with LR 14.3.1 / Mac OS 15.5:   1. Download and open this catalog:  https://www.dropbox.com/scl/fi/vhm0r8s17csaatgs153pw/hdr-dng-lens-profile-bug.zip?rlkey=6i2o4jgomfzpfbj8gm4eizak8&dl=0    It contains raws from five cameras: Canon EOS R6m2, Fujifilm X-T5,  Nikon Z 7_2, ODS OM-1, Sony ILCE-7C. All the raws have Lens Corrections > Enable Profile Corrections checked.   2. Observe that for each camera, there are three stacks containing these stack tops:   - an HDR made from two copies of the original raw, e.g. DSC_0102-HDR.dng.   - an HDR made from full-resolution DNGs exported from two copies  of the raw with the options Image Format: DNG, Lossy Compression, e.g. DSC_0102-full.dng.   - an HDR made from reduced-resolution DNGs exported from two copies of the raw with the options Image F

When an external or network volume is disconnected and later reconnected, the Metadata panel can sometimes still show "File not found" in File Size rather than the actual size.  I think this is another bug with the caching of metadata in "<catalog> Helper.lrdata". There have been three recent reports about this: https://community.adobe.com/t5/lightroom-classic-discussions/file-size-not-shown-for-files-on-network-drive/m-p/13588066 https://www.lightroomqueen.com/community/threads/metadata-says-file-not-found-in-the-file-size.46971/ (two reports)   The workaround is to exit LR and delete "<catalog> Helper.lrdata".   To reproduce:   1. Import a photo from an external drive with Add.   2. Exit LR, disconnect the drive, delete the "<catalog> Helper.lrdata" file, restart LR.   3. Observe that the photo is correctly marked missing and the Metadata panel shows "File Size: File not found":   4. Exit LR, connect the drive, restart L

LrDevelopController.getSelectedTool() returns "masking" rather than the documented "local_point_color" when masking Point Color's eyedropper is selected.   To reproduce in LR 14.2 / Mac:   1. Place these lines in the file "getselectedtool.lua" in the Scripts folder: import "LrDialogs".message ( import "LrDevelopController".getSelectedTool ())   2. Restart LR.   3. Open a photo in Develop.   4. Add a linear gradient mask.   5. Select the eyedropper in the masking Point Color subpanel.   6. Do the menu command Scripts > getselectedtool.   7. Observe the message dialog says "masking" (incorrect) rather than the documented "local_point_color" (correct):   Note that the SDK documentation indicates "local_point_color" should be returned:      

Calling LrBinding.makePropertyTable() in a script in the Lightroom Scripts folder always fails with the error:   "LrBinding.makePropertyTable: missing functionContext"   This prevents making simple scripts using LrDialogs. presentModalDialog(). It also makes it harder to file bug reports involving dialogs.    To reproduce on LR 14.3 / Mac OS and / Windows 11, place this script in the Scripts folder: local LrBinding = import "LrBinding" local LrDialogs = import "LrDialogs" local LrFunctionContext = import "LrFunctionContext" local LrTasks = import "LrTasks" LrFunctionContext.callWithContext ("X", function (context) local success, err = LrTasks.pcall (function () LrBinding.makePropertyTable (context) end) LrDialogs.message (tostring (success), err) end) LrFunctionContext.postAsyncTaskWithContext ("X", function (context) local success, err = LrTasks.pcall (function () LrBinding.makePropertyTable (context) end) LrDia

I discovered this today after a painstaking couple of hours. I am on the latest LRC 14.2. I am not going to bore you guys on how I found this issue but here it is.    Canon R6 MK2. Shooting RAW.    I was working on some wedding photos and was applying adaptive blur Circle to the RAW files. All the RAW files that had this adaptive blur were failing. Good thing I didn't apply this to all images so I was able to go over my steps and figure this out.    I didn't check all the adaptive blur types but this was annoying time lost as I had also done AI enhance on my images which took forever. It doesn't matter if you enhance or not, the issue persists just for the adaptive blur Circle. 

I don't know what my next steps are because nothing really works.     Here is the error rport Moderator: We’ve removed your pasted Crash Report from this post. Crash reports are of little use in a vacuum. It is far more important to submit the Crash Report with your email attached so it can be reviewed in full by the engineering staff. Additionally, posting this much text into a forum post breaks several forum features, including translation. Lastly, Community Experts are not likely to scroll dozens of pages to review the information here. If you feel you must post a report in addition to submitting it via the dialog, please use an attachment instead. 

Thank you for your understanding. 

The text filter: Caption Ends With "ab" matches a photo with caption "xab" but not with caption "aab".

When the SDK method photo:setRawMetadata("gps", coordinates) changes the GPS coordinates of a photo, the Library Metadata panel doesn't show the new coordinates. The same problem occurs with the fields "gpsAltitude" and "gpsImgDirection".   To reproduce on LR 14.3.1 / Mac OS 15.5:   1. Save the attached file "setrawmetadata-gps-bug.txt", rename it to have the .lua extension, and move it into the LR Scripts folder. Restart LR.   2. In Library, select a photo.   3. In the Metadata > Location tagset, set GPS to these coordinates: 37°19'50.6"N 121°53'40.1"W Observe that the address suggestion matches the coordinates:   5. Do Scripts > setrawmetadata-gps-bug, which sets GPS to these coordinates: 40°43'42.3696" N 115°28'58.9836" W Observe that the address suggestion has changed to match those new coordinates, but the GPS field still shows the coordinates from step 3 (incorrect):   6. Restart LR, and observe that the changed GPS coordinates are now displa

LR Classic is frequently crashing in the metadata caption box. I can't reliably reproduce the issue, it just works for a while then LR disappears and then crash report window appears.   I do notice the text drawing in the caption box gets a bit flaky. Odd or just deleted text appearing then disappearing. MacOS's new caps-lock indicator gets a bit flaky too, before a crash.  I also have dynamic spell checking on, but that appears to be stable.   LR Classic version: 13.0.01 MacBook Info  Model Name: MacBook Pro   Model Identifier: MacBookPro18,4   Model Number: Z15H000UBX/A   Chip: Apple M1 Max   Total Number of Cores: 10 (8 performance and 2 efficiency)   Memory: 64 GB   System Firmware Version: 10151.1.1   OS Loader Version: 10151.1.1  

Im having an issue with generative AI fill where the selection that I draw disappears in my "refine selection" selection. Only the selection disappears, but it still works when I prompt it to remove. Oftentimes I can brush back over it and it will begin to show what my previous selection was.   https://vimeo.com/1091870251?share=copy The video shows that when I brush back over the selection, it selects my previous selection, but it does not stay selected. It continually disappears, but will still generate content there when prompted. It makes it difficult to refine the shape around an object when I cannot see what I am generating. 

I am at my wit's end. I have been a LR user since Beta (2006), and have devoted tens of thousands of hours to creating and managing my catalog. But, in the last 4-6 months, performance (and stability) has reached unusable levels.   Here are my system stats (also attached)   Ryzen 9 79503D 192GB Ram 32TB NVME Raid0 (Catalog + Previews) (17 GB per second sequential read] 96TB Thunderbolt 4 attached RAID 6 (Original Photos) [1.6 GB per second sequential read] Radeon 7900XTX w/ 24GB V-Ram 4X 27 inch 4k displays Windows 10 Pro for Workstations 22H2 - 19045.4894   Here are my lightroom settings   Lightroom 13.5.1 Full GPU Acceleration No XMP Autowrite 6.06GB Catalog File Size Catalog Optimized at every close (daily) 3840/High Previews Never Discard 1:1 Previews Replace Embedded Previews during idle OFF Sync OFF 200GB Camera Raw Cache Generate Previews in Parallel ON Enable HDR in Library OFF   Here is what I have tried to fix performance   Create a bra

When Sync with LR Cloud downloads and imports photos from the cloud, it creates a pseudo-volume and psuedo-folder in the Folders panel representing the contents of the "Mobile Downloads.lrdata" folder containing the imported photos (e.g John's MacBook Pro > Imported Photos).  When a plugin tries to access the pseudo-folder, the methods catalog:getFolders() and catalog:getActiveSources() return invalid LrFolder objects.   To reproduce on LR 14.3.1 / Mac OS 15.5:   1. Download and unzip this catalog: https://www.dropbox.com/scl/fi/plzlyaxuw7os6coeb0d7n/folder-bug.2025-6-04.zip?rlkey=d1hpg6i4wwz25x4unpv01lvt0&dl=0    2. Copy the file "folder-bug.lua" from the catalog folder to the LR Scripts folder and start LR.   3. In the Folders panel, select the Imported Photos pseudo-folder under the pseudo-volume John's Macbook Pro:   4. Do the menu command Scripts > folder-bug. Observe the following incorrect output:   The LrFolders representing w

    Say your keyword heirarchy is like this:A > B > C D > B > E D > B > F   One of the keywords that appears in the "Keyword Suggestions" box will be "E < B". This suggestion is obviously referring to E < B < D (which is D > B > E). The expected result when clicking this suggestion is that it adds the "E < B < D" keyword to the photo. However, when you click the "E < B" suggestion, it creates a new E < B < A tag (which is A > B > E).     This issue also happens with the autocomplete in the textbox of the "Keyword Tags" box.     System Info: Lightroom Classic version: 14.3.1 [ 202505061331-b063faef ]License: Creative CloudLanguage setting: en-USOperating system: Mac OS 15Version: 15.4.1 [24E263]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.36.0Power Source: Battery, 99%Built-in memory: 16,384.0 MBDedicated GPU memory used by Lightroom: 1,213.4MB / 10,9

I use Lightroom for culling through wedding photos, and as of yesterday's update, any time I increase or decrease the rating of an image (or apply any other kind of edit) it will add 4 hours to the capture time, therefore sending that photo to a random place later in the collection, only for me to find it again as I'm moving through. In fact, it just happened twice, as I edited a photo that had already been changed, and it added 4 more. What in the world??? This could prove to be exceptionally annoying.   Photos are syncing.   LR version 14.1 MacOS 14.7.1 M1 Max

The Help windows displaying keyboard shortcuts still have many errors. While a large number were fixed in LR 12.1, many were not, and some new errors were introduced.   The Any Shortcut plugin's Analyze > Analyze All TranslatedStrings Files generates the file "errors.txt" (attached) containing all these errors. It should be run before every new LR release. The plugin's option Correct Help Keys In TranslatedStrings Files will automatically fix all of the errors.   I've summarized the errors below, with explanations for what's gone wrong and how to fix them.   ---------------------------------------------------------------------------- The help keys for shortcuts containing Delete (Mac) / Backspace (Win) need to be specially encoded -- they should refer to Delete or the localized version of Delete (if there is one).  LR will automatically translate that to Backspace (or the localized version of Backspace) on Win.   Many instances of help keys incorrectly conta

File > Export doesn't remember the previous setting of Resize To Fit when Image Format is DNG.   To reproduce on LR 14.3.1 / Mac OS 15.5:   1. Select any photo.   2. Do File > Export, with the the File Settings options Image Format: DNG and Use Lossy Compression, and the Image Sizing option Resize To Fit: Long Edge, 3000 pixels:     3. Do File > Export again, and observe that Resize To Fit is unchecked.

Dialog windows created by LrDialogs.presentModalDialog() don't always close fully on exit.   To reproduce on LR 14.2 / Mac OS 15.3.2 / Macbook Pro 16" 2023 Apple M2 Max:   1. Download and install this plugin: https://www.dropbox.com/scl/fi/rpm9osljz9yv9arxu8yqk/dialog-bug.lrdevplugin.2025-03-24.zip?rlkey=fuvww8hkkhatibotqbqu8fvaw&dl=0   2. Do File > Plug-in Extras > _Dialog Bug > Bug and observe this dialog:   3. Click OK and observe the dialog close properly.   4. Do File > Plug-in Extras > _Dialog Bug > Bug again and observe the same dialog.   5. Click OK and observe that the dialog hasn't completely closed:   6. The dialog remains until you restart LR.   * * *   This bug persists after resetting preferences and opening a new catalog. I first noticed it with my Debugging Toolkit,  where it's a serious annoyance. Nine others have reported similar symptoms with creating snapshots starting with

macOS 15.2 Lr Classic: 14.1.1   Steps: 1. In Develop mode, create a new snapshot for a photo 2. Enter a name for the snapshot in the New Shapshot window and click Create Results: The New Snapshot window persists as an empty window until the app is canceled.

After updating Lightroom Classic to v14 and converted my database, all the edited photos that had a "Subject Mask" applied now have an empty mask with a warning and exclamation mark (!). If I let Lightroom correct the mask pushing the exclamation mark on a single photo, it seems the correct subject is selected, keeping the edits. If I do the same with multiple photos together it appears teh usual form that tells that the AI masks are recalculated, but at the end all the masks are still empty with warnings.

Lightroom Classic CC, latest version, freezes when I use "Synchronize folder" and have the "show import dialog before continuing" option selected. (Not only does it freeze but it ends up using a ton of CPU, more than 200% per Activity Monitor, and the fans start going like crazy.)Lightroom synchronizes the folder just fine when I DON'T have that option selected, but I need to be able to use that option. The problem occurs whether or not the "scan for metadata updates" option is selected.I'm on a Macbook Pro, latest version of Mojave. In Lightroom, the issue occurs for me in the latest version of Lightroom Classic CC. Per a different forum post in which someone solved their problem by downgrading to v 7.5, I tried that but the problem remains.I did NOT have the problem in Lightroom 6 (from 2015), which was what I was using until just recently when I got a new computer and needed to upgrade my OS. I'm still trying to get back up and running with Lightroom on the rebuilt system, and this

use case: I want to browse a set of photos and incrementally add some keyword, this involves going back and removing the same keyword. Background: I am using Lightroom 14.3.1 (latest) on Windows (Windows 10 version 22H2 Build 19045.5737). Lightroom language is english. Feature in question: For quickly setting keywords, there is the "keyword shortcut" feature, which exists since at least Lightroom 6 and speeds up work a lot.I am aware that you must first press Ctr+Alt+Shift+K to set the "keyword shortcut", then you can press Shift+K on an in dividual picture to add/remove it.I am in Library module, Loupe view when I use this feature. expected behaviour: when pressing Shift+K, keyword is added/removed and a small popup is displayed. Popup similar to pressing "P" or "U", giving "Flag as Pick" or "Remove Flag". actual behaviour: the shortcut keyword is added or removed but I see that only if I have the "keywording" panel open. There is no popup.If I do not have the "keywording" panel open,

Hi,I’m experiencing a recent issue with the Crop tool in Lightroom Classic. When I try to crop an image after applying a rotation correction (either automatic or manual), the crop frame won’t let me move it fully to the edges of the image. It’s as if there’s an invisible boundary about one centimeter from the top or side edges, preventing me from placing the crop where I want. This didn’t happen earlier today and started occurring with the last two photos I’ve edited. I’ve tried: Toggling “Constrain to Image” on and off Using different aspect ratios (including “Original” and “Custom”) Removing the rotation, cropping first, and then reapplying the rotation Restarting Lightroom In all cases, the issue returns as soon as I apply any rotation, even a minor one. I’m attaching a screenshot that clearly shows how the crop frame cannot be moved freely even though the image has visible content. Is there a setting or recent behavior that could be causing this?I’d appreciate any guidanc

After updating LR Classic to version 14.3, the "update" button in the Transform panel stopped working after using the settings from the previous photo. Transform remains wrong even after selecting a different option (vertical instead of auto, etc.) and the Update button remains white. MacOS 15.4.1, LRC 14.3

When cropping an HDR Panorama using two displays, the full image is not shown correctly in my secondary display. My primary display will show the full panorama, but when I try to crop it the secondary display erratically shows white space where there should be imagery. If I make crops, the secondary display will update (slowly), but continue to show white space. This white space seems to mimic the boundary of the original panorama.   I recently upgraded from a 2019 iMac to a 2023 M2 Max Studio with 96gb ram. The problem used to occur on my iMac and I was hoping that the new powerful machine would make a difference. It didn't. I'm using MacOS Ventura 13.5 and LR 12.5. But this issue also occured on my 2019 iMac, using different OS and different LR Classic versions.    I have two external monitors. The one I'm using with LR is a 4k display. The other monitor I use is an old Apple Thunderboldt display (2560 x 1440). I tried using that as my LR secondary display, but the iss