Bug Reports

I noticed after updating my new v10 converted catalog that LrC was acting slow in the Library module, so I disengaged the usual culprit for this, the "Automatically write changes into XMP" setting. Then to my dismay, I noticed that it proceeded to mark the majority of the photos in the current grid view as needing a metadata update, even though the catalog metadata was fully saved to XMP prior to the upgrade, as far as I was aware.   Then I paged down, and the pattern repeated: Lightroom scanned all the now-visible photos and found that almost all of them also needed to be updated on disk.   And I did it again. And again.   Eventually I wrote a script to send "Page Down" events to the program periodically to ensure that Lightroom looked at every photo in the catalog, then let it run overnight with the library filter set to "Metadata Status = Up to date", so that it would give me the list of photos that need no metadata update. The next morning, I scrolled the grid back u

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.

Hi,after the latest update to v15 of LR for Windows, the behaviour of the cropping tool changed. It's really annoying: It is very difficult to create a selection in portrait format with the mouse in this case. Simply dragging diagonally downwards is no longer sufficient – see my screen video here:https://youtu.be/NYfgYOV3IXE Any idea to get back the old behaviour – not by using the previous version of LR 😉 Thanks!mycc

Lightroom Classic 15.5.1 and prior versions. Using MacOS, but I doubt that matters for this bug.When using the Dust removal tool (in the Distraction Removal panel), if you rapidly add dust removal spots, the “Removing New Dust Spot...” dialog will stick and not disappear even after LR has finished adding the spot.Steps to reproduce:Enable Dust removal. Start rapidly clicking multiple spots, without giving each time to complete. The busy dialog will popup, timeout, but fail to dismiss automatically. Manually press Cancel to dismiss it yourself.

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?

When using the color grading panel the numerical fields for the Hue and Sat input behave erratically. When moving the Hue slider sometimes the last digit disappears. This happens with single Color Wheel interface. So instead if displaying 235 the field displays 23. It shows this behavior with various value: 231 shows 231, but 220 shows 22. You can check this  when displaying all 3 color wheels simultaneously. The hue values in both image is 235.Lightroom classic is showing this behavior since the last update, 15.6 release. This seems like a bug. I have tried resetting everything to the default settings but that doesn't make any difference.When I edit the same photo in Photoshop Camera Raw, Color Grading behaves as expected.

In Lightroom Classic, after I created a new catalog, the file originally displayed the correct LrC logo. However, the logo has now disappeared and is no longer showing on the file icon. Tried all neassary process but not working.

Auto updated to LrC 15.5 on my MacBook Pro M3 Max last night. Came home from shooting a concert and the import dialogue would appear to function normally, but after hitting the actual button to import, nothing happened. It went back to the grid view, briefly the import status bar appeared in the top left then just as quickly disappeared. I tried different ways of doing it, enabling full disk access (already was set), copy vs convert to dng, even created a whole new catalog and did a hard reset on my computer. Same issue every time. Decided to downgrade to 15.4.1 through the creative cloud as I was able to recently import and edit on that version. Opened Lightroom back up and viola, everything worked just fine. Gonna stick on this version and disable automatic updates until I hear adobe fixes this.

自動補正を全体にかけハイライトやコントラス、彩度などの項目ごとの設定を同期するとチェックしていない項目がリセットされて0となってしまいます。   11.3.1のみこの状態となっており11.3では問題なく同期できました。

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.  

This has been happening for probably a week or two. I have it by default apply content credentials to every jpg I export - can’t hurt, right?In every single export lately, a random number of them ‘fail to apply’ and hence do not export at all. I have to keep going to the export dialog, click ‘skip’, and it will export a few more and fail to export a random number. Currently I have done this 8 times to a set of 148, and am down to one single file that it just doesn’t seem to want to apply them to ever. I assume this is a bug and I should give up on credentials until this is fixed.  Mac Mini M4 Pro, OS 26.5.2 

When a video is exported from Lightroom Classic, the “Capture Date” (CreateDate or DateTimeDigitized) is overwritten with the time of the export. However, the “Capture Date” must not be changed during export. It works when exporting photos.

SummaryLandscape AI masking in Lightroom Classic 15.5/15.5.1 progressively becomes extremely slow during normal use on my system.Immediately after a Windows reboot, a Landscape mask typically completes in approximately 6–7 seconds. After continued Lightroom use, the same operation on comparable images can take 60–90+ seconds.I captured a controlled example in Lightroom Classic 15.5.1:Degraded state before Windows reboot: 86.68 secondsNormal state immediately after Windows reboot: 6.51 secondsThis represents approximately a 13.3× slowdown.Restarting Lightroom does not consistently restore normal performance. Rebooting Windows restores the fast Landscape masking performance.The problem appears specific to, or particularly severe with, Landscape AI masking. Other AI masks such as Sky and Subject do not exhibit the same degree of degradation in my testing.System ConfigurationOperating System: Windows 11CPU: Intel Core i9-14900KRAM: 64 GBGPU: AMD Radeon RX 9070, 16 GB dedicated VRAMAMD driv

Hi everyone,I'm having an issue with the latest version of Lightroom CC on a MacBook M5 Pro running macOS Tahoe 26.5.1. (I was experiencing the same problem on 26.5 and decided to update hoping it would fix it, but unfortunately it didn't.)Since this morning, it's been impossible to to use Noise Reduction, even though my internet connection is working perfectly. I've already updated both Lightroom CC and macOS, cleared the cache, and optimized the catalog, but I keep getting this error screen whenever I try to use Noise Reduction.Has anyone experienced the same issue or knows how to fix it? Any help would be greatly appreciated. Thanks! 🙏 

Exporting a portrait video at Quality: Max (up to 4K) chooses a target resolution that is much less than 4K, with a lower frame rate than the source. To reproduce on LR 15.5.1 / Mac OS 26.6.2: 1. Open the attached catalog. 2. Select the video Portrait.mov and do File > Export. 3. In the Video section, select Quality: Max (up to 4K) and observe that the Source resolution is 2160 x 3840, 60 FPS (correct), but the target resolution is 1920 x 1080, 30 FPS (incorrect) -- it should be 3840 x 2160 (or similar horizontal 4K resolution), 60 FPS:  4. Do the export and observe that the resolution of the output is indeed 1920 x 1080, 30 FPS (incorrect), with the portrait video inserted as letterbox (black borders on the left and right).  The exported video should be 3840 x 2160, 60 FPS (or similar horizontal 4K resolution), with the video inserted as letterbox. 5. Select Landscape.mp4 and export it with Quality: Max, and observe the Source resolution is 3840 x 2160, 60 FPS and the Target resolu

In LrC, German version 15.5.1, Camera Raw 18.5.1, the tool tip for “Punktfarbe”, “Hue Range”, the lower triangle, says “Geringere Abfallkante”. I presume the tool tip in the English version is something like “lower edge”, “lower threshold” or “lower limit” or “lower ramp”. In any case, you would not translate “lower” into “geringer” in such a situation. You would use “Untere” instead, which matches “Obere” for the upper end. Geringer would translate to smaller or less in this context, in the sense of “not as high as something else”, which is arguabely not what you want to say. Note that my mother tonge is German and I am an electrical engineer. Feel free to contact me if you need further input or insight at <Email redacted by Mod> Kind regards, Markus

I am a photojournalist and recently switched from a PC to a MacBook (last week). My workflow has been rock-solid for many years, and my old archive copied over to the new Mac system without any issues.My Workflow: Preview & Culling: Photo Mechanic Editing: Photoshop 27.9.1 / Adobe Camera Raw Saving: Exported/saved as DNG files Archiving: Import DNGs into Lightroom Classic 15.5.1 The Issue: For my commercial side work, I regularly apply the "Adaptive: Color" profile to my Raw files. However, since switching to the Mac, when I import these newly edited DNGs into Lightroom Classic, LrC fails to apply or read the "Adaptive: Color" profile. The images import looking completely flat.What I've Tried: I read that updating the AI settings in Lightroom might resolve this, but it did not work. Manually reapplying the Adaptive Color profile inside Lightroom does fix the image, but this is way too time-consuming and defeats the purpose of my workflow. Note: Older images processed this

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

When I try to import picture files, I get a popup for assisted culling that locks the application. I need to go to task manager to shut down the application.   I turned off assisted culling under catalog settings, but this does not correct the issue. Is anybody else experiencing this issue. I cannot import new files!  

LRC 15.3Windows 11 Step to reproduceConfigure auto import. Don’t rename and don’t apply any preset. Keep is simple  Auto import settings  Copy a photo in the auto import folder. The photo is imported automaticly Launch a normal import with the "don’t import suspected duplicates" box checked Point to the initial folder were the photo was (not the auto-import one) The photo that is already in the catalog is not greyed. You can reimport it and create a duplicate even if you ask to avoid duplicates. Kind regards

If a plugin calls catalog:updateAISettings() immediately after photo:applyDevelopPreset(), the application of the preset is ignored. This bug was introduced in LR 15.3, likely with the background processing of AI commands. To reproduce on LR 15.3 / Mac OS 26.4.1: 1. Import the attached preset “_Update Bug.xmp”. 2. Put the attached file “updateaisettings-bug.txt” into the LR Scripts folder. 3. Go to Develop with a test photo. 4. Do Scripts > updateaisettings-bug. Observe that Exposure is not changed (incorrect -- it should change to 4). 5. Apply the preset “_Update Bug”. Observe that Exposure changes to 4 (correct). A workaround is to call LrTasks.sleep (0.1) before calling catalog:updateAISettings().

I have many video files imported into LrC that I want to modify the filename.  The video files were taken with the iPhone 17 Pro.  My usual method to edit the filename is to edit the filename entry in the metadata panel.  When I use the method I get an error message that the filename cannot be edited.  If I use the alternate method of using the F2 key, I get the same error message.  I have submitted another bug report about not being able to import video files into LrC 15.5.  That bug report has been “Acknowledged”.  In that case reverting to v15.4 allows imports. Unfortunately reverting to v15.4 does not fix this issue. 

As the title says, if I go to the develop module in lightroom, click on the removal tool then go down to distractions and click apply on the reflections section I can’t then send the photo to photoshop. If I send it to photoshop it opens up the photoshop app but just gives me the home screen as shown and doesn’t open the photo.   

What an awful release. Don't get me wrong, I'm glad to see new developments, but this Lightroom update is an absolute disaster. After culling just 5-10 images, the AI Assist culling tool completely hogs all my RAM, causing my Mac to freeze and throw memory errors. It’s a total nightmare.Culling images via the library module is practically impossible right now - everything just locks up. Even with previews pre-generated and trying to run AI Assist culling, the performance is still abysmal. On top of that, it frequently fails to even generate a Denoise. What is going on, Adobe?! This is absolutely unacceptable!P.S. The RAM management is completely broken and goes beyond any acceptable limits!  

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.