Bug Reports

After last update to Lightroom CC 2015.4 (in Spanish, on Mac OS X El Capitan in Spanish), when importing photos using dates to create folders, the names of the months are in English, messing all the previous folder structure (previous versions of LR used names of the months in Spanish). Happens the same after uninstall / reinstall with clean preferences.It seems a bug in new LR 2015.4

In Lightroom 5.x after the same action CTRL+ALT+S worked Lightroom version: CC 2015.3 [ 1052427 ] License: Creative Cloud Operating system: Windows 7 Version: 6.1 Application architecture: x64 System architecture: x64 Logical processor count: 8 Processor speed: 2,8 GHz Built-in memory: 6135,0 MB Real memory available to Lightroom: 6135,0 MB Real memory used by Lightroom: 1690,9 MB (27,5%) Virtual memory used by Lightroom: 1774,2 MB Memory cache size: 764,2 MB Maximum thread count used by Camera Raw: 8 Camera Raw SIMD optimization: SSE2 System DPI setting: 96 DPI Desktop composition enabled: Yes Displays: 1) 1920x1200 Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No Graphics Processor Info: Check OpenGL support: Failed Vendor: NVIDIA Corporation Version: 3.3.0 Renderer: GeForce GT 610/PCIe/SSE2 LanguageVersion: 3.30 NVIDIA via Cg compiler Application folder: C:\Program Files\Adobe\Adobe Lightroom Library Path: T:\L

Just updated to the newest lightroom cc version and now the sliders in the develop mode do not respond to small slider adjustment clicks in either direction. I can move the slider in small increments all the way to either end with no change to the image I'm editing. I have to either use the + - keys or click very large increments.

Lightroom 6 users the old font which results in too small menus under OS X 10.11.

Lightroom CC 2015.4 locks up on my iMac running MacOS X 10.11.3. I had to force quit the application. I've tried several solutions, like uninstalling and then installing the stand-alone installer and the 6.4 updater, and uninstalling and installing LR CC2015.4 from the CC app, but nothing seems to work. The update runs fine on my MacBook Air with MacOS X 10.11.2, so I wonder if it's the combination of both updates that causes the problem.

After installing the 2015.4 update today, I can no longer scroll through images in Loupe view with the mouse. Keyboard scrolling via arrows works, mouse does not, to go from one image to another. Scrolling in the Grid view works fine. I tried two different mouses to make sure. This has never happened in any of the previous versions on the same computer. Any ideas? Thanks

In LR6 if I use the straighten function and make a crop after that and try to straighten again, the crop will be reset. This is very frustating. In LR5 this works fine. If I make a crop at first and straighten after that it woks as expected, but not if I straighten the picture as the first step.

Software bug. MAC OS X Yosemite (and Mavericks before it). Using LR 5.6 & Photoshop CC2014.2.1 CC subscription. When an external firewire backup drive is connected (the backup drive is a clone of my MacBook Pro that stays connected for scheduled automatic backups, etc.), when I am in Lightroom and I select "Edit (an image) in Photoshop", Photoshop opens in the wrong location. In other words, it opens the Photoshop application on my backup drive instead and I get a warning dialogue box that says "The application has been moved, and its path has changed. To update the product configuration, click update". I have a choice to update or not. Of course, I choose to not update that. That's a bug (in my opinion.) When the backup drive is not connected the correct PS 2014 application opens. Bottom line: I should be able to keep a backup drive connected and have the Edit in Photoshop open the correct application. One way you could easily solve this issue is to change External Editing in Pref

Under Lightroom 6 on Mac OS X 10.11 El Capitan (GM seed), the keyboard shortcut for the Find command and the Full Screen command swap places after 30 seconds. Lightroom has always used Command-F to be the Find command. When I first launch Lightroom and I click on the Library menu, I see "Find (Command-F)" and under the Window menu, I only see "Full Screen Mode". Pressing the command key shortcut engages the Find command as I was used to. After about 30 seconds, the keyboard shortcut mysteriously and silently switches places. Now, when I look under the Library menu, I only see "Find" and under the Window menu, I see "Full Screen Mode (Command-F)" and pressing the key combination changes the Full Screen mode. I would love to see Lightroom return to the previous behavior of consistently engaging the Find function with Command-F because that is what I am used to. Thank you.

In my efforts to speed up LR, I've been building Smart Previews and then taking the RAW folder (24MP Nikon D750 DNG files) offline via folder rename. Works! But, when I select a set of Smart Previews and try to use Lens Corrections (ENABLE PROFILE CORRECTIONS), LR throws and error "File Not Found". It does work just fine with single image selections. Just not a group. LR ---does--- apply the lens corrections to the Smart Previews, but when I bring the full-size DNG back online, the lens correction is disabled. That's quite bad behavior! Mac 10.10.4 - LR 2015.3 - 480GB SSD - 32GB Ram

LR 6.3 resets crop after rotation. Step 1 - rotate picture via slider Step 2 - crop picture Step 3 - rotate cropped picture (via slider) -> crop removed! I use this function very often. In LR5.7 everything works as expected, in LR 6.* never. Here is what works: - Step 1 - crop Step 2 - rotate cropped picture (via slider)-> crop stays! But: Step 3 - crop refinement Step 4 - rotate refined crop -> crop reset to former state! - Also using the crop frame corner to rotate arbitrary does functioning correctly. Often when you make crop refinements (off center) you have to adjust the rotation angle because of the different perspective due to off center cropping. Why Adobe ignores this bug so persistently. I prefer to use the slider for rotations instead of direct rotate using crop frame corners.

If I'm in Lights Out mode and I choose undo or redo from keyboard, the image disappears. Sometimes doing multiple undos will bring the image back or hitting the spacebar to zoom will also bring it back. Using lightroom 6.3 and OS X 10.11.1

Lightroom 6. (Standalone) W8.1 Pro. Hp, intel i7 3.3 16g mem. 1. Pressing F locks lightroom in full screen. Only way is out is using task manager to close lightroom. Tested on two different computers, same results. 2: Playing video in full screen mode, locks up lightroom, video does not scale correctly. Test on two computers same results.

Entering Slideshow after selecting a few pictures gives me a black screen and a wrong preview, see atached picture. This happened after upgrade to LR5 earlier this week and was not a problem in any version of LR4. I have tried with both NEF and DNG files.The only thing working is Export to PDF. I am running a Dell Studio XPS with Windows 7 64-bit and ATI 4850 graphic.

The default extention used in Lightroom is a .jpeg extention. The default for PhotoShop Express is .jpg and niether application allows a choice. When using the "share" function to post on social media sites, the .jpeg file type will not post to Tumblr but does not does not return an error either. It would help if the user could have the choice of file types or just change it to a .jpg in the code.

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