Bug Reports

If someone has already reported this I apologize. I did try to search for it but couldn't find anything with the keywords I was using.If I enter a misspelled keyword accidentally it continues to show up in "Autocomplete" even though I delete it from the Keyword List.I've never had this happen before. I recently upgraded to the 9.0 release.My specific example of this behavior is when I go through to keyword basketball photos one of my keywords is Dribble. In the past I could type in dri and hit enter and it would autocomplete Dribble. I accidentally entered dri9 (the 9 is above the right side of the I key) and when I hit RightArrow to move to the next photo it entered dri9 into the keyword list. On the next dribbling photo when I typed dri it showed dri9 as the top option in autocomplete. I went into the keyword list and deleted the dri9 keyword. That removed it from the photo and from the keyword list but it still shows up in autocomplete. I tried to see if I could remove it by enterin

I have issues with LR Classic CC Library crashing (Message: "LR not responding") after adding larger quantities of metadata in the DNG. The above problem started when I decided to add older pre-digital era photos. These photos have no exif or date/time/place embedded since they are negatives or slides. As a result I have to add the above metadata manually. This was with my "old" Win10 PC a HP Z620 with Xeon processor and ample storage on a internal HDD (E:) the catalog was on the same drive. I was advised by Adobe support to move the Catalog to the C: drive and purge the cache. Give the LRcache extra Gb's (15 Gb) and leave the photos (approx: 10000.) on the E:drive. This seemed to be working. After working some time with the data the problems re-appeared. (LR not responding) It looks like LR is locked in some kind of "loop". To get out of this loop I have to end LR forcefully by Ctrl-Alt-Del and stop LR Classic. The result is that a larger part of the metadata is lost and not added to

A bug seems to be introduced with version 9.0 of Lightroom that when a plugin designer sets exports settings using the "updateExportSettings" of the Lightroom SDK all these settings are ignored and default settings are sent for the export job.When the following code is used, the files are NOT renamed on export. The exported file have the same name as the original files.updateExportSettings = function( settings )    settings.LR_collisionHandling = "rename"    -- Rename settings    settings.LR_renamingTokensOn = true    settings.LR_tokenCustomString = ""    settings.LR_tokens = "{ {naming_sequenceNumber_5Digits}}"endI do not know if this is the best place to put this, Adobe seems to have deleted the Lightroom SDK forum.

Changing the color profile in Lightroom and set it to any profile, including (and most visibly on) camera type profiles, will make (especially) the skin tones very/only yellow.This issue occurs only on Sony A6600 RAW files.Please note that the issue is NOT related (or influenced by/triggered by/associated with):- monitors (3 type of monitors, various brands, tested)- PC specs (2 pc, low & high specs)- other cameras (have been tested and the issue does not occur on the following: Canon EOS 1D (2002 model), Sony A6000, A7, A7s, A7iii)- software (Lightroom is at it's latest version, with auto-updates configured and it is an official license, mobthly subscription)- camera settings (regardlless of WB, WB Shift or any other settings, profiles, the issue occurs)- lens/lens attachments (regardless of the lens/lens attachments, the issue occurs)- time/location (the issue occurs regardless of the photo being taken outdoors/indoors, day/night/artifical light)Also, please note that further inv

Hi,Since a few days, LR 9.2.1 tells me upon startup that a new version is available. Of course, this is wrong. Using the Help | Updates menu has no effect. Adobe CC Desktop says : up to date.It's the new joke in town.

Just discovered this as a new problem in LR Classic 8.4, this isn't present in 8.2.In LR if you hover over a preset in the preset browser a preview of the effect is displayed in navigator and main screen. In 8.4 however if image is in portrait orientation and the preset contains either brush or radial actions these will be incorrectly displayed in the preview - they appear squashed. When you actually apply the preset however they apply correctly. Preview:Applied: Preview:Applied:

I've got allot of pictures in my Lightroom Classic catalogue without keywords, when I try and add keywords through the dialogue box Lightroom crashes and I have to sign into my iMac again from the welcome screen, it's happened around 8 times now and it's really frustrating. Does anyone know what could cause this to happen?

Lightroom Classic adds the green border to HEIC files from iPhone. See the original photo and a screenshot. If I edit this image in Photoshop (after applying the Lightroom corrections), I can see and edit the green border there as well.P.S. The files are modified because of this stupid limitations:Sorry! We were unable to upload your image because it was over 2MB in size. Please try uploading a smaller version of the image.Sorry! We were unable to upload your image because it is not a PNG, JPG, or GIF file. Please ensure your image is one of these formats and try again.

Keywords with national characters (Norwegian, ØÆÅ), are not sortedalphabetic.Keywords are all written i Norwegian.I'm running windows 10 Home, Version 1903 and Lightroom Classic 9.2

After I imported raw photos taken with HTC U12+, it shows incorrect temperatures and tint, as it's showed in the following picture:Every raw photo, no matter what temperature I've adjusted before I took it with U12+, showed the temperature at 50,000k, which is not supposed to happen.Also, the Tint shows rather high digits compared to the normal ones.It doesn't happen in other softwares that are able to edit raw files, such as Snapseed, which shows the correct temperature (4900k)Such an issue has been recognized by HTC, and they're working on it, but I was told to report the bugs here as well since it's not clear whose fault it is. Please fix this bug. Thank you.

Whenever I export from Lightroom Classic and do some editing in Photoshop and return to Lightroom Classic on saving, there is always a rectangle at a different light level than the rest of the image.  This is corruption, I don't see this rectangle at all in Photoshop and if I reopen the file in photoshop it is not there, just in Lightroom.It is sooooooooo annoying.You can see it in this attached image, it happens almost every time I edit in Photoshop and return to Lightroom.  I have more examples.IainMac OS 10.15.3, iMac 27" 2018, Benq SW321C Photographer Monitor. Adobe Photoshop 21.1.1 Lightroom Classic 9.2Same image in Photoshop:

When using the right-click to bring up the popup menu on the main photo in Library loupe view the "Email Photo" menu item is grayed out.It is not grayed out when right-clicking intop menufilmstrip in Loupe viewthumbnail in grid in Grid viewfilmstrip in Grid viewfilmstrip in Develop viewmain photo in Develop view.Reset of preferences or restart of the computer and Lightroom did not help.MacOS 10.14.6.  Lr 8.3.1

I am surprised to see that there are very few relevant standard preview size settings for people using a 4k monitor. The maximum setting is 2880px and then "Auto". Lightroom is choosing 6720px on the "Auto" setting which is massive and (I presume) contributing to Lightroom running extremely slow. This is all while running a brand new 16" Macbook Pro with 32gb of RAM, AMD Radeon Pro 5500M 8 GB, and 2.3 GHz 8-core i9 processor.Please include more preview size setting in between 2880px and 6720px for people working on 4k monitors.

In LR 9.2 when Lights Out is active, using Copy Settings changes the state of Lights Out to be Lights On.repro:1. enable lights out in either Library or Develop (any dim mode)2. Select an image3. Use either the kbsc (ctrl-sh-c) or the Copy button to copy settingsresult: Lights Out state changesexpected: Lights Out should not changeworkaround: push L again

Lightroom Classic - Updating to Lightroom Version 9 but my catalog from version 8.4 is incompatible and for some reason, it can't be updated. I can revert back to 8.4 temporarily so as not to lose my collection of work but it's not going to be a solution long term. Can you help give me some steps that might offer a solution to this issue I am encountering?Any advice, solution or steps that I might be able to try would be most appreciated.Thank you.Joe

While investigating another Lr bug, I removed my old Lightroom Classic CC 7 Preferences.agprefs file so that Lr Classic 9.1 would create a new one.I have noticed the following entry in the newly created file:AgImport_backupDownloadFolder = "C:\\Users\\Tony\\Pictures\\Lightroom\\Download Backups",After doing an import of some images and closing Lr, this setting changed to:AgImport_backupDownloadFolder = "C:\\Documents and Settings\\Tony\\My Documents\\My Pictures\\Lightroom\\Download Backups",This is now using the old Windows XP folder names ("Documents and Settings", "My Documents" and "My Pictures"), and yes, I know there are hidden links in Windows 7,8,10 to handle these old names for backwards compatibility.Later, Lr created another entry in Preferences:AgMRUPopupList_importBackupDownloadFolder = "s = {\\"C:\\\\Documents and Settings\\\\Tony\\\\My Documents\\\\My Pictures\\\\Lightroom\\\\Download Backups\",\}\",which is obviously related to the AgImport_backupDownloadFolder entry.In

I created a white text string with a dark shadow in the LR watermark editor. When printing to a jpg file, the shadow did not appear although the text appeared correctly (flat - no depth). I then tried to print to a printer, selecting a PDF printer in the printer dialog box (MacOS 10.14), the shadow appeared correctly in the pdf file. I tried various combinations of printing options, and decided there is a bug in printing watermarks with shadowed text to a jpg file (print to file). I printed the image to a pdf file, imported to photoshop, the saved as a jpg file to get around the problem. Latest version of LIghtroom Classic (2020) as of 2020/02/11.

Using two displays, preferences and system report may both open and can be moved behind second window. Lightroom Classic 9.2 2-11-20 release. Mid-2011 21" iMac, macOS 10.13.6.

In Lr9.2, open Preferences, make a change to the Raw Defaults, then click the Cancel button.Reopen Preferences and check the Raw Defaults settings. They should not have changed, i.e. the changes made in the previous step should have been discarded, but they haven't.This is so very bad. Another black mark for the development team.

There is a problem with automatically detecting external metadata changes in HEIC files.I have Lightroom Classic (9.0, latest 11/2019 version) installed on two networked computers as allowed by the license: a desktop and a laptop. Both machines have "automatically write updates into XMP" set.Once I import and develop our travel photos on my desktop, my wife synchronizes the pictures folder on her laptop, sometimes adds captions, and picks photos to print for scrapbooks by setting those photos to "Green". I then synchronize the shared pictures folder on my desktop and order prints of the ones she picked.This system works great for .JPG and DNG files produced by my Nikon SLR.  But we also use our iPhones at times when I don't want to carry the SLR.  On this last trip, I set our iPhones to produce HEIC files because Lightroom now supports these.  After importing and developing, we set the color of the photos on the laptop to green, I synchronized the folders on my desktop a

Version 9.0 has a bug using Sony cameras (A7III at least): while scrolling images with embedded previews, you'll get a glitch where the right border of the image looks "multicolored". While scrolling the colored border is thicker, while it settles on few pixels when you stop scrolling. Nothing that compromises the workflow, but still annoying. See image.Images with 1:1 previews don't have this issue, as well as images that have been edited.Turning off the GPU doesn't make a difference. I have to note that it only happens to one long side (either right or bottom).As said, generating a 1:1 preview solves the issue (though I work with smart previews):Here is my system information:Lightroom Classic version: 9.0Operating system: Windows 10 - Business Edition Version: 10.0.17763System architecture: x64Logical processor count: 8Processor speed: 3.3 GHzBuilt-in memory: 16341.9 MBInternal Camera Raw version: 12.0 [ 321 ]Displays: 1) 1920x1080Graphics Processor Info:DirectX: NVIDIA GeForce GTX 1

When I try to create a virtual copy in Lightroom ClassicI get the following error:"An internal error has occurred. ?:0: attempt to index field 'additionalDevelopMetadata' (a nil value)".The error started after I combined a second catalogue into a main catalogue using the 'Import from another catalogue' function.The error only happens with the images from the second catalogue that have been imported into the main catalogue. All other images in the main catalogue are fine. I still have the second catalogue and the virtual copy works correctly in that catalogue as well, so the issue appears to be related to the import process. The reason for combining the two catalogues was to reduce the need to swap between the two.I had already done quite a bit of work on the imported images before I came across the virtual copy error, so I now have a bunch of edited images in my main catalogue that won't allow VCs to be created, and a bunch of un-edited images in the old second catalogue that will allo

Metadata changes in the IPTC extension data field do not take. For example, I change "Location created-City" from "New York--Brooklyn" to "New York-Brooklyn", but once I click off the picture, onto another, and go back to the picture that I attempted to make changes to, the "Location created-City"filed has reverted back to ""New York--Brooklyn". These extension fields are very important to me and it's frustrating that they don't work properly

When displaying GPS coordinates, the Metadata panel truncates, rather than rounds, GPS coordinates at thousands of a second. This corresponds to an error of about 3.1 cm of latitude or longitude at the equator. While obviously not of concern to most users, commonly used augmented GPS systems can produce sub-centimeter accuracy. See this original report of the problem: https://community.adobe.com/t5/lightroom-classic/gps-data/td-p/10789291To reproduce:1. Select a raw photo in Library.2. Copy and paste this into the Metadata panel's GPS field: 0°0'0"N 9°53'31.787" E.3. Observe that the field now incorrectly displays: 0°0'0"N 9°53'31.786" E. 4. Observe that the longitude stored internally in the catalog (targetPhoto:getRawMetadata ("gps").longitude) is correctly: 9.892163055555 = 9°53'31.786999998".  Rounding that to thousands of a second yields what was input, 9°53'31.787, while truncating it yields what was displayed, 9°53'31.7

Some metadata presets don't set Altitude correctly. To reproduce:1. Select a photo.2. In the Metadata panel, do Preset > Edit Presets, click Check None and then check Caption, GPS, Altitude, ISO Country Code, and Title. Enter 100.0 into the Altitude field.  3. Save the preset, calling it "Altitude Bug".4. Apply the preset to any photo and observe that the Altitude field is cleared rather than set to 100.0.Interestingly, if you remove any of the fields Caption, GPS, ISO Country Code, or Title from the preset, it works correctly.See here for the original report: https://community.adobe.com/t5/lightroom-classic/in-lightroom-classic-9-1-altitude-saved-in-metadata-preset-is-not-applied/m-p/10835470#M171442Tested on LR 9.1 / Mac OS 10.14.6.