Bug Reports

In Lightroom CC (2015) when editing the mask for the gradients if I use the mouse wheel to change the size of the brush whilst zoomed into the image then it also scrolls the image up/down as well. This behaviour is different to the adjustment brush tool where the mouse wheel just changes the size of the brush.

In the Lightroom forum there have been a couple of threads where users are saying that they have tried to open the zip file that Lightroom created with the catalog backup. They say that the zip file is corrupt and won't open. I have tested the whole process of backing up and opening the zip file on my Windows 7 computer, and haven't experienced the problem. But it seems to exist. Has anyone else seen this?

When I select an MP3 file for music to accompany a slideshow, I get the message that Lightroom has stopped working properly.

Lightroom CC 2015 - I have a preset to set images to "RED" label on import. When the images import, they appear in Lightroom as "Red" but when I search or try to select the images it tells me that there are no "RED" labeled image there. I need to select the images and set them to RED again manually for them to truly be RED.

Lightroom CC: display width problem in Adjustments panels (gradient tools) where slider descritors in the French language use longer words then in English and extend the width of the panel, making the numbers on right side unreadable. Screenshot: look at the "Defringe" slider in French is "Supprimer la frange". No problem in English.

MAC Yosemite, LR 5.7 & 5.6, when I use trackpad gesture to pinch in or out (zoom in or zoom out) in the grid module, all of my photos change their aspect ratio (they become squeezed in or out) also the grid moves to the left of right and some of the photos are not visible, I have to scroll left or right - this never occured before LR 5.5 or earlier.

Cropped images unexpectedly change crop location.

You can't use the Parent > Child keyword notation when tagging faces -- LR will rename the child keyword to be a screwy name, and it can cause an internal error. To reproduce: 1. Create two parent keywords, Friends and Family. 2. Under each of those keywords, create the child keywords Peter and assign each Peter to a separate photo. The hierarchy now looks like: 3. Go to a photo with no keywords, draw a face rectangle, and enter "Family > Peter" into the person box. 4. LR incorrectly renames the keyword Family > Peter to be Family > "Family > Peter": Sometimes this can result in a LR internal error, "name is not unique", though I haven't been able to reproduce the exact steps for this to happen:

Face tagging doesn't correctly auto-complete hierarchical keywords. Suppose I have two keywords, Family > Peter and Friends > Peter. In the Keywording panel, when I start typing "Peter", LR suggests both keywords and lets me choose: But the person box above a face rectangle provides two choices, unqualified by the parent keyword: It doesn't matter which you click on, you'll always get Family > Peter. And you can't use the Parent > Child or Child > Parent notation -- see this bug report: http://feedback.photoshop.com/photosh...

Objects photographed against the sky or other blue coloured areas get a "halo" when images from Fujifilm X-trans cameras are developed in Lightroom. My camera is a Fujifilm X-T1. Before this, I owned the X-E series cameras and noticed the same thing with them. Today I installed the latest version of Lightroom (5.4) and the problem is still there. Lightroom doesn't handle blue coloured areas well. Take a look at the blue and red traffic signs. You may need to click the images to view them full size (they are 100 % crops). Compare this with the same raw file developed in Capture One: Things photographed against a blue sky get a soft "halo": Looking at the red channel only shows this clearly For comparison, the same image in Capture One

Product: Lightroom 6 (not CC) on Windows 7 64-Bit Bug. Attempting to start LR6 with a DISABLED network connection results in a hang that does not clear even after reboot. The only solution I've found is to remove a .slc from C:\Program Files (x86)\Common Files\Adobe\SLCache. This forces re-registration of the product. The desired behaviour should be the same as removing the network cable. This lets LR6 carry on working without a internet connection.

LR 6: Cannot enter negative values e.g. for lighting in Development (e.g., -1,0); sets always to zero. Works if I just move the slider; positive values ("+1", "1") work also. (MacOS 10.10.3)

With the final release of LR 4.1, using the + and - keys within the Develop module to adjust exposure no longer work. They appear to work, in that the app throws the expected dialog ("increase exposure +.10" or similar) and this action is recorded in the history panel, but the exposure slider on the right does nothing, and the expected result (up or down exposure) on the image never happens. With the + and - keys, you can send the exposure up or down 4 stops, per the history and the onscreen pop-up, but the adjustment actually never happens. Only when you use the mouse and drag the exposure slider up or down, does exposure actually adjust. This is a tremendous workflow hit when you have thousands of images you want to make minor exposure adjustments to, and have to keep reverting to the mouse. Everything worked fine (in this regard) in 4.1RC, and every version prior. 2010 Mac Pro 24G memory Lion 10.7.4

I've found a solution to a problem many others seem to have reported - but it does involve a work-around, suggesting the Adobe Photoshop Lightroom team need to fix a bug. When a large number of Develop Presets are loaded into Lightroom (in my case, over 500), the Library Module, and strangely, to a lesser degree, the Develop Module run very slow. Having performed some troubleshooting, I discovered the reason for the slowness was a CPU spike. On my iMac 3.4GHz with 32Gb RAM, NVIDIA GeForce GTX 680MX with 2GB, and 1TB Fusion Drive, the CPU would go over 100%, while the disk and memory allocations were low. I run Mavericks 10.9.2, so it's not a matter of an out of date OS. This occurred whether I had 10 images or 10,000 images in the catalog (I tested various scenarios). I read on a forum that the number of Develop Presets could affect performance, so deleted the majority of them (backing them up first) to see if it would make a difference. I reduced the number of presets to less than abo

Using the new 2012 process in Lightroom 4, the auto tone adjustment function does not work properly. Most images come out strongly over or underexposed.

LR 4.4, OS X 10.8.4 After the infamous facebook Tuesday night update the Facebook publish plugin no longer works. LR will not display a fb album list, cannot create albums or publish new photos to existing albums. Editing Collection settings will no longer authorise and returns error "Can't save changes: Authorizing" Sometimes states error "Cannot retrieve facebook album list", plugin also fails and needs reloading, diagnostics file contains : Plug-in error log for plug-in at: /Other App Links/Imaging/Adobe Apps/Adobe Photoshop Lightroom 4.app/Contents/PlugIns/Facebook.lrplugin **** Error 1 An error occurred while attempting to load this plug-in’s portion of the Export dialog. ?:0: attempt to index upvalue '?' (a nil value) I have reloaded an earlier backup of the plugin to make sure it was not corrupted. Several users have posted about this error on the Adobe community forum http://forums.adobe.com/community/lig... Removing authorisation and plugin from fb does and reauthorising does

Just installed Lightroom 5 final. Output Sharpening and Noise Reduction does not work. Whole story here: http://forums.adobe.com/thread/1229132

Full Screen Preview (F) works incorrectly with selections when invoked from Grid view (G), though it does work correctly when invoked from Loupe view (E). Full Screen Preview should work just like Loupe view (and it does, when invoked from Loupe view). To reproduce: 1. Go to Grid view. Let’s call three consecutive pics A, B, and C. 2. Select A and B, with A most selected. 3. Go to Full Screen Preview; the most selected (A) is displayed. 4. Click right-arrow. Pic C is displayed, even though it wasn’t selected. 5. Go back to Grid view and notice the original selection has been lost; just C is selected. With Loupe view, right- and left-arrow cycle among the selected photos, and the original selection is not changed (only the most selected). Full Screen Preview should work the same way. And if in the recipe above, after selecting A and B, if you first enter Loupe view and then Full Screen Preview, left- and right-arrow work correctly, cycling among the selected pics A and B. See here for a

Hi, during the last days I created about 50 HDR/dng files (Canon 5D3, 3 images merged) using the new LR CC HDR Merge function. Now, after the merge, when I edit the dng file (22 MPixel, 85 MB) LR slows down extremely. The main performance issue is not changing the sliders but waiting until the image is rerendered! After a development change it takes often 10-20 (!) seconds until the image is rendered. In library module, mostly I have to wait 20 to 40 seconds until a preview is rendered. Often I wait forever and the preview is NOT rendered. Then I have to restart LR and then again have to wait 20-40 seconds until the image is rendered. During rendering about 50% of a i7-3770 CPU (i.e. 2 cores are fully loaded!) are used. Sometimes the CPU load goes up to 100% (i.e. 4 cores are used!) during rendering the image. Below is an example of the load while rendering a preview for more than 2 minutes. The worst case is using the compare mode in library module. When comparing 2 HDR/dng files, I h

Works ok if played from slideshow module, but not impromptu.. win7/64 More info here: http://forums.adobe.com/message/6037135 I'm sure this problem was introduced long before Lr5.4, but Lr5.4 is the first revision with a slideshow feature worth using (due to color/tone bug - thanks to Adobe for fixing) so... Is there any way to manually advance a slide without a trip to the slideshow module?

LR 5.0 on a Mac (tried both Mac Mini, MacBook Pro and MacBook Air - all running 10.8.4). When I run a slideshow and pause it, the arrows keys to go backward/forward are not working. Created a "testuser" account (so no LR prefs that have been inherited) and copied over a test catalog. Same issue. Also installed it on work laptop where I've never used LR. So no old "cruft" on account or inherited. Same issue. I use the slideshow module to pick/rate/flag and therefore have paused and gone back and forth while the slideshow was paused (e.g. to change rating on previous photo), then resume. Bug? Workaround available?

Still broken in Lightroom 5.4 on Mac/Mavericks. When running a slideshow, the left/right arrow keys do not work to go back and forth in the slideshow. Though I am glad to see you finally fixed the color profile problem on slideshows.

i have the option to automatically save XMP data into the images activated. so all keywords and metadata changes are not only saved to the catalog but also into my DNG and TIFF images. now this works fine for everything except the new face recognition data. i mean the areas (rectangles) where the faces are. i guess the problem is that the images already contain the keywords (names) of the persons in the images. what i did was using the rectangles to identify the persons in the images. drawing rectangles around their faces and name them. this info about the rectangle positions is NOT automatically stored in the image files. not after hours of letting LR run idle. this info is only stored when i manually save (CTRL+S) the images or do something other to the metadata (like adding NEW keywords to it). so in short: just adding the face region data (the rectangles) will not trigger the automatic XMP save function when the name keyword was already asigned as keyword to the image. that ́s very

Hello, some problems with NR not applied if image size < 1/3 of original were apparently solved in 5.2, but in some cases NR is still not applied. Please have a look at attached images, they are both exported with exactly same settings, the only difference is, that there is a crop applied on cropped.jpg version. Please notice the difference in overall noise. Please solve this problem as soon as possible, this has a big impact on image quality if higher ISO is used. Please contact me, if original NEF or XMP is needed. I can reproduce the problem. It seems, that it appears only if some specific crops are used. Thank you. cropped.jpg: not_cropped.jpg:

A smart collection uisng the criteria Collection and Publish Collection doesn't always update its results properly in LR 4.4 and LR 5 Beta (Windows 7 64-bit). Here's how to reproduce: 1. Create a Flickr publish collection named "test 1" with 1 photo. Create a collection named "test 2" with 2 different photos. 2. Define a smart collection named "Collection test" defined as "Match all", "Publish Collection contains test". Observe that it properly selects the 1 photo in the Flick publish collection "test 1". 3. Edit the smart collection to instead use the criterion "Collection contains test". Observe that it continues to select just the 1 photo in the publish collection "test 1", not the 2 photos in the collection "test 2". Here's a screen shot: