Bug Reports

This may be because I am running an older iMac, but in Grid View, images in portrait mode are getting the filename cropped when displayed in the bottom label.  Is there a workaround for this?  It's not work stopping, just annoying.  

In v10.1.1, I can select a group of images. Using Crop & Straighten, I select an aspect ratio of "2x3 / 4x6", the aspect ratio is locked on the master image. I then Synchronize the group of images, selecting only "Crop, Straighten Angle & Aspect Ratio". The entire group of images now has an aspect ratio of "2x3 / 4x6", with the aspect ratio locked. This would appear to be the desired effect, when syncing a crop at a specified aspect ratio.   Now, with the new v10.2, the same sequence ends up having only the master image with the aspect ratio locked! All other images in the selected group have the correct aspect ratio, but they are set in the unlocked state!   I have two computers, one with each version, they are replicating the above. This is a major hit. I'm performing this on hundreds of images at a time, I then need to go into each image and tweak the position of crop. With the crop unlocked, I can mistakenly screw up the aspect ratio.   System Specs:   &

I recently imported to Lightroom a few thousand photos that I had scanned. Then I tagged faces in them. Lightroom slowed down until it started disappearing and reappearing. I noticed that the task manager could no longer display graphs.  These are symptoms of a handle leak, so I rebooted.   Having rebooted I restarted Lightroom and continued tagging faces. In Task Manager I kept an eye on the columns: Handles, Threads, User Objects, and GDI objects. This is how they looked at the beginning: And this is how they looked after a lot of tagging: All four counters have increased significantly. In particular "User Objects" has increased from 2,526 to 5,588 items. This indicates a Window leak.   So I brought up Spy++ and looked at all the windows on the system.   There were hundreds and hundreds of top-level listboxes!   All these ListBoxes are owned by Lightroom, but it is not their parent. Their owner is "Lightroom Catalog-2-v10 - Adobe Photoshop Lightroom Cla

When updating web / classic galleries the 'Update Web Gallery' never finishes. This occurs with all the templates in the 'Classic Gallery'. I can make changes to things like the Site Title, Collection Title, etc., in a Classic Gallery and those changes will be displayed on the monitor but images included in the gallery are never displayed. I can modify and create other gallery templates with no issue (Grid, Square, and Track) and images are shown appropriately. However, 'Preview In Browser' will work and reflect changes accordingly. 

As this has happened to me over a dozen times in the past few weeeks, and after each instance the dialog box appears stating there is no known solution so would I like to sned in a report, I am hoping it is not breaking news. But, when I attempt to go to the Maps mode from Library or Develop after having selected a few (or a few dozen) images, LRC unexpectantly quits.   Through trial and error, I have found that if I do not make an image selection and then go to Maps mode, it usually does not just quit - so there is that. But obviously not what was intended, since this is new behavior since gettting the latest update of LRC.   If it is pertinant, I am runing this on an M1 MacBook Pro with 16GB of RAM (and an external 2TB SSD) on OSX 11.5.1

Lightroom Classic 9.3 and 9.4 and probably other versions:Right-click a Develop preset and select Apply on Import from the menu. A plus sign is appended to the preset's name. Go to Apply During Import on the Import screen and notice that the preset's name appears in the Develop Settings field. While still on the Import screen, select a different Develop preset from the Develop Settings list. When you return to the Develop module, the plus sign still appears on the originally selected preset rather than the preset selected on the Import screen.

Auto Sync in Survey mode doesn't sync changes made to the stars under the thumbnail, though it does sync changes made to the pick and rejected flags under the thumbnail, to the stars in the toolbar, and to the stars with keyboard shortcuts.   To reproduce:   1. Select four photos and go into Survey mode.   2. Do Metadata > Enable Auto Sync.   3. Click and change the stars under one of the thumbnails -- notice that the stars do not change for any of the other thumbnails.   4. Click the pick and reject flags under one thumbnail, and notice that the other thumbnails also get the flags.      5. Click and change the stars in the toolbar (not under the thumbnails) and notice that the stars change for all the thumbnails.   6. Use keyboard shortcuts (e.g. 1 ... 5) to change the stars and notice that they change for all the thumbnails.   Tested in LR 10.0 / Mac OS 10.15.5.

Lightroom 9.2.1 had this problem, I was hoping 9.3 would fix the bug. It doesn't!If you create a slideshow which contains mov files, if you do no changes to the mov file, the slideshow Export video works fine. However, if you change the mov file white balance or tone (e.g. in the library quick develop panel) then try and export the slideshow as a movie, the process just hangs forever.Does anyone else see this problem? can you try and reproduce.My mov files are created by a Fujifilm X-T3, I'm using MAC OS Catalina 10.15.5Here's my system information:Lightroom Classic version: 9.3 [ 202005281810-476e492c ]License: Creative CloudLanguage setting: en-GBOperating system: Mac OS 10Version: 10.15.5 [19F96]Application architecture: x64Logical processor count: 8Processor speed: 4.0 GHzSqLite Version: 3.30.1Built-in memory: 24,576.0 MBReal memory available to Lightroom: 24,576.0 MBReal memory used by Lightroom: 1,759.6 MB (7.1%)Virtual memory used by Lightroom: 7,041.7 MBMemory cache size: 39.8M

I'm currently using LR Classic release 10.1.1, Camera raw 13.1, on an iMac running Big Sur 11.2. and GPU AMD Radeon Pro 580 - 8gb.  I use a Wacom and MIDI2LR with a Behringher X-touch.   This error is extremely similar to the problem where brush work was deleted/modified when spot removal tool was used, with this problem when you exported the error was not exported.   The problem I am experiencing is that in the library panel (and on the film strip when in develop mode) I am seeing the incorrect brushwork on a graduated filter which is being deleted/modified/affected, but not when in develop mode (develop mode is showing the correct edit).  On top of this when I export a full res jpeg I am seeing the problem in the exported jpeg.  You can see the specific problem on their faces in the images below.  I've since worked out that the library version of masking is where my Wacom pen drew, and the develop version shows the auto mask selection.  But when I e

When I copy the settings and only check "color adjustments" and then paste the settings onto another image, it also copies and pastes the tone curve, even though it's not checked. This has always been an issue for me and I would appreciate if someone helped, as I have to enter the settings manually on every photo. I am using Windows 10 if that's relevant.

The Smart Preview Status column in the Library Filter bar's Metadata browser shows wrong counts.  To reproduce:   1. Start with a catalog containing many photos.   2. In All Photographs, do Expand All Stacks, select all the photos, and do Library > Previews > Discard Smart Previews.   3. Select the first 10 photos and do Library > Previews > Build Smart Previews.   4. Create a smart collection with the criterion "Has Smart Preview is true". Observe that the smart collection shows a count of 10.   5. Open the Metadata browser with the single column Smart Preview Status and select Has Smart Preview.   6. Observe that the count for the line Has Smart Preview usually is much less than 10, but the number of photos displayed in Grid view is always the correct 10.   See here for the original report: https://www.lightroomqueen.com/community/threads/wrong-photo-counts-in-metadata-filter.42872/   Tested on LR 10.2 / Mac OS 11.1 and 10.2 /

Photo > Enhance with the Super Resolution and Create Stack options never completes when run on a photo in Quick Collection. The .dng appears but the progress bar never finishes. This doesn't happen when Create Stack is unchecked.  Resetting preferences doesn't help.   Most likely the code that tries to create the stack doesn't realize that collections aren't allowed in Quick Collection.  I think the proper behavior is to grey out the option when invoked on Quick Collection photos.   Tested on LR 10.3 / Mac OS 11.3.1.  Doesn't happen on my Windows 10 LR.  

I've been subscribed for over 2 years now and have never been able to make use of Lightroom Classic. Every time I try to import more than a handful of folders worth of photos it just freezes up. I have tens of thousands of images from over the years but the most I've ever been able to import has been perhaps a thousand before it just freezes, and even then it takes up to an hour just to import a couple hundred. I'm using the add option so I don't know if that makes a difference. I've tried uninstalling and reinstalling - more than once - before anyone asks.   This has happened on 2 different laptops by the way - I expected it with my old one as it didn't have enough RAM, but I kept lightroom in mind while buying my new laptop. Despite that it's still unusable for my needs...or anything to be perfectly honest. It also freezes every time I try to use to stitch panoramas. I'm doing them in photoshop now, but from the few times Lightroom hasn't crashed I know it's better for this than

When using the straighten tool on an image, clicking and dragging does not show the straighten line when in Soft Proofing mode. This is happening in Lightroom 10.3, on macOS Big Sur. 

Hi Adobe I had a long support session with you today. A short command \ (backslash) is not working on Swedish keyboard. The command triggers zoom instead. I could with Alt+Shift change the keyboard setup in Microsoft only to try and the \ worked fine.

Windows 10 Pro, Lightroom 8.3.1I have been tagging faces and noticed after a while that LR has slower and slower redraws and general GUI response. Looking in the task manager, I see 1800 or so GDI handles in use. At start-up it is more like 670 handles.After some playing around while watching the task manager, I blame the Navigator window. If I just mouse-over a dozen or so folder names, the Navigator window shows the first photo in each folder, and the GDI handle count jumps up by dozens. It is the same set of photos each time, so it isn't about caching of bitmaps, I don't think.There may well be other handle leaks, but this is the most obvious one.My system has 128GB of memory. In the Old Days of Windows, leaking a few hundred handles basically killed Windows. More recent versions claim to let you waste handles recklessly, but the truth is that programs get unacceptably slow pretty quickly if they leak. For now the work-around is to close and re-open Lightroom. But you want to m

Dear developers,   PLEASE make a troubleshooting article in the official support articles for Lightroom Classic, for the startup crashing problem appearing constantly.    The Lightroom Classic starts, it shows the pictures from the library, then it pops up the error reporting window - 0xc0000005 error.    I faced this already 4 times during a short time period of 3 months.    Everytime I did more hours of troubleshooting and googling what can cause this problem.  I started with GPU drivers, update, rollback, delete, clean, install. No result. Then I went for Windows updates, installing the latest updates, then uninstall up to the last day, when LR CC worked. No result.  Then I did   sfc /scannow system integrity check, it did not find any problems.    At the end I found out, that:  The ADOBE CREATIVE CLOUD app is the reason. It is constantly getting corrupted. Even it is corrupted, the app runs, does n

I have an issue with LR using almost all GPU memory, impacting Photoshop performance. Once I switch to LR Developer module, VRAM usage goes through the roof and the PS interface becomes sluggish. For instance, opening a new document in PS is slow - and the new empty document will shortly show a part of the photograph I've opened previously. Zooming is slow and opening a filter like NIK becomes extremely slow. During the slow performance PS is even briefly showing status 'Is not responding' in the process list.   LR and PS constantly up to data via Creative Cloud. Windows 10 up to date, use constantly latest NVIDIA Studio drivers and have no errors or messages in event logs. No other issues. Screenshot of VRAM usage:     LR uses 22GB of the GPU memory. This amount seems rather unnecessary: LR performed about the same with my previous 8GB graphics card (of which LR used about 7GB, of course, and impacted PS performance the same way):      By closing LR, af

When attempting to export pictures to an HD slideshow video, I noticed that it completely fails to even begin the export at either 720 or 1080.  I am able to export at the lower quality settings, but the pictures are completely blurry.  I read a post that having portrait oriented pictures in your slideshow is causing the problem.  Sure enough, I create a slideshow 720 or 1080 video with only landscape photos and the export works fine.  I then try to create a slideshow 720 or 1080 video with nothing but portrait, and it hangs.  It did this is the version prior as well, as I was hoping the update would fix this.Here are my System Settings:Lightroom version: CC 2015.6.1 [ 1083169 ]License: Creative CloudOperating system: Mac OS 10Version: 10.11 [6]Application architecture: x64Logical processor count: 4Processor speed: 3.1 GHzBuilt-in memory: 16,384.0 MBReal memory available to Lightroom: 16,384.0 MBReal memory used by Lightroom: 2,202.4 MB (13.4%)Virtual memory us

So I am using the brush tool on some of my photos and after that I decided to use the spot removal tool. Upon doing so it removed more than the spot. It actually ended up removing separate brush strokes I have made. I am not sure how this is possible but please look into this. 

1. Editing an image 2. Create a virtual copy 3. Crop the copy 4. Adding a spot removal to the original 5. Synching spot removal from original to copy 6. Interrogate spot removal   Expected - spot removal over the same part of the image and sampling from the same part Actual - spot removal does not always sample exactly from the same place This is an example in which the shift is very slight, sometimes the sampling area completety change!   Bokeh ball removed by sampling just from next to it...   Image 1 (original)     Image2 (virtual copy of the original on which I use the spot removal)     Image3 (a cropped virtual copy of image1 to which I synch the spot removal tool from image2 - see the shift on the right)    

Today I found a new problem.After connecting my new iPhone 11 Pro with the iMac (Catalina) in order to import photos using LR Classic the application closed suddenly.After reopen LR I tried again and the message was "no photos found" !Using a SD card nothing happens but with the Iphone (iOS 13.2) LR close suddenly !Note: This conversation was created from a reply on: Lightroom Classic: Fails to import photos and stalls out on macOS 10.15 Catalina.

The Collections I'm syncing from Lightroom on the desktop are all sorted via User Order. When a Collection is synced to my phone the order is all over the place. Custom on the phone is apparently not the same as User Order. How do I get the custom order I've made on the desktop to sync and be the same on the mobile app?

Only half the width of the keywordlist is used to display the keyword. I use a hierarchical keyword list and at lower level keywordnames are cut off. Instead of for example "Flower" it is displaying "Flo...". I understand that if there is no room left, it has to cut of the name, but in my case still al lot of space is available. If i look at images of keyword lists others post, it seems that a lot more space is used to display the names. If i resize the width of the panel, i can see more of the keyword. At the smallest width only half the width is used for the keyword name and the other half is used for the count, which need in my case much less room than the name

LrC 10.2, macOS Big Sur 11.2.3 on iMac Pro w/ 64 GB memory and Radeon Pro Vega 64 16 GB.   After Import, and only after Import, access to the Map module, either via the pin on an image or directly to the tab, results in LrC instantly blowing out and presenting Adobe and Apple crash report dialogs. After recommendation of another Adobe forum's administrator to reset preferences and reboot, problem still exists.   Many crash reports submitted and should be available for analysis.