Bug Reports

When clicking on a lightroom://plugin.identifier/link when lightroom classic is running, it will call the registered url handler of plugin.identifier. But when lightroom classic is not running and one clicks on the link, lightroom will start up, but not call the url handler.   How to reproduce:   Create a simple plugin:Info.lua:   -- lightroom://com.example.urlhandler/test return { LrPluginName = "URL Handler", VERSION = { major = 1, minor = 0, revision = 0, build = "1" }, LrSdkVersion = 11.0, platforms = {"Windows", "Mac"}, LrToolkitIdentifier = "com.example.urlhandler", LrForceInitPlugin = true, URLHandler = "URLHandler.lua" }     URLHandler.lua:   local LrDialogs = import "LrDialogs" return { URLHandler = function(url) LrDialogs.message("URL Handler", tostring(url), "info") end }     Make a simple index.html with     <a href="lightroom://com.example.u

On Windows, when the user has set Preferences > Interface > Font Size to Large, Larger, or Largest, it's impossible for plugins to properly size large controls and dialogs.  This is because LrSystemInfo.displayInfo() and .appWindowSize() incorrectly return width and height in units of physical pixels, rather than scaled pixels.     On Mac, those functions correctly return scaled pixels, allowing plugins to properly size controls and dialogs.   Most recently tested on LR 11.1 / Mac OS 11.6.2 and Windows 10.   [This bug report is an updated version of the original posted in 2018, which never got copied to this forum: https://feedback-readonly.photoshop.com/conversations/lightroom-classic/lightroom-lrsysteminfodisplayinfo-returns-wrong-units-of-pixels-on-windows/5f5f45ea4b561a3d426790a5    It has been edited somewhat to reflect changes in LR in the past four years.] Details On Mac, you can set a scaling factor for Retina displays via System Pr

When using the keyboard shortcuts "=" or "-" to adjust a Develop slider, an adjustment to another slider with the mouse is incorrectly included in the history step for the first slider.  This doesn't happen when you make the adjustments solely with the mouse.    In a related bug, if you adjust a Develop slider with the shortcut and then quickly click Reset, "Reset" appears as a history step before the slider.   To reproduce in LR 13.0.1 / Mac OS 14.1:   In screen recording tracking1.mp4:   1. Reset the settings on a photo and clear the history.   2. Click on the "Exposure" label to select that slider.   3. Quickly type "=" three times and then immediately use the mouse to click on the right end of the Contrast slider.   4. Observe that there is just one history step, "Exposure +0.30 0.30", even though Contrast is now +65 (or whatever value you clicked).   5. Set Contrast to -100, and observe there is now (correctly) a second histor

On MacOS 14.2.1, with Canon R3 and CR3 RAW files.   I don't use catalogs at all, just drag and drop raw files into Library, then edit in Develop. Just loading a directory of RAW files in this version just automatically generates XMP files for no reason, an old bug I haven't seen for many many versons.    As usual, XMP files should only be created when there are changes done to the RAW file, not just upon loading them in lightroom. It's a good system so I can edit galleries as needed, and then I can look in the directory and see if there are any photos I might have accidentally skipped over deleting by seeing there is no XMP associated with it. 

Okay, so just noticed recently that both my work laptop (Win10) and home laptop (Win11) have started crashing when jumping in/out of Library/Develop modules. I tend to end up with a grey screen in the main image area first before LrC either crashes completely or just hangs with the grey screen for ages.   Work laptop crash report attached (got deleted on upload). System setup info also attached for both.   Weird its just started. I'm using SSDs for both external catalogues too - only common factor?  

Lightroom Classic version: 13.1 [ 202312111226-41a494e8 ] MacOS Ventura 13.6.3 on iMac Pro 1. Import a TIFF into LR (mine was the result of focus blending in PS). 2. Do some editing, including some changes within an AI mask (select subject, in my case). 3. Rotate or flip the image, using the menu commands (not using the crop tool). 4. Re-edit in PS, using the “edit original” option. Save.   The result is that the image remains rotated but the mask doesn’t, and a weird crop is applied.

This was originally posted under "Bugs" but I really want this to be answered as a question. I will be happy to delete whichever post doesn't fit under the best category however! Thank you.   When using Lightroom Classic 12.2.1 with MacOS Ventura 13.3 (on a Retina 5K, 27-inch, 2020 iMac with the AMD Radeon Pro 5700 XT 16 GB and 72 GB of memory)... I am getting the entire image selected when I try to use the "Select People" then choosing "Entire Person." Lightroom Classic allows me to individually select the hair, teeth, eyes, etc. as usual but when trying to select the entire body, the whole screen gets turned pink to indicate that the Lightroom thinks that the whole picture is the person. I've attached two (redacted for privacy) screenshots of the "Subject" masking that still works as it should and the "Entire Person" mask that shows where the entire photo area has been selected incorrectly by the AI. Anybody have any thoughts? Thanks!

Since upgrading to v13, the export of images doesn´t work anymore. I always get this message:$$$/CRaw/Error/Unknown=There was an unknown error. (1)   I´ve tried reinstalling it, but its also couldn´t solve my problem. My system is Windows 11, 64-Bit version . All Drivers are up to date

Customer takes a picture on IOS device and makes Develop Adjustment edits on the IOS device in an Album that syncs with Lightroom Mobile.  That image appears in the collection in Lightroom Classic with a “Metadata Change icon. This is incorrect since no Metadata changes were made using Lightroom mobile or Lightroom Classic.  GPS on device has been disabled. Issue: When customer clicks on the metadata icon in Lightroom mobile and selects “Save” the develop adjustments are removed from the image in BOTH lightroom classic and the IOS device. The same behavior occurs when the develop adjustments are made in Lightroom mobile to an image taken on the IOS device

Why no one writes about the fact that in develop mode, after any manipulation with a photo, it is impossible to go to the next photo in the feed? You go, but the photo remains the same as it was, you have to go back and only then go to the next photo. This is a global problem!!  Anyway, I did some research and I realized why many people are silent about it, because this problem occurs only when using the +\- buttons on any keyboard, even on macbook !!!!. If you use only mouse or touchpad, there is no problem with photo transition. That's why many photographers don't pay attention to it, because they don't use the keyboard. Therefore, ADOBE does not react in any way.

Hi I recently updated my Lightroom Classic and now every time I try to launch it I get the error 'Adobe Lightroom Classic quit unexpectedl'   Below is the crash report. Does anyone know a fix to this? <Apple Crash report removed so Pinned Post is visible>

Since the latest version of Lightroom I can no longer edit an image in full screen. After pressing F to enter the full screen mode then pressing the > key to move to an adjustment the full screen image only displays a small rectangular part of the image in the top right hand corner.  Seeing this on both my Imac Pro and MacbookPro.   Also since the previous version of Lightroom pressing the I key there is a discernable delay before the information is displayed when the catalog is first opened. It used to be instantaneous. Again on both my Imac Pro and MacBook Pro.   Lightroom Classic 12.3 Mac OS Ventura 13.2.1

Hello,   Anyone experienced this issue? Upgrading to Ligtroom classic 12.1, RGB color readouts were completly off on masks. Visually you could see the expected changes in contrast, brightness, etc while mouse over readouts showed the same numbers as before. So completly off. Like you could see that black areas were getting toward complete black, but the readout was still at around 14% in all 3 channels.   I downgraded my Lightroom to previous 12.0.1. which works just fine.   iMac (Retina 5K, 27-inch, 2020) 3,8 GHz 8-Core Intel Core i7 40 GB 2667 MHz DDR4 AMD Radeon Pro 5500 XT 8 GB Osx Big Sur 11.6.4   Boris GG  

On Windows, the method catalog:triggerImportUI (path) opens the Import window but doesn't set the initial source to "path". It works correctly on Mac.   To reproduce on LR 13.0.1 / Windows 11:   1. Save this script to the file "test-import.lua":   local path = import "LrPathUtils".getStandardFilePath ("home") import "LrDialogs".message (path) local catalog = import "LrApplication".activeCatalog() catalog:triggerImportUI (path)     2. In LR, do Scripts > Open User Scripts Folder and place "test-import.lua" in that folder.   3. Restart LR.   4. Do Scripts > test-import and observe that the Import window opens but no source is selected in the Source panel.  The Windows 11 result is on the left, Mac OS 14.1 on the right:         

I upgraded to 13.0.1 and now it crashes intermittently in development mode. It could be around the time of moving from one photo to another but I am not sure. In editing about 300 photos it has crashed around 20 times. There is a pause, then a blank screen and then it crashes. One time it prompted me to send a crash report and I did. It also did this when I updated my graphics driver. This is what I have tried. I can not remember LRC crashing on this system ever before upgrading to 13.0.1 Updating other apps in CC like the camera raw Running all Windows updates for Win10 Updating the Nvidia driver to the latest and also making sure I am on the studio driver Tried disabling the GPU acceleration.  Updated loop deck drivers  Rebooted at least 5 times Deleted the GPU file in app data  My system   Windows 10 Pro 64bit - latest updates AMD Ryzen 7 5800X 8-core Processor 32GB of RAM MS1-B550 A Pro Mother board MSI RTX 3060 Sudio driver 537.58 M2 SSD for OS and a se

Hi folks,   I have these weird bugs that have been happening since the latest update and it is driving me crazy. It's a bit hard to explain but hopefully this is clear...   BUG 1 I'm in the develop module and I click to another photo and occasionally the develop settings from the first photo get applied to the new photo I just clicked on (I'll refer to this as the ghost settings). *BUT* it's not actually showing the develop settings being applied in the history. When I click on other actions in the history, it doesn't show the changes reflected on the image - it's still stuck on the developed settings it copied from the previously selected image (the ghost settings). Sometimes I have to leave it for a couple of minutes before it will revert to its own original develop settings. And if I edit while the ghost settings are applied then it's editing it with the ghost settings visible and I can't revert to the original develop settings. It's unbelievably frustrating.   BUG 2

Lightroom Classic 13.0, macOS Ventura 13.6 Lightroom 13 introduced new histogram style purportedly to accomodate HDR but the new style makes it difficult to actually use histogram to determine areas in gistogram free of data and settong white/black levels correctly.This all being discussed to death in this post https://community.adobe.com/t5/lightroom-classic-ideas/p-reinstate-version-12-histogram/idi-p/14157437 which was moved to ideas preseumably because it asks to reinstate v12 histogram. It is also being discussed here https://www.alex-kunz.com/new-features-in-lightroom-classic-13/ . I now rephrase the request for bugfix - fix the new histogram in v13 to make it show gaps in highlights and blacks clearly (similarly to the way v12 one did where it can be done with ease).The demonstration of the differences between old style and new style where 1-1.5 stop free part of histogram in highlights can clearly be seen in v12:   and not so clearly in v13  

I have seen many posts about this and then many lazy replies of 'this is now fixed in the update', but I have just purchased a Wacom Tablet, done everything which I've seen on YouTube ETC, and it is STILL not working.   The pressure DOES NOT WORK in Lightroom when trying to Dodge for example.   What is wrong with Adobe? Why isn't this fixed yet?   Windows Ink is disabled, and I've restarted several times and have the latest drivers.   What is the solution here? Or do I need to get a refund because Adobe have messed up with one of the most popular brands of tablet out there?

"An error occurred while saving the book: an error occurred adding text and fonts to the book."I am running Windows 10 (v10.0.17134); LR Classic CC v8.0 and v7.5 (to avoid yet another bug) both get the same error. i7-6700K with 16GB RAM, loads of free disk space, 15GB RAW cache, etc so no limitations that should cause problems. I have published around 15 books from LR on Blurb ever since the Book module first appeared; they all use the same layout standards and fonts so nothing new in this book. The book was producing a PDF and also uploading to Blurb until I edited some text fields and expanded one text box.  I have tried the community-selected workaround of selecting all text fields (Ctrl-Alt-A) and changing fonts to Arial then back to Myriad Pro (I have always used Myriad Pro except for Georgia on the cover) but still does not work.  Tried both v8.0 and v7.5 but neither work. No text or image boxes added so can't have any new empty boxes (and I am pretty sur

  I am a Jeffrey Friedl's “Export to Flickr” Plugin user since many years. Yesterday morning Lightroom Classic passed to V13 I used LR/Mogrify 2 and LR/Export to Flickr for many years now. With previous version of Lightroom Classic I used Mogifiy without problem with Export to flickr This is an example uploaded Oct 7th 2023 https://flic.kr/p/2p7NDVm This morning, after updating to LR V13 and Register Export to flickr the export of new pictures gave only the picture without its frame producef by Mogrify This is an example of the frame free picture uploaded this morning : https://flic.kr/p/2p8vNW9 I also tested exporting with LR/Mogrify 2 alone in a picture file, it worked just normallyLR/Export to Flickr alone also worked normally but not the mix of two!

In LR 13.0, the wrong keyboard shortcuts are shown for Range > Depth Range in the Masking panel for Spanish, French, Italian, and Portuguese.   In Spanish on Mac, "Alt" is shown instead of "Opción" or "Opc":   In French, Italian, and Portuguese on Windows, "Cmd+Opt" is shown instead of "Ctrl+Alt":                         

In Japanese, the keyboard shortcut shown for Create Virtual Copy in Library and Develop is "Shift + Command + y" but should be "Command + Shift + Y". (It looks sloppy to not follow LR's convention.)   Changing that on Mac will automatically change it for Windows to "Control + Shift + Y".    

Checking and unchecking Use Device Map in Lens Blur doesn't update the Focal Range histogram.   To reproduce in LR 13.0.1:   1. Import this HEIC with a camera depth map: https://www.dropbox.com/scl/fi/us562okxbc76t2q8gzxd7/depth-map.2023.11.01.heic?rlkey=182qxsw53lmpiqrvk1pwc1502&dl=0   2. Apply Lens Blur and click Visualize Depth.   3. Toggle .... > Use Device Map in the upper-right corner of the Lens Blur panel. Observe that the visualized depth map changes but the histogram remains the same:   The histogram should change to match the currently display depth map.                                                                    

When editing a photo with an embedded lens profile, the message "Built-in Lens Profile applied" often doesn't appear in the Lens Corrections panel.  To reproduce:   1. Download this catalog, which includes 32 raws from various Nikon Z cameras and lenses with embedded profiles: https://www.dropbox.com/s/sy42uni5okojm5j/lens-profile-bug.zip?dl=0   2. With another catalog open, do Preferences > Performance > Camera Raw > Purge Cache.   3. In the downloaded catalog folder, delete <catalog>Previews.lrdata and <catalog>Helper.lrdata if present.   4. Open the downloaded catalog.   5. Go to Library, select all photos, and do Library > Previews > Build 1:1 Previews.   6. Select the first photo and go to Develop. Observe that the message "Built-in Lens Profile applied" is missing from the Lens Correction panel.   7. Regardless of whether the message is missing, zoom to 100% and then zoom to Fit. Observe the message is n

Issue: Point colour does not clear when syncing from an image with no point color adjustments Lightroom Classic Version Number: 13.0.1 OS Version Number: 13.5.2 Steps to reproduce:  Image 1 has no point color adjustments  Image 2 has point color adjustments   Sync develop settings from image 1 to image 2 Expected result: Point color adjustments should be Nil, 0Actual result: Point color adjustments remain attached to image 2   Reversing the order and pointg color adjustments carry over from image 2 to image 1. Seemingly no way to clear the point color adjustment unless resetting image individually using the reset buttoin at the bottom of the develop module. Very time consuming for 1100 images.