Bug Reports

When viewing a film strip which is filtered to only show flagged image if I click on the flag to "unpick" the selected image and then click on the next image that image is also unpicked. It's a little complicated to explain but the attached video shows it happening and it's very easy to duplicate using these steps:Set the pick flag on multiple imagesGo to Develop Filter only so only images with the flag are displayedSelect an imageClick the flag on the thumbnail to remove it from the filtered listQuickly click on another thumbnailA second image will be removed (UNDO will return it)It seems like the time it takes for the preview for the next image that's automatically displayed when the last image is filtered out is the window for when a click on a thumbnail means the 2nd image will also lose it's flag.I believe it's a bug, it's been happening for quite a few versions now but I've posted in discussion as per the preferred method of reporting. It's become more apparent and annoying in 14

Typing into the year field in the Edit Capture Time dialog is too fussy, making it difficult for people who are slow typists (hunt-and-peck or disabled) to enter the year. If you type just a little slowly, then after 1-3 digits, the dialog thinks you've finished entering a year, and the next digit you type will erase the previous ones. Screen recording: https://www.dropbox.com/s/ks09r4f5847zwx0/capture-time-digits.2019.04.05.mov?dl=0A perhaps related problem was reported fixed back in 2015.4, though it had somewhat different symptoms. Another user just wasted a bunch of time tripping over this:https://forums.adobe.com/message/11010712#11010712The fix should be trivial: the timeout for entering digits just needs to be increased a fair bit.Tested on LR 8.2 / Mac OS 10.14.3.

Invoking the Library Filter bar’s Restore Default Presets creates duplicates of the built-in filter presets.   To reproduce in LR 15.2 / Mac OS 26.2: 1. Set the option Preferences > Presets > Store Presets With This Catalog. 2. Open the attached catalog “filter-presets-bug”. 3. In the Library Filter bar, click the drop-down menu and do Restore Default Presets. Observe that the built-in presets Default Columns, Filters Off, and Location Columns have been duplicated.  Examining those presets’ .lrtemplate files, the contents of the duplicates are identical. Before and after of the drop-down menu: 

Same  Problme  help me, please

When closing LightRoom Classic, this application creates a bakckup file. Sometimes, it does work ...Two cases1) backup stored on internal disk (APFS format) : OKThe zip file contains 2 elements : the catalog, a file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data 2) backup stored on an external disk ‘SSD disk as Sandisk Extrem Pro or hard disk as La Cie USB 3) (ExFAT format) : WRONGThe zip file contains 4 elements : a catalog file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data 2 additional fles (temp files) Photos 2022 et +.lrcat-shm et Photos 2022 et +.lrcat-wal  At end of closure operation, catalog folder is correct : a file named Photos 2022 et + Helper.lrdata, a file named Photos 2022 et + Previews.lrdata, a catalog file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data  Informations systèmeNom du modèle : Mac miniPuce : Apple M4  - Mémoire : 24 Go Informations sur le logiciel LightRoom ClassicVersion Lightroom 

After upgrading to v15.2, the Library Filters cannot be enabled. Clicking the Library menu ‘Enable Filters’ will just give Library Filters Off each time is it clicked. The check mark remains on the Enable Filters menu. Using the hotkey Ctrl-L  does not work either, just keep saying Library Filters Off. No way to enable the Library Filters. I have also restarted my Windows 11, and still cannot enable Library Filters.

LR fails to normalize the Unicode text of keyword names and allows the creation of two keywords that are canonically equivalent, with the same appearance and meaning under the Unicode standard. To reproduce on LR 15.2 / Mac OS 26.2: 1. Open the attached file “keywords.txt” in a Unicode-compliant text editor (e.g. Textedit or Notepad). 2. In LR’s Keyword List panel, click + to create a keyword, and copy/paste the first line from the file into the keyword’s name. 3. Repeat for the second line of the file. 4. Observe there are two keywords with the same name, as defined by the Unicode standard: The two lines of the text file use different canonically equivalent Unicode representations for the same letter: U+00F6 (LATIN SMALL LETTER O WITH DIAERESIS)U+006F (LATIN SMALL LETTER O) + U+0308 (COMBINING DIAERESIS) Such keywords tripped up this user’s catalog upgrade from LR 14 to LR 15:In that case, we were unable to construct a test case that failed other than on his computer. There is a simil

LR 15.0.1 / Windows incorrectly rounds a capture date/time of 11/13/25 10:30:03.99974 PM to 1/1/1601 4:00:00.477 PM.  But LR 15.0.1 / Mac correctly rounds it to 11/13/25 10:30:04.000 PM.   Tested on LR 15.0.1 / Windows 11 Intel, Windows 11 ARM, and Mac OS 15.7.1. To reproduce:   1. Download and open this catalog: https://www.dropbox.com/scl/fi/3psajur7hfth6ezly98vk/subsec-bug.2025-11-18.zip?rlkey=e3ww25awh8wf3rmrf1nr6x8am&dl=0   It contains two photos with these capture date/times: subsec.dng: 2025:11:13 22:30:03.99974 subsec-smaller.dng: 2025:11:13 22:30:03.99900   2. Right-click the folder "pics" and do Synchronize Folder.   3. On Mac, observe the capture/date times of the two photos have been rounded correctly:   But on Windows 11, observe that the capture time of "subsec.dng" has been mangled to 1/1/1601 4:00:00.477:    

I start with an edited version (lightroom adjustments only) of a photo in lightroom. I make a copy of it and then click reset on the new copy. This copy is essentially no modifications at this point. I then edit that copy in photoshop. When I am done editing in PS, I save it. I then open that PS-modified version in lightroom and paste ALL settings I have copied from the original to this new TIFF version. I expect the changes to work but it looks wrong. I notice the REMOVED tool item masks are strange. It looks like the REMOVE masks in the version that I pasted to are 90 degrees rotated - clockwise. Basically, copy/paste of masks does not work from a raw file to a tiff version. It’s like PS messed up the orientation indicator or something and LR got confused?

Upgraded to 11.3 this morning. 11.2 and previous worked without problems.   I notice the following: Using the hand tool to reposition the image within the print frame: Up and down are reversed.    For example I am printing a photo of a model on white background. If I reposition the photo so that the model is in the center of the frame I have to click and drag the image in the opposite direction to which I want the image to move.    So with the model in the center of the frame and with ample padding around the image the print comes out with her toes cut off????    If I then reposition the image on screen so that the models toes are cut off the print comes out with the model centered nicely with ample padding around the image!!!!   Richard

[This bug report was originally posted on 1/26/2019 in the old feedback forum, but it never got transferred here. See the attached email message.]   In LR 14.3.1 / Windows 11, when LR is in  Window > Screen Mode > Full Screen, floating dialogs always appear hidden in back of the main LR window, and calling the toFront() function has no effect. This prevents my Any Crop and Any Filter plugins from being used in Full Screen mode. This doesn't occur in the other screen modes, nor does it occur on Mac OS 15.5.   This simple plugin demonstrates the bug:https://www.dropbox.com/s/6d1l3llo5dwzzuw/floatingfullscreenbug.lrdevplugin.zip?dl=0 Simply invoke Library > Plug-in Extras > Floating Dialog in the various Screen Modes. The command executes this simple code: LrDialogs.presentFloatingDialog (_PLUGIN, { title = "Floating Fullscreen Bug", contents = f:push_button {title = "Push Me"}, onShow = showErrors (function (t) LrTasks.startAsyncTask (s

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

Hello: I just updated to the 15.0 release and I think I just discovered a bug. When I click Edit Capture Time via the Metadata tab, whatever time I enter is one hour off from the time that shows up in the EXIF data panel (and how it sorts the photo if "Capture Time" is used to sort the library); therefore to get the EXIF information to show up correctly, I must purposely enter the information one hour behind the time I want it to be (see screenshot where I want 5:31pm to be the edited time, but I must enter 4:31pm to get 5:31pm).  -- Scott, MacBook Pro, Apple M3 Pro chip, macOS Sequoia 15.6.1.

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 calling the LrApplication.addDevelopPresetForPlugin with the settings below, which don't include any white balance settings, the temp is adjusted to 2000 and Tint to 150.local photoPresetTable = { Exposure2012 = -0.43, Whites2012 = 2}Full code examplelocal LrDialogs = import 'LrDialogs'local LrTasks = import 'LrTasks'local LrFunctionContext = import 'LrFunctionContext'local LrApplication = import 'LrApplication'local LrFileUtils = import 'LrFileUtils'LrFunctionContext.postAsyncTaskWithContext("Test apply preset", function(context) LrDialogs.attachErrorDialogToFunctionContext(context) local catalog = LrApplication.activeCatalog() local activePhoto = catalog:getTargetPhoto() -- Create preset local photoPresetTable = { Exposure2012 = -0.43, Whites2012 = 2 } local newPhotoPreset = LrApplication.addDevelopPresetForPlugin(_PLUGIN, "Test preset", photoPresetTable) -- Apply preset catalog:withWriteAccessDo("Apply preset", function() activePhoto:applyDevelopPreset(newPhotoPreset, _PLUGI

OS: Windows 11LrC VERSION: 14.5A couple of days ago I upgrade to v14.5.As for every update, I regurlay empty cache, optimise catalog, remove all previews and generate new standard ones (also, I wanted to test how was was the new option to use GPU for generating previews).Never had a problem with this workflow.After previews generation process was completed (1h 30m for 29.000 files, 23.000 jpegs and 6.000 raws) I got an error: for 21 RAWs the preview could not be generated. Looking in the catalog at those files, I realised they have an exclamation mark on a dark circle: this is not the missing photo mark. If I click on the exclamation mark, I see error "Lightroom has encountered problems reading this photo, you are not allowed to edit this image. " Yet, I can still enter develop module and edit the photos without any problem: the editing history is there, I can zoom in at 100% (generating the 1:1 preview), I can change sliders, export... Everything... (PS: I do not use smart previe

catalog:getCurrentViewFilter() doesn't report the new Stack options in Library Filter's Attribute bar.  This affects the popular commands Back To Previous and Forward To Next Source/Filter/Selection of my Any Source plugin.   When this is fixed, be sure to test catalog:setViewFilter() as well.   To reproduce on LR 15.0 / Mac OS 15.7.1, run my Debugging Toolkit's Debug Script command:    

Lightroom Classic crashes when backing up catalog and looking at preferences, and doing an integrity check. I'm running Lightroom Classic on a new MAC with Sonoma and I've recently upgraded all my external hard drives.  I'm a photographer for the USA Today and have an enormous catalog. My crash report header is below - the full report is beyond enornmous. My catalog is over 4 gig. Lightroom Classic crashes during the integrity check. I've reset preferenes during startup.   I've uninstalled Lightroom today and reinstalled the latest from Adobe CC.   Neither of those options have helped.  I've tried backing up my catalog to 3 other external hard drives and also to the local MAC hard disk - no luck and no success with any of that. Restart, Reboot - nothing works.   Help, please.   -------------------------------------Translated Report (Full Report Below)------------------------------------- Process: Adobe Lightroom Classic [694]Path: /Applications/Adobe Light

I have a Macbook Pro M4 Pro chip, using MacOS Sequoia 15.5 with 48GB of memory. I am using version 14.4 of Lightroom classic with Camera Raw 17.4. My Lightroom keeps crashing, with no particular pattern that I can pick up.   Is there any fix or anything I can do to resolve the issue? Your help would be appreciated.

Windows 11 21H2   If you shut down Lightroom Classic 11.3.1 with the Library Module showing, then re-launch later, the Map Module works fine.   If you shut down Lightroom Classic 11.3.1 with the Map Module showing, and then re-launch later, the Map Module is not usable. The exact form of the error changes, its not always the same, sometimes I get JavaScript error, sometimes the Map Module just freezes, other times it has other errors, but the Map Module simply doesn't work in this situation.

I just updated my LrC to v 12.4 this morning and now when I try to copy/paste settings in the develop tab to a new photo, the new photo is hazed out and flat looking. If I reset the settings and put them in manually, it looks correct, so it has to be an issue with the copy/paste. Please help this is slowing down my work flow tremendously.   PC, Windows 10

When a video is exported from Lightroom Classic that does not have the size 1920x1080 pixels, it is scaled down. Videos that are in portrait format (1080x1920 pixels) are scaled to 960x540 pixels. A video with 1440x1080 pixels becomes 1280x720 pixels when exported. Do not scale videos during export.  

Description: Lightroom Classic (v15.1.1) is experiencing a terminal hang (Beachball) immediately upon launch on macOS Tahoe 26.2. The application only functions when the system is completely offline.This is NOT a catalog or hardware issue. It occurs even with a brand-new empty catalog and with the sync engine paused.System Specs: Model: Mac mini (Mac14,12) Processor: Apple M2 Pro Memory: 32 GB RAM OS: macOS Tahoe 26.2 (Build 25C56) Architecture: arm64e Troubleshooting performed (All unsuccessful): Multiple Preference Resets: Reset preferences on launch and via manual deletion of PLIST files. Adobe Clean Removal & Reinstall: Used the official Adobe CC Cleaner Tool to wipe all Adobe products and folders (including ~/Library/Application Support/Adobe), followed by a fresh reinstall of the Creative Cloud Desktop app and LrC. Standard Troubleshooting: Followed all official Adobe "Basic troubleshooting steps" (checked file permissions, etc.). Network Diagnosis: Verified /et

Windows LR doesn't correctly open a catalog folder exported with Mac LR with File > Export As Catalog, Export Negative Files, if the Mac catalog folder contains subfolders with non-ASCII characters (e.g. á or é). To reproduce on LR 14.2 / Mac OS 15.2, Windows 11:   1. Download this .zip file containing a catalog and photos to your Mac desktop: https://www.dropbox.com/scl/fi/stbx8iyfekqk9xkuri3fi/accents.2025-02-14.zip?rlkey=xt283tc32rjarroeu4bz90jlh&dl=0   It contains a catalog created with Mac LR by doing FIle > Export As Catalog, Export Negative Files.   2. Unzip and open that catalog in Mac LR. Observe that it contains four photos in two folders and none of the folders or photos are marked missing:   2. Download the .zip file to your Windows desktop.   3. Unzip the .zip using these exact commands:   cd Desktop tar xfzv accents.2025-02-14.zip   Do not use the Windows ZIP built-in to File Explorer. It still doesn't correctly handle paths c

Hallo,   trotz aktueller Version 14.2 funktioniert bei mir in LightroomClassic seit mehreren Tagen das Kartenmodul nicht. Ich bitte um Hilfe bzw. Aufklärung!