Bug Reports

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.

Is this a normal behavior or a bug?Select "Export...", the export window opens, post processing is there under watermarking (top image).Check a preset (click on the checkbox next to a preset), post processing disappears (image in the middle). Uncheck the preset, post processing doesn't come back (bottom image).To get post processing back you need to click cancel, and open the export window again.

Lightroom Classic v9.1 on MacOS Mojave 10.14.4Trying to export a book to PDF. 13x11 size, no cover. PDF will be created with most pages, but pages using specific custom pages are skipped/left blank. In LR, the progress bar still says "exporting book to PDF," and that process is never completed. I made a copy of the book and eliminated all pages except the two problem pages. Same result, cannot export those two pages to PDF, progress never completes.I changed the images for those two pages. Same result.I changed those two pages to use one of LR's templates and different images. The PDF now includes actual pages (not blank ones), but the process never completes. I exported this book to a new catalog. Tried different PDF settings (quality, color space, etc). I deleted preferences. Deleted all custom templates I created. Rebooted. Etc. Problem persists. I CAN, however, export this book to JPEG, but that is a more time consuming workflow. Does anyone have any other recom

In Lightroom, versions prior 9 the Export dialog had a very convenient behavior: any settings changed were retained, regardless of the fact that Cancel or X (close) was clicked. Now, in v9 this has been changed, so Cancelling the dialog looses all settings!The behavior before v9 was very convenient and somehow designed with the right intent: one may forget to do further adjustments to the files being exported, so the export procedure must be postponed...The behavior in the current version, v9 is quite unusable. Ok, if Cancel means cancelling all settings, then let the user retain the settings made already (chosing export location, file type, size, etc) so please add a third button: 'Close dialog for now' (or something similar, clearly understandable). Clicking this button should retain the settings but should not start the export procedure.

Since Catalina, option to export and to Use Lossy Compression doesn't seem to work no matter the camera raw compatibility?

Hi there,Funny bug with the export function:The function to Export with Previous does not work when the previous export was a User Preset. It's the previous previous setting that is then used.Cheers!

Hi,I do a lot of photography with country lodges where uprights are vital. In a shoot i may edit 300-400 shots and the ability to use sync to automatically apply Transform auto uprights is huge to me.For some reason this no longer works properly. Now when i try and sync apply this to several images it opts for the 'update' and not 'upright' - this usually causes the verticals to be wrong or badly wrong.I'm using version 8.3.1 on Windows 10.Is this a known bug or is there a fix to save me having to manually apply this on every image, even a keyboard shortcut would help for now !!TIA,Mike.

When exporting a folder into a catalog named "Katalog - Fridays for Future - středoškolská stávka za klima - Olomouc - 15. 3. 2019", Lightroom Classic CC crashes. The window quietly disappears and no crash window is opened. Catalog folder is created but remains empty. This does not happen when naming the catalog "Katalog".   My Lightroom Classic CC installation is up to date. Release 8.2, build 1204643, Camera RAW 11.2.

This is a small bug, but one that has persisted for the last several minor and major releases of Lightroom CC and Lightroom Classic CC.Lightroom offers users the ability to have a custom splash screen appear instead of the default one built in to the program. That function works just fine, but the text that is displayed is woefully outdated. (See example image attached to this post.)The Adobe copyright information displayed on the bottom of this custom splash screen hasn't been updated in four years. It still reads: "Lightroom © Copyright 2007-2014 Adobe Systems Incorporated"  Just thought you might want to have the programming team update that text string for the next release so that the Copyright is accurately displayed when the custom splash screen option has been enabled.

I just encountered a weird thing. My website complains with just TWO out of many photos I posted (JPG from LR), that it can't read the EXIF data. Looking with IrfanView, there are no EXIF data in these two (they got exported in one batch with all the others).I noticed that these two photos are heavily transformed (Vertical -65), whereas all the others, that got some transformation (not all but quite some) don't have such high values and got exported with their EXIF. So. I played around with the vertical value and found out, that the EXIF data gets exported up to the value -39 and from -40 on it's missing. Reproducible.

Created a collection of photos (just manual selection) and those photos were flagged as picked up (white flag), when I select a photo in bottom row of thumbnails and hit U to unflag, the correct message appears on screen about unflagging but on the thunbnail photo still appears that white flag and dissapears once mouse is moved away. But when mouse is over this image again (not clicking, just moved cursor to thumbnail, flag is back.For Reject (black) flag there is no issue.Using Lightroom Classic version: 8.4 [ 201908011719-03751b60 ]

P: Videos do not play or import macOS High Sierra

Lightroom 8.4 crashing when attempting to access Map or Web modules. No problem accessing all other modules. Using macOS 10.14.6 on an iMac Pro.

1. Import an image and apply metatdata to the Title field. (eg. "Lovely Wiew")2. Export to jpg. The jpg has the Title "Lovely Wiew".3. Recognise the typo (ie Wiew should be View).4. Correct the raw image in Lightroom. Raw image now has a title of "Lovely View".5. Re-export the image, overwriting the existing jpg.6. The jpg still has the incorrect Title value of "Lovely Wiew".after correcting and re-exporting the image, the catelog value for this raw and jpg should be "Lovely View" and the metadata within the jpg should contain the Title "Lovely View".This bug causes me unending levels of grief and hours of wasted re-work time.