Bug Reports

In Book Module, when selecting Large Landscape, Hardcover Dust Jacket, The penultimate page template in the drop-down menu looks wrong. The front and back cover layouts appear to have been switched. From the POV of design aesthetics, a more pleasing layout is: Front Cover - Large Photo and text Back cover - Medium photo and text Inside flaps - Small photo and text The corresponding template for Standard Landscape, Hardcover Dust Jacket has exactly the above described layout which I really want to use for my Large Landscape book. Could this be fixed for the next release?

The LR Flickr publish service in CC 2015.2.1 / OS X 10.10.5 is causing Flickr to handle improperly multi-word keywords. For example, if you publish a photo with the keywords "Peter Ellis" and "Lake Powell", Flickr will show four keywords attached to the photo: "Peter Ellis", "Peter", "Ellis", "Lake Powell", "Lake", "Powell". This is incorrect. However, these methods do not exhibit the incorrect behavior: - Publishing to Flickr with CC 2015.1.1 and the LR Flickr publish service. - Publishing to Flickr with CC 2015.2.1 and the Friedl Flickr publish service. - Exporting to the desktop from CC 2015.2.1 and then uploading to Flickr via the Web browser. All these methods result in Flickr showing just the keywords "Peter Ellis" and "Lake Powell". Thus, the bug is specific to the Flickr plugin in CC 2015.2.1. In all cases the export settings were the default plus these: Include All Metadata, Remove Person info unchecked, Remove Location Info unchecked, Write Keywords As Lightroom Hierarchy che

I have found a bug found in Lightroom 6. When I use the adjustment brush, I use the ‘show selected mask overlay’ feature but with Lightroom 6 it is hardly visible when you make an adjustment. Very very pale pink. With Lightroom 5 it was much more visible. If I go to adjust an existing photo I altered first in Lightoom 5 and open it in Lightroom 6 the mask overlay is much deeper pink but as soon as I brush on more adjustment, what ever I add shows as pale pink. The problem happens when I use a Wacom tablet or Wacom mouse. I have just had a chat to Victoria Bampton and she just reproduced the same problem with her Wacom tablet. With her Apple trackpad though it worked fine. I am using Yosemite 10.10.3.

Lightroom 6; The color picker for the brush/gradient dropdown will not pick a color off the photograph, only from inside the color box. Works fine with 5.7.1.

I have Lightroom 6.2 on a Windows 10 machine with a 4k monitor, set to 150% scaling. Whenever I drag & drop a photo (or group) onto the map module, the item is placed below and to the right of where I dropped it. It _looks_ like the drop location is being scaled by about 150%, relative to the top-left of the map pane. Existing items appear to render in the correct location on the map, and mouse interaction with the map appears to work as expected, so this problem _seems_ to be limited to drag & drop.

i found this problem report elsewhere and over 3 months without answer. I have the same problem. I have Lightroom 6.01. The Duplicate Published Smart Collection feature does not work. Whenever I right click on a Published Smart Collection to invoke the Duplicate... command, I get an error message each time I attempt to do this. The error message says "An internal error has occurred. Assertion failed."

I've had this happen a few times since Lr3.4RC (or at least I don't recall it happening with previous versions) - I thought it was me, but this time all I did was click a thumbnail and it switched from portrait to landscape orientation.

SInce 2015.2 update, I'm getting Internal Error message every time I open gradual filter or radial filter tool, with buttons Show Details/Crash/Continue. With continue, it works, but this is still unbearable. Running on Mac OSX 10.11. I've tried reseting preferences and re-installation. Here's the exception as outputted by Show Details button. Exception Name: LuaRunException Description: bad argument #1 to 'find' (string expected, got table) User Info: { LuaErrorCode = 2; } 0 CoreFoundation 0x00007fff96cd5bd2 __exceptionPreprocess + 178 1 libobjc.A.dylib 0x00007fff882754fa objc_exception_throw + 48 2 CoreFoundation 0x00007fff96cd5b19 -[NSException raise] + 9 3 AgKernel 0x0000000104dd964f AgTransitQueue_enqueueToQueue + 3962 4 AgKernel 0x0000000104ddd2ca AgExceptions_setThrowHook + 230 5 AgKernel 0x0000000104dc115e lua

Hello Just did my first import....but after import finish in Library all previews/thumbnails show BLACK, see imagine. I have ReSync'd even Exit out then come back and Previews not showing. All other folders are OK, just not the NEW import. Checked with Actual folder on MAC Finder and these ok. Any ideas?

When entering names on Unknown faces, it seems far too easy to change the case of a name. In almost all cases I use, the first letter is capitalized. When entering a new label it seems that by mistake, it is all to easy to change the case to all lower case. If as can happen the labels applies to 1000 images, then these all show up as "Changed in catalog" and require saving. If you do not notice immediately, then they need to be re-saved later when you notice the change and then correct the error. This is a massive waste of time and backups, as each change not only is reflected in the original, but in all the backup versions as well

Perform the following steps in this order. Library module Select an image Choose export Set resize mode to long edge Set inches and enter 12 for size Set pixels per inch Enter 300 for resolution On Windows 8.1 64bit I get the following error: Invalid constraint size. Must be a number between 1 and 217. Closest value inserted. This only happens when I try to change ppi in long edge or short edge mode. Other modes work fine. Also if I switch from inches to pixels I can set the ppi to 300. If I then switch back to inches the 300 value will stick as long as I don't attempt to change it.

When croppin in "Dim The Lights" or "Lights Out" modes, closing the crop tool while still in the develop module makes the entire screen, including the image, go dim or black, respectively. System Information: Lightroom version: CC 2015 [1014445] License: Creative Cloud Operating system: Mac OS 10 Version: 10.10 [3] Application architecture: x64 Logical processor count: 4 Processor speed: 3.2 GHz Built-in memory: 24,576.0 MB Graphics: NVIDIA GeForce GT 775M 1024 MB

Faulty Script in Web Module of Lightroom CC 2015.1 There seems to be an error in one of the Scripts ( jquery.min.js) which is used by Lr 2015.1 to build Web Galleries. If a user types the URL of their web site into the “Gallery Author URL” box; and a visitor to their Site then clicks on the Link, a 404 “Not Found” error page is triggered. You can see an example of this if you go to this Page: http://shelbourne-america.net/Tigers-... and then click on my name: Instead of transmitting “http://shelbourne-america.net” the script instead triggers this triple-field URL: http://shelbourne-america.net/Tigers-... which leads only to a 404 Error page. I find the Lightroom CC 2015 Galleries to be very disappointing in both their design and their functionality. Adobe needs to provide a far greater range of Customisable Settings for text layout and sizing; for spacing between thumbnails; for positioning and formatting of the Main Title and also Caption boxes. Most egregious of all?: There is no way

Lightroom CC writes JPEGs in an atypical layout that trips up other programs. While they appear to be strictly conforming to industry standards, the unusual layout has caused problems for at least two users: one who had problems uploading photos to real-estate services, and another whose own software tripped over the layout. LR writes the APP1 header as: TIFF header, 114 unused bytes, ExifIFD, IFD1, IFD0. Whereas Photoshop CC uses a more traditional layout: TIFF header, no unused bytes, IFD0, ExifIFD, IFD1. Here's an Exiftool dump of the beginning of a LR JPEG: And here's a dump of the beginning of a Photoshop JPEG: I've tested LR JPEGs with 12 Mac and Windows programs and 2 online services, all of which read them just fine: Mac: Preview, Photoshop CC 2014, ColorSync Utility, Firefox, Chrome, Lattice, Paintbrush, Safari, Word Windows 8.1: File Explorer Preview, Irfanview, Paint, Windows Photo Viewer Online services: Flickr, Zenfolio Even though LR's JPEGs may be strictly conforming,

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).