Bug Reports

I notice than when a collection is removed from Lr mobile the collection is properly removed from Adobe Lightroom but the corresponding photos in desktop Lr continue to show the Synced with Lightroom mobile badge. This is misleading because, in fact, the photos are no longer actually synced -- they were removed from Lr mobile! I also notice an All Synced Photographs "collection" in the Catalog panel of the Library module. Recall that I have removed all collections from Lr mobile yet desktop Lr still show a sync badge on the photos and the All Synced Photographs collection contains the photos that were previously synced. I have also signed out of both mobile and desktop and then signed in but the All Synced Photographs remain and the photos still have the sync badge. I have even removed the collection that was used for syncing in desktop Lr but the sync badges and All Synced Photographs remain. Even more perplexing if you click the sync badge Lr asks to save metadata to disk. If you the

In the Slideshow module, I select Add Text Overlay from the Slideshow menu. Underneath the photo, I select Edit to customize the text overlay. I add theese fields: Image # (01)-Filename-Image # (001)-Total # (001). The Text Overlay is correct on screen, but when I export the Slideshow from the menu Slideshow, Export JPEG Slideshow, all fields show the same data - total numbers of photos in the slideshow.

The preview works correctly except that the intro screen is never displayed during preview and occasionally is swapped with the ending screen, however, the main issue happens when you press "Play" and the slideshow appears on the selected monitor, it stays there after any interruption of the show and even upon completion. Changing modules does not clear the display. Only exiting Lightroom. Also, if you stop the show, make a change and start it again, there is occasionally a dialog box that is displayed behind LR which requires the program to be stopped through the Windows Task Manager because LR is waiting for the modal dialog to be satisfied. I am running an ATI Radeon 6800 HD (2GB) PCI-E Display Adapter with the latest drivers on Windows 7 Premium with the latest service packs and all updates on a Quad Core AMD FX PC with 16GB RAM. This issue did not exist with LR 5.7. Thanks!

Lightroom 6.0 slideshow (Windows 7)- when exporting slideshow as 1080p high quality video - some of tiff images rendered as swapped blocks - i.e. bottom left 1/4 corner of the picture shown at the top left and vice versa.

Crashes when i try to insert an mp3 music file in slide show under Windows

When the export options Remove Person Info and Write Keywords As Lightroom Hierarchy are selected, Export To: Hard Drive mistakenly includes a person keyword in the field XMP:HierarchicalSubject. LR CC 2015.1 / OS X 10.10.3

I had Lightroom 5.7 installed when I downloaded Lightroom CC ( Windows 8.1) and when I used my card reader it defaulted to 5.7 for loading files. I uninstalled Lightroom CC and all works well except that if I put a card in my reader and lightroom CC is not on I get a fault message to say that the program cannot be found. I have this correctly selected in preferences.

I was also excited with the news of this release, UNTIL I found that both LR and ACR seem to have a bug where images taken with a D810 camera don't have the option of Adobe Standard camera profile. It is missing from the Camera Calibration list, and images already edited with it get converted to the next profile on the list - Camera Flat. NOT what most of us with D810s want! Win8.1 Bob FrostNote: This conversation was created from a reply on: June updates to the Creative Cloud Photography plan.

Lightroom CC Quick Develop When I make any changes to a file (D800 NEF) in Quick Develop in Loupe view, I get a message "Loading" for about 4-6 seconds (forever) before the change is rendered. In LR 5.7, the same thing takes less than a second. Fresh install of LR CC. System Preferences reset to default, just to be sure. "Use Graphics Processor" enabled (no difference when it is disabled) MacBookPro 2014 fully loaded (i7,16GB,1TBssd) OSX 10.9.5 No other software running. This makes "Quick Develop" largely unusable! Please fix, ASAP. Thanks. The new GPU assisted speed in Develop module seems to be working fine, is appreciated, and is getting closer to how it should be.

Lightroom 6 often writes invalid XMP metadata in exported JPEGs, including for photos containing lots of brush strokes made with the adjustment brush. This trips up Google Photos, preventing it from showing any of the EXIF metadata. It may well trip up other software. To reproduce: 1. Start with any image. 2. Use a small adjustment brush with Exposure = 100. 3. Make lots and lots of brush strokes (see the example pic below). 4. Export the image as a JPEG, including all metadata. 5. Load the image to Google Photos and observe that it doesn't show any EXIF metadata. 6. Delete all of the XMP develop settings with: exiftool -xmp-crs:all= file.jpg 7. Upload that modified file to Google Photos and observe that it now shows the EXIF metadata. Here's an example pic exported from step 4: https://dl.dropboxusercontent.com/u/2... If you extract the XMP metadata with: exiftool -a -m -b -xmp file.jpg you'll see that LR has recorded all of the develop settings twice, including all the brush strokes.

I can make Lightroom 5.7.1 on WIndows 7 (64bit) crash in a repeatable way; I even have a video demonstrating it: In the development module go to the manual lens corrections. The press the left mouse button on the numeric field to rotate the image. While holding the left button, press the right button (by mistake). A dialog pops up that you can cancel with ESC. Then there's a numeric input in the field, and it still has input focus. Press ESC to cancel the focus. Now try to undo the partial rotation (because your're a perfectionist) by pressing Ctrl+Z. A short pause, the Lightroom is dead. It happened to me a few times (in 5.7.0 also), so I made a video (WMV, 2MB).

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