Bug Reports

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.

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

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

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.

Lr Classic 15.0.1 macOS 26.1   Steps: 1: Enter Develop mode for Photo A 2: Click Copy... to copy settings 3: Select all settings.... but uncheck Crop 4: Go to Photo B and paste settings (if prompted select either Merge or Replace... it doesn't affect reproducibility)   Results: I see the crop was applied to Photo B even though crop was not selected when pasting. I didn't test this for other combinations of settings but perhaps others here might have other occurences of their own.

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.

W tłumaczniu na język poski znalazłem nastepujące błęd: Pokaż wskaźniki przycinania powinno być Pokaż wskaźniki prześwietleń i niedoświetleńPokaż opcję Obcięcie, gdy mysz jest nad wskaźnikiem powinno być Pokaż ostrzeżenia, gdy mysz jest nad wskaźnikiemUkryj obcięcie światła powinno być Ukryj ostrzeżenia o prześwietleniachUkryj obcięcie cienia powinno być Ukryj ostrzeżenia o niedoświetleniachPokaż obcięcie światła powinno być Pokaż ostrzeżenia o prześwietleniachPokaż obcięcie cienia powinno być Pokaż ostrzeżenia o niedoświetleniachPokaż obcięcie powinno być Pokaż prześwietlenia i niedoświetlenia   Profil Adaptacyjna powinno być Adaptacyjny

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. 

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

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

Issue:List of camera models and their associalted raw standards shows only 6 entries without scrolling. A scrollbar is only added after 8 entries. The last entry does not apper in the list. Versions:Lightroom Classic Version 15.2.1. Camera Raw 18.2.2. .OS Windows 11 Pro, 25H2, Build 26200.8037, German DE-DE To reproduce:Create 6 Raw Standards for different camera models. They appear all in the list. Add a 7th Raw Standard for a new camera model. They last entry ist not shown. No scrollbar abailable. Add a 8th Raw Standard for a new camera model. The scrollbar is available. The last entry is missing.Note: The list ist sorted alphabetically.

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.

When Rename Photo is applied to a virtual copy, the Example line in the dialog uses the virtual copy’s metadata, but the actual rename uses the original’s metadata.  They should both use either the virtual copy’s metadata or the original’s metadata. (I think it’s more useful and less confusing for the actual rename to use the virtual copy’s metadata, but assuming the current behavior is “as designed” rather than “as coded”, then the Example line should be fixed to use the original’s metadata.) To reproduce on LR 15.2.1 / Mac OS 26.2: 1. Download and open the attached tiny catalog. It contains the original x.jpg and a virtual copy of x.jpg.  All the editable metadata fields of the original contain “j” (for JPEG) or the number 1, while those fields of the virtual copy contain “v” (for virtual copy) or the number 2. 2. Select the virtual copy and do Library > Rename Photo. 3. Edit the template to contain just the token Title. Observe that Example: says “v.jpg” (since the virtual copy’s

Issue: When I save metadata from Lightroom Classic via "Save Metadata to File", I lose subsecond EXIF metadata that was originally there in the file. This is new behavior, did not happen in previous versions (though I'm not sure exactly when it started).   Lightroom Classic version: 13.5 [ 202408062022-6258095b ] System version: macOS 13.6.9   To reproduce:   1) Import a photo that has a subsecond creation date—for my test, I used an iPhone photo imported via mobile sync.   2) Check SubSecTimeOriginal from the command line: $ -> exiftool -G -s -SubSecTimeOriginal /Volumes/Media/Photos/Import/Mobile\ Import/IMG_6067.HEIC  [EXIF]          SubSecTimeOriginal              : 389   3) In LrC, run the "Save Metdata to File" command   4) Check SubSecTimeOriginal from the command line: $ -> exiftool -G -s -SubSecTimeOriginal /Volumes/Media/Photos/Import/Mobile\ Import/IMG_6067.HEIC  Warning

1. Platform and Version Lightroom Classic version: 15.2.1 OS: Windows 11 Pro 2. System Environment (Multi-monitor & Scaling) Display Setup: 4 monitors (Mainly using two 2560x1440 and one 1920x1080). Windows Scaling: All monitors set to 125% scaling. GPU: NVIDIA GeForce RTX 4070 Ti [cite: 2026-02-02]. 3. Steps to reproduce Open Lightroom Classic on a multi-monitor system with Windows Scaling set to 125%. Enable the Secondary Display (F11) in Full Screen mode on any additional monitor. In either the Library or Develop module, cycle through the "Lights Out" modes by pressing the 'L' key (Lights On > Dim > Lights Off). 4. Expected result The UI should dim (Lights Dim) or turn black (Lights Off) on all monitors, while keeping the image/grid area fully visible and unaffected by the dimming layer. 5. Actual result The dimming behavior is erratic and inconsistent: Total Blackout: Frequently, the photo area itself is dimmed or completely blacked out on either the main or sec

When you change the year in Metadata > Edit Capture Time to before 2001, the milliseconds goes negative and one is added to whatever value you enter for seconds.  This is likely related to the Cocoa timestamp epoch of 1/1/2001.  If instead you change the year to 2018, the milliseconds gets decremented by one (also incorrect). To reproduce on LR 15.2 / Mac OS 26.2: 1. Open the attached tiny catalog. 2. Select the photo and do Metadata > Edit Capture Time. 3. Click in the year and type 2019 (quickly, to avoid another Edit Capture Time bug).  Observe that the milliseconds field stays at 22 (correct). 4. Click cancel, do Edit Capture Time, click in the year, and type 2018. Observe that the milliseconds field gets changed to 21 (incorrect) 5. Click cancel, do Edit Capture Time, click in the year, and type 2001. Observe that the milliseconds field gets changed to 21 (incorrect). 6. Click cancel, do Edit Capture Time, click in the year, and type 2000. Observe that the milliseconds field