Bug Reports

The update to the Generative Remove AI model in Lightroom Classic 14.5 has ruined it, as it now changes elements outside the painted mask, making it more or less unusable in many situations.

Synchronize Folder > Scan For Metadata Updates can cause frequent spurious metadata conflicts for TIFFs that are stored on NAS.  Over the years many people have reported spurious metadata conflicts that Adobe hasn't been able to track down, and many of those reports involve photos stored on NAS.  Here's a recent report:https://feedback.photoshop.com/photoshop_family/topics/before_after_comparison_of_metadata_conflicts...While the particular use case here may not be that common, it may provide a reproducible test case that points to the bug (likely a race condition) underlying all those other persistent reports.Here are the steps that consistently produce the spurious conflicts in my configuration:1. Connect to a network volume on a 2013 iMac running MacOS 10.14.6. The volume is mounted with SMB 3.0.2.  2. Place 4 1800 x 1200 TIFFs (about 13 MB each) in a folder on the network volume.3. Import them with Add into a LR 9.0 catalog running on a 2019 Macbook Pro

This bug causes DATA LOSS.Description of Issue After viewing duplicates using the new LR15.4 Find and manage duplicate photos feature, and marking some photos (either Original or Duplicate) as Rejected, the use of the “delete rejected photos” function (e.g., through the keystroke cmd-Delete) will cause all photos to be deleted from disk and from the catalog, not just those marked for rejection. Lightroom Classic Version Number (Help>System Info…) Lightroom Classic version: 15.4 [ 202606101834-493069d4 ] OS Version Number ​​​​​​​MacOS 26.5.1 (25F80) Step-by-step Reproduction Instructions ​​​​​​​add a photo, and a duplicate of that photo, to a LR catalog. switch to Duplicates view; the two photos should appear in a stack. mark one of the two photos Rejected. cmd-Delete to delete rejected photos confirm. The Expected Result ​​​​​​​only the Rejected photos disappear from disk and the catalog. The Actual Result ​​​​​​​all the photos - even those not marked Rejected, disappear fr

I have updated the LR to version 15.3, and since that update I cannot sync the edits across multiple photos with auto sync on while using Smart Previews to edit. Some things, like applying a preset works but adjusting exposure, shadows etc do not propagate through the rest of the images… If I do edit while on library module it will work. This works fine with the source files connected and when LR isn’t using smart previews… also lightroom is slower to apply presets etc than the previous versionHow do you fix this?

As the title says, While using the Remove tool, the cycle new spot fill type (or Shift + T) shortcut is not working with lightroom classic, my version is Lightroom Classic 15.3.1. Is anyone else experiencing this? I have tried resetting the preferences or holding (Shift + Alt) upon launching the program but to no avail. Any help is appreciated, thank you!

Using the Copy Settings Subset option of modifed doesn't recognise the cropping if the image angle or aspect ratio haven't been modified. Please delete this post or merge with my later post here: https://community.adobe.com/t5/lightroom-classic-discussions/copy-settings-gt-subset-modified-ignores-crop/m-p/15501384

When applying the Color Profile “Adobe Standard” to an image in Lightroom Classic and then exporting as DNG. Then later importing the DNG back into Lightroom Classic, the Color Profile is set to “Adobe Color” instead of “Adobe Standard”.When opening in Photoshop, ACR shows “Adobe Standard” correctly. Lightroom Classic Version Number 15.3.1 Mac OS 26.5.1  Reproduction Instructions:Either use a random image, set the Color Profile to “Adobe Standard” and export as DNG. Then import the DNG back into Lightroom Classic and see it applies the “Adobe Color” profile.Alternatively, import the attached DNG file and see that the Color Profile is set to “Adobe Color”. Open it in Photoshop and see that the Color Profile is set to “Adobe Standard”.Expected Result: Lightroom Classic also applies the correct Color Profile: “Adobe Standard”.The Actual Result: Lightroom Classic applies the “Adobe Color” profile.Lightroom Classic:  ACR:  

I applied Denoise to 115 files by selecting the files, select Autosync, the clicking the check box on Denoise.  After all files complete Denoise, I again selected the same 115 photos, select Autosync, then uncheck denoise.  The process starts and a status bar appears labeled “Removing Denoise on 115 photos”.  The status bar progresses but after a short time stops.  Checked the photos and find the first 21 have had denoise removed.  Did “Optimize Catalog...” and then restart.  Tried to denoise the remaining 94 photos. Same result as before but this time it denoised another 21 photos before hanging up.  Restart, the did the same process to remove denoise on the remaining 73.  This time it removed denoise from 18 before hanging up. LrC is unable to remove Denoise from the entire set of selected photos.   LrC 15.3, Win11 

black and white outline on my pictures in lightroom classic after update  v15.3 ->  Filmstrip 

I re-edit a photo from Lr Classic in Photoshop. It is in my target collection which is my sync collection. Lightroom Classic says the sync is done. The new version is visible in Lightroom on the web (Chrome). The thumbnail in Lr Mobile is correct. When I open the image in Lightroom Mobile it reverts back to the old previously edited version. Thanks

Short description:When importing RAW and/or JPG files from my Fuji X-T5 into LrC, despite selecting the "Do not import possible duplicates" function, no duplicates are recognised and all images that have already been imported are imported into LrC again. A “-2” is appended to the file names.Duplicates of my RAW files from my Canon R5 II are recognised as such and are not imported. All settings are the same in both cases.LrC 15.2, macOS Tahoe 26.3, iMac with M3LrC 15.2, macOS Sequoia 15.7.4, MacStudio with M4 MaxLrC 15.2 Windows 11 lasted VersionLong Description:The problem I described above, whereby RAW files from the Fuji X-T5 are not recognised as duplicates during import and are therefore not imported, is a little more complicated than it seems.One type of import works, but the other does not.It works when I import the images as follows:1. Connect the camera directly to the iMac -> import > all images that have not yet been imported are offered for import. Images that were imp

Depuis quelques semaines LR Classic crashes très fréquemment, parfois toutes les 5 minutes alors que LR n’est pas dans une activité spécifique ou intensive.Ce problème est apparu peut être après la dernière MAJ de LR, ou peut être de MacOS …??? Les crashes arrivent dans des cirsconstances variées… pas de pattern spécifique et avec une utilisation très peu intensive de LR, visulalisation de photos, parfois lors de déplacements de photos d’un dossier à un autre, mais rien d’intensif..  

So ever sice the update to LrC 14.4 the shutter button stopped working with tethered shooting. I've been using Lightroom to shoot tethered for years with my GFX100S and MBP M2 Max with no issue. I used the GFX tether plugin, then Fuji's Tether App and have both still installed. Whenever I update LrC to 14.4 - or now 14.5 the shutter button in Lightroom just stops working. I get accurate readings of the camera's settings, even live view within Lightroom and I can still manually release the camera's shutter button, but that kind of defeats the purpose, especially with the kind of sets I work with. I've tried disabling both Fuji's tether plugin and tether app in Lightroom's plugin manager, did all kinds of reboots in combination with disabling one, then the other, or both plugins but nothing works. The camera's firmware is up to date and I'm on macOS Sequoia 15.6. The only thing that gets Lightroom to work reliably again with tethered shooting, is downgrading to 14.3.1. Anybody got any id

On a HightDPI laptop, the straighten tool and the eye dropper do not click where the mouse points. This is a big enough problem because it makes these tools unusable. Unfortunately, this seems to be a problem of more than six years and still has not been fixed (https://community.adobe.com/t5/lightroom-classic-bugs/p-white-balance-dropper-target-location-is -offset-on-high-dpi-windows-devices / idi-p / 12250363). Could I get information on how this fix stands, especially since Photoshop doesn't have this problem, for example? I have an ASUS ProArt Studio laptop with a 16 "4K monitor with a 250% monitor setting.

Lightroom Classic 13.3 adds tethering support for selected recent Sony cameras, including the A7 IV. However, I cannot get tethering to work with a USB-C connected Sony A7 IV (3.01 firmware) on my Windows 11 computer; I get a "Detecting Camera" dialog with a spinning wheel, but no further. The same camera, cable and camera settings work correctly in the Remote part of Sony Imaging Edge.

W tym oknie jest błąd w tłumaczeniu na język polski. Powinno pisać “Usuwanie kurzu” a nie Dust Removal 

Issue: The Point Color functionality has stopped working post upgrade.Steps to reproduce: Mask an area of the image, then go to Point Color under the mask adjustment section, click the dropper icon and then move the cursor to the image. At that point the dropper icon vanishes (as soon as the cursor moves over the image). [I can’t select any colour/area within the mask.I can see previous colours I have selected prior to the upgrade within the Point Color settings and can manipulate them.Expected result: when clicking the dropper icon, I should be able to move to my mask and select a colour to then manipulate. The dropper icon should still visible when moving my cursor across the image. Camera model: Sony FE 24-70 GMIISystem info:Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11Version: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.8GHzSqLite Versi

Creating a develop preset with Remove selected but no Remove commands applied to the photo appears to succeed.  A .xmp file is created, but the preset doesn’t appear in the Presets panel. To reproduce on LR 15.2 / Mac OS 26.2: 1. Open a photo in Develop and click Reset. 2. Create a preset named “_remove”, with just Remove, Reflections, People, and Dust checked.  Observe that no error is displayed but “_remove” doesn’t appear in the Presets panel, though the file “_remove.xmp” appears in the Settings folder. 

In LR 15.2, Help > Map Module Shortcuts shows the wrong keys for Show Filter Bar in these four languages: Language Shown Should Be DE \ < ES \ , FR \ $ SV \ ,  

The entries for the keyboard shortcuts for assigning the Purple color label were omitted from the TranslatedStrings.txt files in LR 15.2:"$$$/AgLibrary/Menu/Photo/Label/Toggle5AndNextShortcut=""$$$/AgLibrary/Menu/Photo/Label/Toggle5Shortcut="These entries are defined for English (in LibraryLabels.lua). The entries appeared in TranslatedStrings in previous versions of LR: 

I unselected the “Enable hover preview of presets, history and snaphots in Loupe” option in the preferences but even though it is turned off, it is still previewing in case of hovering the mouse over any history state of snapshot. It doesn’t do the preview on the presets, but it is still previews the history and snapshots which it is not supposed to do, because the option is purposely turned off.Lightroo Classic 15.2

[Adobe doesn't accept bug reports of LR 14 on Mac OS 26, so I'm posting this here to inform other plugin developers and users and perhaps Adobe developers, if they're interested.] Plugins sometimes crash LR 14.5.1 with Mac OS 26.0 on Apple Silicon Macs when they try to run a child program using LrTasks.execute(), with the error in the crash log, "crashed on child side of fork pre-exec".  If this bug continues with LR 15 (officially supported on Mac OS 26), it could have a serious impact on many plugins. A similar bug occurred a year ago starting with LR 13.5, on just Intel Macs, and wasn't fixed until 14.5. Adobe's fix was suboptimal, serializing all invocations of LrTasks.execute(), creating a real performance hit for plugins that invoked multiple instances of programs in parallel (e.g. Exiftool). A better fix would have been to serialize the lower-level invocations of the operating system's fork/exec system calls, which would still allow multiple instances of LrTa

I made a virtual copy of an image in LR and then chose “edit a copy in PS with lightroom adjustments”. When I sent the image back to LRc, there was no copy made and the new image overwrote the .TIF file original. My original (with Google AI adjustments that cannot be replicated ‘cuz I’m out of usage tokens) is ** COMPLETELY GONE **. I am quite beyond irritated. Yes, I still have the pre-Google raw file, but I am very much not happy. What should I have done? P.S. aside -- why would my community page not have a “post a question” button on it? I’ve been hunting around for over an hour and it only just now showed up.

Save Metadata To File will unnecessarily write a huge .acr sidecar for a JPEG that’s been exported from LR and reimported. This affects users who regularly export with the Add To Catalog option. See here for a motivating use case:https://www.lightroomqueen.com/community/threads/exported-jpgs-with-an-acr-file.54565/ To reproduce  on LR 15.2.1 / Mac OS 26.2: 1. Download and open the attached catalog, which contains a single raw, DSC08981.ARW, with Denoise applied. 2. Ensure the option Catalog Settings > Metadata > Include Develop Settings In Metadata is enabled (the default). 3. Select the raw and export it as a JPEG to the desktop, with Quality = 70 and the option Metadata > Include: All Metadata. 4. Import the exported JPEG with the Add Option. 5. Select the JPEG and do Metadata > Save Metadata To File. Observe that DSC08981.acr is created, about 10.3 MB (three times the size of the .jpg) (incorrect). 6. Delete DSC08981.acr from the desktop. 7. Edit DSC0891.jpg in Develop a