Bug Reports

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.

In a recent update, Adobe seemed to change the fonts in Lightroom Classic CC.  Now the font's when viewed (here in the keyword screen) don't appear to be aligned.  In this case, all of the fruits are listed under the keyword 'fruit', but they don't appear to be aligned or nested properly due to the font.  Same with food types, Chinese Food and Chestnuts aren't and shouldn't appear nested under Candy, but that's how they appear with the new font changes.       Here's another example: Photos to import is not under Pets, but appears to be due to the new font alignment or misalignment...    

LrC 10.2 is consuming memory at an alarming rate when Tethered Live Shooting is activated for Nikon cameras on Windows 10. It looks very much like a memory leak of huge proportions.   This problem is considerably worse for some Nikon DSLR camera models than others. Initially @Steve Martin reported this problem with his newly purchased Nikon D7500.   I tested with my Nikon D750, and although there was evidence of a slow memory leak, I couldn't reproduce the severe memory leak Steve was seeing on his computer.   After trying everything from resetting preferences to reinstalling LrC and trying on a different computer, Steve tried a Nikon D90 and found it was worse than the D7500.   I have a Nikon D90 which I could use to do testing and can confirm his problem on my own Windows 10 PC computer. Starting LrC 10.2 in Library Grid view with an empty folder selected, LrC soon settled into an idle state using the small amount of memory shown in the screen shot below taken aft

When converting a raw DNG file to a lossy DNG file from within Lightroom Classic, the setting "File Extension" is ignored. This setting determines whether the resulting file extension will be DNG (upper case) or lower case (dng).     With other types of raw files, it works ok. But with raw DNGs, the resulting lossy DNG file keeps the same case from the original file.   The only way to make it honor the File Extension setting is to uncheck the box "Delete originals after successful conversion". In this case, the correct case is applied, albeit the resulting file is altered ("-2" is added), and of course, one has to go and manually delete the originals if they are no longer needed. So it's just a workaround for a feature which I think is not working as designed in this specific situation.   In this video the problem is demonstrated (you have to pay attention to the "Filename" field in the Metadata panel after each conversion:   https://youtu.be/gM6LgxUJ4uM &nbsp

When choosing Crop tool there is a padlock symbol that shows whether aspect ratio is locked or not. When making the first attempt to crop any particular image the padlock symbol incorrectly shows as unlocked when the tool is behaving as locked.   This only seems to happen on the first attempt to crop a new image.  Whilst the symbol incorrectly shows as unlocked (even though aspect ratio is locked), just passing the mouse pointer over the padlock (no click required)  changes the padlock to correctly show as locked. Whilst incorrectly showing as unlocked (even though aspect ratio is locked), pressing the shortcut key A has no effect on the padlock symbol but does change the aspect lock to unlocked (so now the symbol and the behaviour matches). Subsequent use of the shortcut A makes padlock symbol behave correctly for that image. Once the initial incorrect view has been corrected (by one of the above methods), all subsequent behaviour on the same image seems correct. Open a

Me: Any clue why my newly built Lightroom preset - that has color grading selected when created - doesn’t actually apply color grading to images when selected? My color grading only presets work just fine, but not ISO adaptive ones. Adobe, fix this please.    From AdobeCare: Hi Dave, thanks for the heads up. Has this preset ever worked since you created it? Would you mind reviewing the process of creating an ISO adaptive preset in Lightroom Classic and see if that helps? See: helpx.adobe.com/lightroom-clas… Thanks, ^AK   Me: Thanks - this is a new one, so never worked. I have several other ISO adaptive presets (made before Color Grading) and they all still work fine (but with no color grading). I was finally getting around to making one with Color Grading included. I do have Color Grading only presets that work (not adaptive). Reviewing now   Me: Reviewed, that’s exactly what I did. Images from ISO 320/800/1600/3200/6400, checked that the only differe

Hi everyone,   I've just noticed odd behaviour after recent LR update on my Win10 64bit - I'm processing photos from 1 photoshoot, using nikon d700 and 50mm lens for all of them.   As conditions are the same, my workflow is to apply settings to first photo and then sync across rest of them so if I'm selecting multiple images and then sync settings either from Library or Develop module - that's great, working fine and as expected.   However, sometimes I'm doing manual tweaks and then I want to apply those settings to the next photo so what I'm doing is: in Develop mode, go to the next image and hit "Previous" button next to "Reset" - when this is used the image is getting marginally cropped (probably by 1pixel) even when previous image wasn't cropped at all.   This change is only marginal but alters the aspect ratio without user's knowledge and only indication is a small crop icon in the filmstrip thumbnail.   Thank youMarcin

Long term Lr6/LrC user. First time creating a slide show.   Added photos, mix of portrait and and landscape, into a custom template that shows the Title and Caption. Previewing works fine.   I added a music clip; LrC 9.4 froze  then the crash screen came up.   I've Googled this issue and it seems to be old. Any idea when it will be fixed?   Thanks

Hi, after updating to Lr classic 10.2 metadata like capture time, exposure, filename etc is not updating nor showing after I make a change from the list with right click just above or under the thumbnails in the grid view. Win 10, AMD Ryzen 9 3900X 12-Core, 64GB, x570 MB.

When I right click on the righthand third of an image, the background colour contextual menu comes up instead of the more general purpose Lightroom one that includes settings, export and edit in and such like. The mapping of where the image is on the screen seems out. If I right click to the left of the image on the background area it still behaves as if I've clicked on the image, i.e. I don't get the background contextual menu   Ive got right click on the rocker of the wacom pen, if I am viewing the image zoomed in the problem stops. Didn't notice this issue in previous Lightroom version.   Wacom driver 6.3.42-2, (screen area full, tablet are full, no to force proportions in wacom driver)  Windows Ink is turned on.   Lightroom Classic version: 10.1.1 [ 202101041610-8c69aa4e ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Business EditionVersion: 10.0.19042Application architecture: x64System architecture: x64Logical processor count: 32Proc

lightroom classic cc 8.2 (build 1204643) on windows 101) enable color label toolbar both in grid and loupe view.2) choose a folder with multiple photos3) from grid view add a color label to a photo4) press enter (or E or double click) on the labelled filein loupe view the previously labelled file has no label selected5) still in loupe view, press arrow right to select the next file and then the arrow left to return to the previous filethe labelled file now is shown labelled in luope view too6) press G to return to grid view7) remove the color label😎 press enter (or E or double click) on this filein loupe view the file is still shown as labelled9) press arrow right/left (one or more times)all the pictures are shown as labelled (even if they are not)

Win 10 1803, LR  8.0, I7 8700k, 64GB ram Control keys inop. Most functions in Edit, Image, Layer, Select anf Filter grayed out. Images opened directly into PS all ok. Reset prefs no help.

The problem is created when syncing the pictures from Lr Classig to Lr Mobile. During that process they will get an "upload time / create time", but as Lr mobile sort them according to the capture date you will not see this problem until you create a web gallery. There they are presented in the same order as they were uploaded to Lr Mobile!   The work around is to update the sort order in the web gallery to capture date.    As soon as the support representative and I understood the reason for the problem she said that this will be corrected soon!.   This item is reported as Adobe Case ADB-19651987-L9V5

When I use Lightroom on Russian language export menu is cropped on the right side. I use the last version of Lightroom Classic on iMac 21.5 2017 and MacBook Pro 13 2017. 

In LR 5, the image in my second monitor renders blurry as if the photo is out of focus although the image is clear as a bell in the main editing screen. If I click off lens corrections, and then reactivate it, the second monitor window clears up and renders the photo clearly.

It has become painfully slow in Mac Mojave when I press “F” to view previews in Full screen. Takes about two secs to switch between pics, even if previews already exist. It goes instantly to switch between pics in Loupe mode. Tried turning graphic processor on and off, without significant difference. (On an 27" iMac 4 GHz Intel Core i7 24 GB)

I had upgraded to v10 of Lightroom Classic, and now this is extremely slow. On top of this, most time it crashes entirely, especially when I am starting Lightroom for a second time without restarting Windows (as in I close Lightroom, and restart some time later).   I have noticed that this issue is less frequent when my machine is on mains power, and wondered if this was also an issue with power profiles. The Better Performance profile is definitely less issue prone on v10, compared to the Better Battery profile which is the default.   I have tried downgrading to v9.4, but of course now my catalog files are not compatible with earlier versions, and I do not want to lose images I have imported since.   I would be grateful for help with this, as I am effectively stuck without my most used software at the moment.

Copy or sync crop and spot removal develop settings causes wrong results at portrait photos. The crop and spot removal settings are wrong by 90° after copy/paste or sync.   Here an example photo to reproduce. - Importing in Lightroom Classic 10 - Create a copy by edit in Photoshop  - Make a small edit, e.g. add text "Photoshop edit" and save. - Add a crop and spot removal e.g.   - Copy or sync the crop and spot removal develop settings to the same/original photo before the edit in Photoshop. But the result of the crop and spot removal is totally wrong:

Hello,   Since upgrading to Lightroom Classic v10.0, all UI-related functionality is painfully slow. All editing functions are working correctly and quickly but scrolling through the catalogue or even scrolling a side panel is taking many long seconds to refresh. Unreasonably long.   Disabling GPU Accellaration has no affect on my Lightroom's performance.   macOS Mojave 10.14.6 Mac Pro (Late 2013) 3 GHz 8-Core Intel Xeon E5 32 GB 1866 MHz DDR3 AMD FirePro D700 6 GB  

On macOS you can have the Secondary Display visible whilst you are cropping to you see a full screen view of the current crop boundaries.   As you adjust the crop bounds rect the secondary display should show a real time update of the crop.   This seems to only work up until the first pause point but then doesn't continue to live update.   1. Drag bounds 2. Pause, mouse still held down 3. Continue to drag bounds   You will see that there is a point where the second display stops responding to mouse drag events.

The boolean criterion "depthMap" for catalog:findPhotos() doesn't work. It always returns an empty array, for both "isTrue" and "isFalse".

When I try to import video files into my catalog it tells me "There is a problem with the video file (12)".  There is no issue with my video files.  I removed a video that had previously been imported to my catalog with no issue and tried reimporting as a test and it would not import.  I received the same message.  I created a new catalog to test and same message and video would not import.  This is a recent issue as i have been able to import videos with no problems.  The issue is occurring on both my Mac Book Pro and my Mac Pro.      

Please get dynamiclinkmediaserver under control. It hogs huge amounts of processor even when no Adobe apps are running. All I can do is to keep removing the dynamiclinkmediaserver folder from Application Support. But then it gets regenerated when I run Lightroom Classic CC

Hi, By simply launching the latest Lightroom Classic (9.3), it will set the shared media caches locations for Premiere Pro, After Effects, Audition and Media Encoder to the default Lightroom video cache location. /Users/{USERNAME}/Library/Caches/Adobe/Lightroom/Video Even though Lightroom's own media cache location might be custom set to something else.  Running the latest app versions available on MacOS Catalina 10.15.5 Does this also mean that the rather small cache size limitations usually set in lightroom now apply to the video editing apps shared cache too? Will Lightroom also delete cache files from Pr, Ae, Au, Me ? This bug has been reported for years. It's been marked as solved before by suggesting newer versions would not show this behaviour. Well its still here, I guess someone has to really look into this. @Adobe: Could you please provide a workaround, if there is one, for the time being until this gets eventually fixed? CheersAndi