Bug Reports

The new Metadata panel field Last Exported Date isn't formatted with the correct localized date format:     Tested in LR 13.2 / Mac OS 14.4.1.  

In LR 13.3, the History panel still uses pre-LR 13.3 terminology, referring to the tool as "Heal" rather than "Remove".  Here's a screenshot showing the application of all the different Remove modes with and without Generative AI and Object Aware, and then deleting them: Remove, selecting Generative AI, Remove Object Aware, Remove Generative AI + Object Aware, Heal, Clone.     The History steps also refer to "Gen. Remove", though the Remove panel uses the term "Generative AI". In general, the terminology is ambiguous and confusing, e.g. using "Remove" to name both the panel/tool and one of the modes, so being precise will at least reduce confusion a little.   There may be other History steps still using the old terminology -- I didn't do an exhaustive search.  

Using the Hour file-renaming token results in an internal error when LR is running in Polish or Russian. To reproduce on LR 13.3.1:   1. Set Preferences > General > Language to Polski and restart LR.   2. In Library, select a photo and do F2 (Rename Photo).   3. In the File Naming drop-down, select Edit (the last menu item).   4. Create the renaming template "Data (RRRRMMDD) - Godzina" (Godzina is Hour in Polish):   5. Click OK twice, and observe this error:   Translation: Internal error. AgDate.formatDatelnUserFormat: %W specifier not yet implemented.   6. Repeat the previous steps for Russian:   and observe this internal error:   * * *   This is a trivial bug to fix. In the corresponding TranslatedStrings files, all the other languages have  /AgNaming/Token/dateEvaluator_Hour set to %H (the Lua date-formatting code for "Hour with leading zero (24-hour clock)"). But the files for Polish and Russian have it set

The tool tip for Remove > Next Variation is garbled in LR 13.4 / Windows running in French:   This is caused by a typo in TranslatedStrings_Lr_fr_FR.txt:     "$$$/AgDevelop/Dust/GenRemove/NextVariation/Shortcut/Win=Alt + ^U + 2192"     It should be:     "$$$/AgDevelop/Dust/GenRemove/NextVariation/Shortcut/Win=Alt + ^U+2192"       Of course, this wouldn't have happened if the tool tip followed the convention used everywhere else in LR, with "Left Arrow" and "Right Arrow" used instead of ←and →, and if the developers used the Any Shortcut plugin to catch errors before release. (There's plenty of room in the tool tips for spelling out Left Arrow and Right Arrow.)

Lightroom Classic 13.0.1   We wszystkich tłumaczeniach występują dwa błędy 1. "Show More Labels” 2. "Use the Point Color Dropper to add samples"  we wszystkich tłumaczeniach te dwa zwrotu są po angielsku  

The Lightroom Classic Keyboard Shortcuts help shows a shortcut for the non-existent command Stack Visually Similar Photos:   https://helpx.adobe.com/lightroom-classic/help/keyboard-shortcuts.html   TranslatedStrings has entries that allude to such a command, but it's never been released (unfortunately!).

Hello,   Issue has only started as-of a few days ago, importing photos causes LR to throw the error message listed below.   Workflow: transfer SD card data to set folder, create new catalog at same location, import photos to catalog via add -> crash   I am running win11 on a very capable machine with no outdated drivers/software -- this is my only issue. Please help if you can! <Deleted Extraneous Information>

Hoping for some help here. I am on a PC and have the latest versions of Photoshop and Lightroom Classic. I wanted to download and try the new Photoshop Beta so I downloaded it from the Adobe Creative Cloud and it installed fine. BUT - when I use Lightroom and choose EDIT IN - ADOBE PHOTOSHOP 2023 it opens the BETA version. It does not give me an option to choose WHICH Photoshop version I want to use. Uninstalling the Beta basically kills the ability to send an image from Lightroom Classic to Photoshop at all and the only way to get things back is to uninstall the beta and then uninstall Photoshop CC 2023 THEN reinstall Photoshop. I'd love to play with the beta and be able to choose which version of Photoshop I want to use when sending images from Lightroom Classic.   I've seen some videos where the option to select which version of photoshop you want to use is selectable from a dropdown menu but this was on a Mac and not a PC. Any help is appreciated! James  

Lightroom Classic keeps freezing then crash. I have a Mac-Catalinia up to date. Lightroom Classic up too date. Tried every trick on the Internet and adobe. This needs to be fix ASAP.   Here is what shows up:     -------------------------------------Translated Report (Full Report Below)------------------------------------- Process: Adobe Lightroom Classic [1818]Path: /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom ClassicIdentifier: com.adobe.LightroomClassicCC7Version: 12.2.1 (12.2.1)Code Type: ARM-64 (Native)Parent Process: launchd [1]User ID: 501 Date/Time: 2023-03-17 15:15:16.1449 -0400OS Version: macOS 13.2.1 (22D68)Report Version: 12Anonymous UUID: 99735EDA-6D65-020B-7919-5D20885270F3 Time Awake Since Boot: 14000 seconds System Integrity Protection: enabled Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000931

Klasa Lightroom 11,3 Windows 10   1. „Twórz” powinien być „Wywoływanie” (Develop) 2. „Woda” powinna być „Akwamaryn” 3. „Adobe Poziom” powinno być „Adobe Krajobraz” (Landscape=Krajobraz) 4. „Adobe Pionowo” powinno być „Adobe Portret” (Portret=Portret) 5. „Pionowa powinna być „Korekta perspektywy” 6. „Szczegół” powinno być „Szczegóły” 7. „Moduł biblioteki i skróty...” powinno być „Skróty moduł biblioteki...” 8. „$$$/AgBezels/KeyRemapping/MacCommand=Polecenie” powinno być „$$$/AgBezels/KeyRemapping/MacCommand=Command” 9. „$$$/AgBezels/KeyRemapping/WinControl=Sterowanie” powinno być „$$$/AgBezels/KeyRemapping/WinControl=Ctrl” 10. „$$$/AgDevelopShortcuts/Create_Virtual_Copy/Key=Polecenie + '” powinno być „$$$/AgDevelopShortcuts/Create_Virtual_Copy/Key=Ctrl + '” 11. „$$$/AgDevelopShortcuts/Rotate_left/Key=Polecenie + [” powinno być „$$$/AgDevelopShortcuts/Rotate_left/Key=Ctrl + [” 12. „$$$/AgDevelopShortcuts/Rotate_left/Key=Polecenie+]” powinno być „$$$/AgDevelopShortcuts/Rotate_left/Ke

Notifications for likes and comments in shared albums (public synced collections) don't appear in LR 13.4 -- there are no yellow badges.  And sorting by Last Comment Time doesn't work.   (A previous report for the lack of badges in LR 13.3 and 13.3.1 is marked as Fixed.)   Here are the steps I took and screenshots of the results:   1.  In LRC, I created a public synced collection "Test Sync" and added four photos to it.   2. In LR Web, I marked the second photo with a like and the third photo with a like and a comment (photos sorted by capture time).   3. After waiting for the sync to LRC complete, the likes and  comment appear in the Comments panel. But there are no yellow badges and the thumbnails are not sorted by Last Comment Time (the second and third photos with likes and comment should sort first and second).  View > View Options > Cell Icons > Thumbnail Badges is enabled, as demonstrated by the GPS badges on the thumbna

I have used Lightroom for years and have always converted RAW files upon import to DNG with upper case file extension. After upgrading to LR CC, however, all of my files are imported and converted to DNG with the lower case .dng extension. Preferences in Edit and Import are still checked to upper case. I still have LR 5.7 installed on my system and it still correctly uses the upper case .DNG file extension, so this is apparently another bug with LR CC. Not a serious issue, but annoying nonetheless.

HelloWhen I switch to the Polish language on my computer, the Quick Develop panel in the Library module doesn't display the small arrows to expand tools. See the attached photo below. When i switch to English language little arrows are visible as you can see below.   on my friend computer little arrows are not visible at all 😞    I hope this will be fixed in the next version 🙂ThanksPaweł Słowikwww.slowik.eu MY LIGHTROOM AND SYSTEM INFO Lightroom Classic version: 13.4 [ 202406181129-60d181b7 ]License: Creative CloudLanguage setting: enOperating system: Mac OS 14Version: 14.5.0 [23F79]Application architecture: arm64Logical processor count: 10Processor speed: NASqLite Version: 3.36.0Power Source: Plugged In, 100%Built-in memory: 16 384,0 MBDedicated GPU memory used by Lightroom: 190,8MB / 10 922,6MB (1%)Real memory available to Lightroom: 16 384,0 MBReal memory used by Lightroom: 913,8 MB (5,5%)Virtual memory used by Lightroom: 413 072,9 MB

Hi there! There is a bug when exporting to JPG but not to TIF Lens Blur applied. One of the masks (color picker) does not work properly when exporting to JPG with lens blur ON. When either LB is off or export to TIFF, mask is working properly LRC 13.4 on Apple Silicon Here is catalog with DNG file with LB and a TIFF copy. In RENDER subfolder is JPG export from DNG with incorrect blue color cast on the cup https://disk.yandex.ru/d/RP-N3ozNJ1idVw

2. Go to Map Module 3. Type City or location name 4. Use mouse to move "map" BEFORE entering (check spelling or whatever reason) 5. Set Metadata popup opens but does not acccept either "Cancel" or " Apply to Selected" buttons.   This results in Lightroom hanging with the only option to end the task from the task manager.   The Crash reporter never appears   I would expect the following in order of preference: 1. Cancel button entry is accepted 2. Apply button is accepted (any entry can be corrected afterwards) 3. The dialogue times out after a period of inactivity - say 1 minute without the cancel or apply button entry detected.   I have a dump file but its 21GB. If you need it, let me know how to split it (max 1GB chunks) and where to upload it LR Classic 13.4 Windows 10 Pro, 2H22OS Build 19045.4651   Steps to reproduce: 1. Select a file/files 2. Go to Map Module 3. Type City or location name 4. Use mouse to move "map" BEFORE entering (check spelling or whatev

After HDR stacking a couple dozen sets of images, CTRL-H (to invoke HDR stacking) switches to opening Outlook. Tried switching around to different functions and images to no avail. Shutting down and restarting Lightroom gets it back. Forgot to try the menu option, next time it happens I'll try that. 

This is a recent, intermittent issue (I've used LR for years, and only seen this recently).  I'm running Lightroom Classic CC release 7.5.  When merging photos to HDR, Lightroom will process the images and at the moment it creates the DNG it sometimes outputs an error "Some save metadata operations were not performed".  It then states "Photos have read only access (1)", and lists the new dng file that was just created.  This also happens occasionally when merging to Panorama.To try to debug this, I made sure that the folder containing all my raw files had no read-only files in it (I did this in the properties pop-up for the folder, clearing the "read-only" attribute box and applying that setting to all files in the folder).  This was done BEFORE any HDR merges were performed.  If there's a read-only file involved, its something LR is creating temporarily during the merge.I also checked the files in question after the error (both the raw images and the new

Lightroom freezes for me right away upon opening. I've sent plenty of crash reports into Adobe but I'm not sure what to do next. Is there guidance somewhere on what to do in this situation?

Since updating to 13.3, I am having several issues. First, almost half of the location data of my 40K catalog (country, city, state, etc.) has been either erased or changed to a variant like México/Mexico. GPS data was lost for 3K images. LR on the cloud has the same missing/wrong data. If I correct them in LR Classic, it reverts to the wrong one. Then it became very sluggish, especially when metadata reading/writing is involved like rating, library filtering, adding keywords, etc. When selecting Lights out mode, it does not work until I rate or edit a photo. Before this version it was instantaneous. Switching to develop mode takes about 3 seconds (it was less than 1 before) and advancing to next image takes 2-3 seconds as well, it does not matter if images are RAW or JPG. I already stopped syncing, optimize the catalog, increased cache to 99GB, deleted sync files, deleted previews, and generated them again, reset preferences, uninstalled, and installed again, removed presets, even tri

The SDK method photo:applyDevelopSettings() truncates the HDR region of tone curves stored in the setting ExtendedToneCurvePV2012. This affects my Copy Settings, Any Crop, and Export LUT plugins, and I'm sure there are many others affected.   1. Download this catalog, which includes two test pics: https://www.dropbox.com/scl/fi/bp4qudliz6x0f2q02boux/extendedtonecurve-bug.2023.10.20.zip?rlkey=7w0y8qtmteiqczlhopo6j240t&dl=0   2. From the catalog folder, install "extendedtonecurve-bug.lua" in the Scripts folder.   3. Open the catalog in LR.   4. Do Scripts > extendedtonecurve-bug, which uses photo:getDevelopSettings() and :applyDevelopSettings() to copy all settings from 1.CR2 to 2.NEF.   5. Observe that the tone curve of 1.CR2 is:   while the tone curve of 2.NEF is truncated in the HDR region:   6. Use the Show Catalog Metadata plugin to see that the ExtendedToneCurvePV2012 setting of 1.CR2 has been truncated in 2.NEF:   1.CR2:   &nbs

Hello,I exported my tags from my major catalog (CSV/txt) . When I import these tags to a new catalog the closing quote sign (if used) is missing. The sign is included in the exported files. It seems that import is removing or ignoring quote sign if it's the last char in a tag. It doesn't matte if I use csv or the txt file for import source.Kind regards

Exporting a photo-merged DNG as a DNG with compatibility Camera Raw 14.0 And Later creates a DNG that can't be opened in either Photoshop Camera Raw or in LR Develop. Tested with LR 13.2 and Camera Raw 16.2 on Mac OS 14.2.1.   1. Open this small catalog: https://www.dropbox.com/s/dzg9nvdz727wgam/merge-export-dng-bug.2024.03.25.zip?dl=0    2. Select both photos and do Photo > Photo Merge > HDR with these settings:   3. Select the merged DNG and Export with these settings:   4. Open the exported DNG in Photoshop and observe the error "The file appears to be damaged":   5. Import the exported DNG into LR, go to Develop, and observe the error, "The image appears to be damaged":   6. Repeat step 3 with Compatibility: Camera Raw 15.3 And Later, and observe the exported DNG opens without error in both Photoshop and LR Develop.    

Hi. Since the introduction of the Polish translation in Lightroom Classic, a certain error has been occurring. When reducing the right panel in the Library module to its minimum size, the photo grid does not expand to fill the panel, leaving a black empty space instead. This problem doesn't seem to affect the functionality per se, but it does hinder the visual experience and workflow within the program. I've recorded a video demonstrating this issue, as I believe it will provide a clearer understanding of the problem at hand. https://youtu.be/iX60-dWp1Rk I'm looking forward to any suggestions or solutions you might have to address this. Your assistance in resolving this would be greatly appreciated. Wishing you a pleasant day.   Have a nice day.Paweł SłowikMY SYSTEM INFO: Lightroom Classic version: 13.2 [ 202402141005-bf1aeb84 ]License: Creative CloudLanguage setting: plOperating system: Mac OS 14Version: 14.3.1 [23D60]Application architecture: arm64Logical proce

Transform settings don't always copy/sync correctly to other photos. To reproduce:1. Download this photo and make a copy of it in the same folder:https://www.dropbox.com/s/dflc03vke3be0zb/transform-bug.2020.02.19.jpg?dl=02. Import both photos.3. Select both photos and go to Develop.4. In the Transform panel, click Auto.5. Click Sync, check only Upright Mode, then Synchronize.6. Observe that the two photos have been transformed slightly differently.7. Reset the develop settings of both photos.8. Repeat steps 4 - 6, but this time check Upright Transforms in Sync.9. Observe that the two photos have been transformed slightly differently.See this thread for the original reports:https://community.adobe.com/t5/lightroom-classic/transform-tool-problems-since-latest-update-in-ligh...Tested in LR 9.2 / Mac OS 10.14.6.

The orientation of DNG embedded JPEG XL files ("PreviewJXL") does not seem to be set correctly. The orientation is set in the metadata, but the JPEG XL specification explicitly states that metadata orientation should be ignored and instead be read from the stream: "The Exif orientation should be ignored by applications; the JPEG XL codestream orientation takes precedence and libjxl will by default apply the correct orientation automatically."  (https://github.com/libjxl/libjxl/blob/b7961e1318634a95c7d689ec340dbad8a42d4ed4/lib/include/jxl/decode.h#L1251) So when viewing a JPEG XL preview file, the orientation is wrong unless it's 0.