Bug Reports

A smart collection with the criterion "Caption contains words <word> <word>" won't match a photo whose caption contains "<word> <word>".   To reproduce, open this test catalog: https://www.dropbox.com/s/4cox1uzkg4bs3ps/contains-words-bug.2023.05.21.zip?dl=0    which contains four photos with the captions "ab ab", "abc abc", "xy xy", and "xyz xyz". Observe that the four smart collections with criteria "contains words ab ab", "contains words abc abc", "contains words xy xy", and "contains words xyz xyz" aren't matching the corresponding photos:     Tested on LR 12.3, on Mac OS 13.4 and Windows 11.   See here for the motivating use case: https://www.lightroomqueen.com/community/threads/detecting-duplicated-specific-text-in-a-caption.47765/  

When I use "+" key to go up on the exposure slider it stops my arrow keys from being able to move left and right on the film strip. If I press "+" it does its job and makes the slider go up but it makes it so I can't go left and right using the film strip. However, if I press "-" it works fine and I can still select the next and previous images with the arrow keys.   I've gone back to 13.4 and it works fine so it's clearly the update is the problem. 

Why is rotating using the crop tool so awful in LR Classic compared to ACR, I'm running a powerful PC with loads of ram, RTX3080. Watching in Task manager and it seems the GPU isn't being used at all?!? See attached videos. All drivers, etc. are up to date.System info from LR: Lightroom Classic version: 12.3 [ 202304101834-a085245c ] License: Creative Cloud Language setting: en Operating system: Windows 10 - Home Premium Edition Version: 10.0.22621 Application architecture: x64 System architecture: x64 Logical processor count: 24 Processor speed: 4.0GHz SqLite Version: 3.36.0 CPU Utilisation: 0.0% Built-in memory: 65448.6 MB Dedicated GPU memory used by Lightroom: 4944.5MB / 10067.0MB (49%) Real memory available to Lightroom: 65448.6 MB Real memory used by Lightroom: 2594.8 MB (3.9%) Virtual memory used by Lightroom: 8524.4 MB GDI objects count: 882 USER objects count: 2856 Process handles count: 6887 Memory cache size: 115.7MB Internal Camera Raw version: 15.3 [ 1451 ] Maximum thread

Hello everyone. I've been using LR for a long time, previously on an intel based Windows 10 laptop. It was a bit slow, but usable. Now I am using m1 macbookair, both MacOS and LR are up to date and the issue persists. Since couple versions ago - LR is not usable for me. My collection is huge, has photos on several external hard drives, but i mostly use one, with most current shots. Since 3-6 months my LR is UNUSABLE. I push the B key to add image to target collection - nothing happens. I push it again - nothing happens. After couple minutes - some photos appear in the target collection, others don't, because i pushed the button more than once. It's very annoying. Sync activity goes back to some photos on random external hdd (not currently connected) form way back - i haven't done anything with those photos but there are sync errors for some reason, because why not? Also - i create a collection - and it doesn't appear immediately.I create another one - after 20 minutes LR wakes up, that

Lightroom Classic Mac OS, 14.0.1 release, Mac OS Sequoia 15.0.1, Macbook Pro M2Max With cloud sync enabled and working ( there are images in sync queue)  it is impossible to appy Adaptive Portrait presets, its starts lagging,  glitching, masks won't appear in the masks list, the small dialog window which should appear with Portrait Preset progress is not appearing, then it can pop up a minute later, and stop responding. As a result user can't continue to work with the app, one has to force quit. I will try to attach a video of screen recording with this bug.  This is one instance of the same old bug filed by me long time ago (in July, after the first release of Lightroom Classic with revamped sync engine).  I tried reporting it muliple times but each and every time my topic was actively mismanaged by moderators:  it was relegated to discussions, then the title was edited by moderators to make it totally irrelevant to the core issue, then locked, then merged wit

I have encountered an instance where a wide gamut orange colour appears desaturated in HDR editing mode. I have the uploaded output PQ HDR AVIF files to https://andrewkeyanzhe.github.io/posts/Lightroom_vs_darktable/ for comparison. My website serves the uncompressed HDR AVIF files, so you should be able to see the difference on an HDR capable device and browser (e.g. Macbook Pro with XDR display with Google Chrome)   The camera used is the Panasonic Lumix S5ii   Details:  Version of the app - Lightroom 14.2 (Camera Raw 17.2), Lightroom mobile v. 10.3.1 71F6C8/202 Platform and OS version - Macbook Pro 16 M1 Pro, macOS Sequoia, iPhone 14 Pro Max, iOS 17.5.1 Basic steps to reproduce the problem - Download the raw file https://drive.google.com/drive/u/0/folders/1YIhkxHvp77HHTaanyFJ5LXX28jH74Rau , open in Lightroom, turn on HDR editing mode, increase the exposure by 3.4 stops so it matches https://youtu.be/0FYjApop7Mk?si=S-cXCX-0hyAvsT

Many items in the View > Sort submenu are always greyed out, though they're not greyed out in the drop-down Sort menu in the toolbar.    Tested with several catalogs on LR 14.4 / Mac OS 15.5 and Windows 11.   Mac:     Windows:          

if I go from one image to the next in the library or development module they often are not sharp unless I zoom in and out. It does not happen with every image but with a lot of them.Funny enough the problem does not occur if I scroll through my images on LR 4 so it definitely has to do with the Classic CC version.I am using MAC OS High Sierra version 10.13.4Please help 

I am having a similar problem exporting a Text Preset.  When I am creating it, there is a horizontal line that cuts it off and I can't move it so the whole letter is inside the area.  I had to make an image of the Signature to be able to have it complete, but I would like to be able to use the Text option which has such a nice drop shadow.  I am using Lightroom Classic and Photoshop CC with last updates. Thank you very much! Gloria 

Ever since LR 7.3 introduced the new develop preset format, it takes O(n^2) time for a plugin to access n develop presets. Some users have 5K, 10K, or 15K presets, and it can take minutes for a plugin to access all of the presets: for _, folder in ipairs (LrApplication.developPresetFolders ()) do for _, preset in ipairs (folder:getDevelopPresets ()) do ... Users think the plugin has crashed or hung! While having 10K presets may seem unusual, there's no excuse for LR to take minutes to return all the presets.Here's how fast my LR 14.3.1 / Mac OS / Macbook Pro M2 Max (2023) loads presets versus the total number of presets:   Note that Excel has fit an n^2 curve to the data with R^2 = 0.9998, a nearly perfect fit.   I'm developing a new plugin that would like to access all the presets, and I know from previous experience that users with several thousand presets or more are not that rare.  It would take about 25 seconds to load 5000 presets and 100 seconds

After updating to the new Lightroom Classic with the content aware fill healing feature, while using the tool, I'm not able to navigate around the image by holding down space bar. It works at first, but as soon as I put down a content aware correction, it no longer works. I have to click outside of the photo entirely before it works again. Seems like a small bug that makes the experience frustrating.

The Metadata > Import Keywords command chokes on keyword names containing 4-byte UTF-8 characters. The Any Tag plugin exports and imports them correctly, confirming the problem is in the Import Keywords command. See here for the original use-case: https://www.lightroomqueen.com/community/threads/problem-with-importing-kewords.53113/   To reproduce on LR 14.4 / Mac OS 15.5:   1. Do Create Keyword Tag, and copy/paste this name for the keyword: flag 🏁 Observe that it appears in the Keyword List:   2. Do Metadata > Export Keywords > Include Keyword Tag Options and then > Exclude Keyword Tag Options, creating "Lightroom Keywords.csv" and "Lightroom Keywords.txt".   3. Open the .csv and .txt files in a UTF-8 capable app, e.g. Textedit (Mac) or Notepad (Win). Observe that the flag symbol is present in both: 4. In LR's Keyword List panel, delete the keyword created in step 1.   5. Do Metadata > Import Keywords, select "Lightroom Keywords.csv", a

I use a custom watermark (graphic/png) in LR Classic (12.2.1)Everytime I export pictures with watermark, the first picture is always wrong. The main colour of my watermark is yellow. The very first pics watermark becomes blue, this happens mostly once per LR session, first export of this session. I already tried to deactivae GPU support for export like mentioned in another thread in this community, but this didn't changed the behaviour.Wrong: Correct:

Hello, I installed LR 14.4 on Mac OS - Develop module - it takes wery wery long time to "Paste Settings from Previous" image when both images are denoised - the time is so long, that it looks like the image is denoised again, even if it was allready denoised. I apply Denoise as a batch to all high ISO images after grading because it takes a long time and I don't need to sit at the computer, but now it tries to apply LR to each image over and over again when "Paste Settings from Previous" is used, even on images that dont need it.    Is here a solution/workaround to skip Denoising from "Paste Settings from Previous"  image? 

I'm trying to learn how to get the most from my new Z6III and was using the LRC 14.3.1 "tethering" functionality but realised it was always capturing two JPEG files ecen though camera set to RAW+JPEG. I switched to using NX Tether 2.3 and without making any changes to the camera find that it captures an NEF and a JPEG file. Am I doing somethi ng wrong or is it a bug in LRC?

Normally, you can apply Transform > Auto to a batch of photos by syncing/copying with just the Upright Mode checked.  The Auto transform settings will be recomputed for each target photo.   But if you accidentally sync/copy Auto mode to target photos with both Upright Mode and Upright Transforms checked, Auto won't be recomputed on the target photos, and they'll display the Update button in the Transform panel.  This is as-designed.   If you try to correct the mistake by copying Auto mode again but with just Upright Mode selected, then Auto won't be recomputed on the target photos, and you'll have to click Update on them one by one.  This is incorrect. The photos have become "poisoned", and no use of Sync, Auto Sync, or presets will compute Auto automatically on the entire batch -- you'll have to click Update on each photo individually.  Too bad if there are hundreds of poisoned photos.   I've discovered just one way to clear the poisoned

I am runnng the current LrC and I am currently on Mac OS 15.5, and on at least two different M chips with well endowed machines. The problem has been present for many versions of both LrC and the OS. The problem occurs when I am typing in the Title or Description field for an image. The first symptom is that the cursor position becomes eratic and the text entered becomes garbled, often duplicated and not even consistently visible until after I have restarted LrC. If I stop and restart LrC, I can correct the garbled text in the text box and proceed. What usually happens though is that LrC blows out completely and I am left with bug report windows for Adobe and Apple. I always fill these in so you should have many tens of example crash reports. I recently noticed that the problem may only occur after I turn Spell Check While Typing mode on. (Wish it was on by default but that is another story and shoukd be a post maybe). Can I be of more assistance in resolving this? Just let me know. As

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".