Bug Reports

What's the purpose of making the scrollbar wider when switching process version from V5 to V6 ??  

I can confirm This is happening to me since I updated to 12.4 just half an hour ago. Now I can no longer launch lightroom classic. Please help. I've sent crash report with my email address. Let me know if you cannot find it.

I recently got a 5D IV and just noticed that capture times on video files shows 5 hours ahead in Lightroom (photos are fine). This causes videos taken late in the day to be imported into the folder for the next day. I'm running the latest Lightroom (6.10) and 5D Firmware (1.04). I checked my old 5D Mark III videos and they are fine. I suspect Lightroom ins't picking up the timezone info and is using UTC time.  Is this a bug?

Hi,   Please look at this:     Monitor resolution: 1280 x 1024. LR maximized. With LR in window mode, the module selector even disappears by the right of the window.   Problem appeared with LR 11. Same issue after latest update, 11.0.1.   A solution would be greatly appreciated.

Hi all I have recently had the most anger indusing issue ever with LRC . When I try to export my slideshows some of them crash the entire programme. I am ripping my hair out here as I use slideshows daily for wedding images and have lost days trying to figure out the problem . Must have sent fifty crash reports to Adobe. Please hlep me anyone  Will   

Using LRC v12.3 on a Windows Machine.  Working in library module, with two monitors.  Primary Monitor set to loupe and second is in grid.  If I click F to go fullscreen, the primary monitor quickly goes to Fullscreen for a second then back to normal view.  If I turn off the grid view on the second monitor, it goes into fullscreen just fine and stays there till I click F again.  Prior to the latest release this was not the case, and the fullscreen worked fine.

Issue:   While panning the photos in before & after view, with spilt screen, when a image is fully panned on one side, it fails to reappear on that side of before or after. A screen recording of the concerned problem is attached.   System & LRC version description:   Lightroom Classic version: 12.4 [ 202306052221-b70c0975 ]License: Creative CloudLanguage setting: en-INOperating system: Mac OS 13Version: 13.4.1 [22F82]Application architecture: arm64Logical processor count: 10Processor speed: NASqLite Version: 3.36.0Built-in memory: 65,536.0 MBReal memory available to Lightroom: 65,536.0 MBReal memory used by Lightroom: 11,073.9 MB (16.8%)Virtual memory used by Lightroom: 4,31,764.3 MBMemory cache size: 983.4MBInternal Camera Raw version: 15.4 [ 1508 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2Camera Raw virtual memory: 1559MB / 32767MB (4%)Camera Raw real memory: 1710MB / 65536MB (2%)Standard Preview Size: 3024 pixelsDisplays: 1) 3

When exporting JPG images from the print module, the watermark is sometimes in the wrong location, despite being displayed correctly in LrC.   LrC 11.0 Windows 10 Pro x64   This is how my watermark is displayed in LrC and exported in JPG if I don't move the photo (up/down or left/right, depending on the aspect ratio). So far, so good.   If, on the other hand, I move the picture (in this instance to the left), the watermark still displays correctly in LrC but is moved in the JPG file. The same happens with text watermarks:   And the same issue also occurs when moving a picture up/down.   I noticed it first with watermarks I had created long ago, but I made new ones from scratch (I did not edit/re-saved the old ones) just to be sure, and those are the watermarks shown here.   Also, of course I couldn't checked every possible output aspect ratio/pixel size, but I've tested quite a few ones and as far as I can tell, this problem occurs only with pictures ta

When using the Lightroom Classic 12.4 'Subject' AI filter, it doesn't recognise the only person of colour. This is terrible, and racist. I hope by reporting this it might contribute to technical improvements, as this isn't the firrst time I've had the same issue with AI not recognising people of colour.Very disappointing.

Since the latest update (12.2) Auto Mask while using brush seems to not auto mask.I've been trying to mess around with GPU acceleration and without. Same issue regardless.I've heard about this problem from another user aswell.MacBook Pro 16" 20196-core i7 2.6Ghz32GB RAMRadeon 5300M 4GBmacOS Ventura 13.1

The issue of Lightroom Classic freezing and crashing when syncing collections to lightroom.adobe.com was addressed in the list of bug fixes included in the new Lightroom Classic version 12.4. It did not help. I installed 12.4 this morning. I was able to sync a few collections and then it crashed. I cleared lightroom.adobe.com and removed All Synced Photographs and tried again. This time it crashed in a different spot. Sometimes it crashes when I am not syncing. I have had it crash upon importing files.  I have had it crash after opening the program.  I am totally baffled. This has been going on since March 5th, 2023.  I have been in contact with Adobe Technical Support numerous times and have had to explain the problem to a different person each time.  I asked that the problem be escalated and they dumped and uploaded some log files.  They were supposed to analyze the logs and get back to me.  That didn't happen. I have tried everything suggested

Hello, I have a problem with export my pictures after update Adobe Lightroom classic catalog. I´m not using watermark. So, I can´t understand this failer error. Can anybody help me please?      {Title updated by moderator}

Lightroom V3.4.1 ACR 6.41 (Windows 7Pro 64bit) I have an image, shot in RAW, in the Develop Module, have performed, a crop, straighten, plus a few tweaks to overall image, importantly a Transform-Flip Horizontal, go to the Print module, Lightroom template – 1 large with stroke, Check the Watermarking Box, Print to : JPEG file, Res 72 ppi, Quality 100, press the “Print to file” button – save to location – image is fine, but the watermark is BACKWARDS in the horizontal opposite corner! Like in a mirror! - Does not happen when the image is not transformed ? Image is not available

I'm having this issue after upgrading to 24.4.1 with Lightroom 12.3 on Windows 10.  The taskbar tab turns orange, but I have to click on it to get Photoshop to come forward.  Any idea what's going on?   Thanks, David  

[This bug still exists in LR 10.0. See here for sample images to test with: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-preset-hover-preview-incorrect-for-incremental-temperature-tint/5f5f46154b561a3d4272bc43?commentId=5fc3e345ce4ce1357af23986]   The preview of a develop preset when hovering over it in the Presets panel is incorrect when the preset contains IncrementalTemperature and IncrementalTint values and the photo being edited is raw. To reproduce:1. Open a non-raw in Develop and change Temp and Tint to +20.2. Save a preset "Temp/Tint" with just White Balance checked.3. Open a raw in Develop.4. Hover the mouse over Temp/Tint and observe the change to the photo.5. Click on Temp/Tint and observe there isn't any additional change to the photo (as expected).6. Move the mouse pointer over the photo. Observe that the photo colors noticeably change.7. Repeatedly move the mouse pointer back to over the Temp/Tint preset and then back over the phot

I convert whole folders of raw files to lossy DNG on a regular basis, and since earlier this year (at least), I've noticed a problem that affects a very small percentage of the files (sometimes it doesn't happen at all), but it's starting to become a little annoying.The problem (when it happens) is that some of the resulting lossy DNG files look good in the Develop mode of LR Classic and in Camera Raw. Even the preview from Windows file explorer (and when using image viewers that display the embedded jpg preview) looks ok. But when displaying these problematic files from the Library module in Lightroom Classic, they show a strong purple cast. So, I think there is some problem with the preview generated by LR.Like I said, this problem happens very rarely, but it keeps happening every now and then. Most of the times I am able to fix the "pink preview" by re-building 1:1 previews, or just removing and reimporting the file. But there must be something going on with the preview generation f

Ever since LR 7.3 introduced the new develop preset format, it takes O(n^2) time for a plugin to access all of the develop presets. Some users have 5K, 10K, or 15K presets, and it can take minutes for a plugin to access all of the presets: for _, folder in ipairs (LrApplication.developPresetFolders ()) do     for _, preset in ipairs (folder:getDevelopPresets ()) do        ... Users think the plugin has crashed or hung! While having 10K presets may seem unusual, there's no excuse for LR to take minutes to return all the presets.Here's how fast my LR / Mac OS loads presets versus the total number of presets:Most likely, LR is storing all the presets in all the folders in a single flat list.  When the method folder:getDevelopPresets() is called, it scans the entire list for presets with a matching group.  The correct implementation is obvious: Use a hierarchical representation, with a list of folders, each folder with a list of presets.

This worked up until last week. I have verified the login credentials via filezilla, which works perfectly. I have also contacted my web host, and they have said that the error that they see on their end is that Lightroom is using an outdated sftp protocol, which is no longer considered secure, and is no longer supported on their server. The sftp requirements for my host are listed here:https://wpengine.com/support/sftp/ I am running the latest version of lightroom classic CC. I appreciate your help in getting this issue resolved quickly. I have also try deleting the preset and making a new one with no change. Thank you.

Create a Smart Collection that shows at least 20 pictures in grid view   View - Sort - Label Color View - Sort - Ascending   None of the cells must be colored   Use the scroll bar to show the 1st. row   Click a cell an press “9” to paint it blue.  Repeat this 5 more times to paint non consecutive random cells   Every colored cell must go to the first rows   Now: Click a non blue cell, drag it and drop it on it self   Result: the color order is lost   Note: This situation doesn’t happen if you repeat these steps in a folder, the problem arises just in smart collections

The fields in the Default, EXIF, IPTC Extension, Location, Quick Describe, and Video tagsets jump and down as you enter text in fields and tab to the next field.  When you hit tab, LR displays briefly shows an empty field at the top of the panel and then removes the field.  This is very distracting when you're trying to enter lots of data.Here's a screen recording: https://dl.dropboxusercontent.com/u/21811200/metadata-entry-bug.2017.07.1.movThis happens to me with new catalogs on CC 2015.10.1 / OS X 10.12.5, CC 2015.5 / OS X 10.12.5, and CC 2015.10.1 / Windows 10.  It doesn't happen with LR 5.7.1 / OS X 10.12.5.

I noticed in the print module when I unchecked the print resolution option that Lightroom would display different image resolutions based on the orientation the shot was taken in.  For example, I shot on two different cameras both 24MP (Nikon d7100 and Sony a7ii) and for portrait it would display an image of 2x3 at 1333ppi while for landscape it would display 3x2 at 1440ppi.  I think this is a bug for Lightroom only as Photoshop still reads both files as the same resolution and the file sizes are identical no matter the orientation. I don't know if this is just a calculation glitch or if Lightroom is actually reading these files as smaller.

I am unable to start / use Lightroom Classic since a week. The programm crashes at startup with error  <crash exception="EXCEPTION_UNKNOWN" exceptionCode="0xe06d7363" instruction="0x00007FFD5CF3CB69"> I am on Windows 10 with AMD Radeon Vega 8 Graphic Card. (VRAM 2048 GB).   All other Adobe CC applications are running fine. I am primarily using Lightroom, though. Hope anyone can help. Here is the full crash report.   <?xml version="1.0"?><!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"><crashreport serviceVersion="4.8.0.6" clientVersion="4.8.0.6" applicationName="Adobe Lightroom Classic" applicationVersion="12.2.1" build="[202303011008-5bfbce17]" source="Windows-Client" crashType="n/a"><time year="2023" month="5" day="8" hour="8" minute="8" second="41" timeoffset="60" timezone="Mitteleuropäische Sommerzeit"/><user guid="ad8b2931-cfb0-45f9-bf97-ca5f3b7a0dfa"/><system platform="Windows 10 Pro" osversion="10.0" osbuild="19045

Today I imported some HEIF images (Camera: Sony Alpha 7 IV) into lightroom. Everything was fine until I opened the develop module. Whenever I did so it first showed a warning that there was an "error writing the metadata" and after deselecting the image the prompt "error reading the image" came up.       I already tried following: Re-importing the images (directly via Lightroom copying from the SD card to the MacBooks desktop), manually copying the images to desktop folder and then importing. Checking all the privacy settings (accessability  and full disk access), first-aid for the harddrive and restarting both LR and the MacBook. Also LR is running on the latest update. My catalouge is currently running from a 64GB USB Stick (formated for Mac OS Extended (Journaled)) and the images are in a folder on my desktop. So I don’t see a reason why or what is causing this errors.

Searching for ancestor keywords in the Keyword List panel shows incorrect results for descendant keywords.  The behavior broke somewhere between LR 10.4 and 12.2.1.   To reproduce on LR 12.2.1:   1. Assign the hierarchical keyword 1 > 2 > 3 to a photo.   2. In the Keyword List's Filter Keywords box, enter "1".   3. In LR 10.4, observe that all the keywords contained by keyword 1 are displayed, that a right arrow appears when you hover over 1, and the correct count is shown next to 3:   4. But in LR 12.2.1 observe that: a) keyword 3 is not shown, b) no right arrow appears when you hover over keyword 1, c) an incorrect count of 0 is shown for keyword 2 (the panel normally never shows counts for ancestor keywords, only for directly assigned keywords), and d) the triangle to the left of keyword 2 points down to indicate there are descendants displayed, but the descendants aren't shown:   See here for the original report: https://community.adobe.co

After you clear the GPS field of a DNG via the Metadata panel, Metadata > Save Metadata To File doesn't clear the GPS coordinates in the file's EXIF.  To reproduce:   1. Import this DNG and observe in the Metadata panel that it has GPS coordinates:   2. In the Metadata panel, clear the GPS coordinates.   3. Do Metadata > Save Metadata To File.   4. Use Exiftool to observe that the file still has GPS coordinates:     $ exiftool -a -G -gps:all APC_0851.dng [EXIF] GPS Version ID : 2.2.0.0 [EXIF] GPS Latitude Ref : North [EXIF] GPS Latitude : 38 deg 7' 51.64" [EXIF] GPS Longitude Ref : West [EXIF] GPS Longitude : 119 deg 26' 42.64" [EXIF] GPS Dilution Of Precision : 6.000906208 [EXIF] GPS Speed Ref : km/h [EXIF] GPS Speed : 1.770554817 [EXIF]