Bug Reports

I have just installed the 2015 CC edition of Light Room but am having problems publishing and exporting photographs. When either exporting to hard disk or publishing to FlickR, I'm getting 5 or 6 random, all white images.

I recently wrote a new plug-in for Lightroom and in doing so initially created a password_field that is taller than one line (height_in_lines = 3 in my case).On a Mac, that password_field behaves just as it should: the content is obscured by round dots, and it cannot be copied into the clipboard.On a Windows, though, to my horror a password_field with height_in_lines > 1 turns the field into a regular multi-line edit_field: the content is visible in plain sight, and it can be copied into the clipboard. This is a serious security flaw.Granted, most password_field boxes are only one line high so perhaps this is an innocent oops, but I was certainly surprised to discover the difference between Mac and Windows.Another minor nit is that the password_field on Mac can have a placeholder_string, but on Windows that placeholder_string is obscured as hashes. Duh!

When I see EXIF data for HDR images that Lightroom created, it's based on the darkest exposure of the source images. I think the middle exposure (or next-to-middle if an even number of bracketed shots) is a more appropriate reflection of the shutter speed/exposure time.

In the German help screen that pops up if you open the "reference view" ("Referenzansicht" in German) for the very first time, there are \n\n characters which presumably should mean that there should be a line feed, see screen shot below.

I am running OSX El Capitan and 50% of the time Print to File fails to export the file. Have to try a second attempt which is always successfull. I don't get any error message (also export progress bar is ok), it just does not save the file in the chosen location. I can also predict when it fails and when not, the "Save as" window in the Finder is slightly different. Am I the only one with this issue?

tethered shooting performance (download) is painfully slow, despite using usb 3.0 and fast computer with tons of memory, Capture One Pro is 5X faster. When is Adobe going to fix this issue? More and more portrait/headshot photographers such as me are shooting tethered and we shouldn't have to move to Capture One Pro in order to get decent performance. Nikon D800E, fast Windows computer (i7) with 24GB memory, Windows 10, USB 3.0

In the book module one can enter different fillings (whited border) for each side of the foto cell (left, right, up, down). However, when I later enter that cell again, Lightroom checks all the small boxes to connect each of the fillings. When I then uncheck any of the boxes, Lightroom resets all fillings to one of the values. Very annoying, please fix this.

Since updating to LR 2015.7 and Macs OS X Sierra, the badge numbers in the grid view are no longer visible no matter what view I choose (expanded, compact, etc.). For good measure I recalibrated my display and that doesn't make a difference. This is not a problem for 2015.7 using other machines running El Capitan and Yosemite.

The following expression fails when called from an LrExportServiceProvider script: LrTasks.pcall (LrFileUtils.exists, ".") It generates the error "attempt to yield across metamethod/C-call boundary". This makes my Debugging Toolkit difficult, if not impossible, to use with an export service.  (The toolkit uses LrTasks.pcall() to catch errors, and it uses LrFileUtils.exists() to implement a more useful require().)Tested in LR CC 2015.8 / OS X 10.11.5.To reproduce the bug:1. Start with a copy of  "ftp_upload.lrdevplugin" from the "Sample Plugins" folder of the Lightroom SDK 6.0.2. Insert these lines at the top of "FTPUploadServiceProvider.lua": local LrFileUtils = import 'LrFileUtils'local LrTasks = import 'LrTasks'LrTasks.pcall (LrFileUtils.exists, ".") 3. Try to export a photo with FTP Upload. The post-processing action is never invoked.4. Go to File > Plug-in Manager and observe that the plugin encountered an error:5. Comment out the lines inserted in step 2 and reload th

Identity plate looks pixelated in the slideshow unless "Render in Background" is UN-checked.Does not happen when you export to video.The bug was present in version 2015.7 and 2015.8 on Mac 10.11.6

I posted the below to the Adobe Communities > Lightroom > Discussions forum earlier today and an MVP suggested I post the problem on this forum because they, too, have the same problem.Occasionally I will create an audio file to accompany an image. That audio file is written to my camera's CompactFlash memory card in a wav format. In my workflow, I insert the CF card into my computer and open LR to initiate an import ofthe image as well as to rename the image using my own template (which is yyyy_mm_dd_HHmmss). Since LR1 and until sometime about 4 months ago, that workflow worked perfectly renaming both image and its accompanying wav file (giving both the same name) and placing both in the folder I designated during import. That enabled me to use LR to see which images had attached audio files by looking at the Library module's Metadata field entitled "Audio File" while I viewed the images as well as to playthat wav file by clicking the appropriate arrow in the Metadata panel. Dur

I am running the latest version of Lightroom CC (2015). I have a workflow whereby I export JPEG files from the Slideshow module, with text overlay '©[creator]'. Each picture has a different name entered in the creator field in the library module. The overlay '©[creator]' previews correctly in the slideshow, but on export the actual [creator] of the last file is shown on ALL the files.The only workaround I can find is to export one file at a time, which is hardly a time saver.Is this a known bug? Is there a solution?

I consider this a confising behaviour occuring sometimes maybe a part-bug:Scenario: In Loupe view, you can switch betwen photos using arrows. Sometimes, this operation is fast, but it takes around two seconds - the photo is shown immediately, but it takes some time till the UI is refreshed (Histogram, Metadata panel etc.), photo is redrawn in high res. etc. This is not the bug yet.The problem is: During this operation, you are already seeing the new photo, but the filmstrip below show the previous photo as selected. And if you press the "B" button to ad it into quick collection, the _previous_ photo is added into the collection. Although you are watching different photo. I found this very confusing at start, before I found I have to wait. But this bug hase been here for years and would be nice to fix it 🙂I have a Windows 10 on a very fast computer (i7 6700K, 32 GB RAM, nvidia GTX 1070).

Lightroom completely ignores the Microsoft IME for Japanese typing on a qwerty-keyboard.Normally one should be able to type in hiragana or katakana by typing in the characters as if romanized. The IME then converts them to kanas in automatically and suggests kanji. That's how in works in every application... Except Lightroom.In Lightroom, you can only ever enter alphabetic characters on a qwerty-keyboard. It doesn't seem possible to enter hiragana at all, with the Japanese IME enabled, active and working beautifully in every other application.First, I'd like to know why Lightroom ignores the IME.Secondly, please fix this VERY soon. This is a real crapjob for Japanese customers. And whomever incidentally has to enter some japanese text into their descriptions, such as myself.Tested on Lightroom 6.7 on Windows 10. UK English display language, UK English locale, Japanese IME on a Lenovo T450s laptop with US keyboard layout.

I recently upgraded to a 4k second monitor to replace a HD monitor. I did work through various type size issues discussed elsewhere, and the Library, Develop and Book modules are working fine.The Map and Web modules only partially redraw the main image window and are totally unusable.  GPU acceleration has no effect. Nvidia GTX 860M driving the 4K UHD monitor via Display Port.Looks like a bug of sorts to me.  Any ideas on fix or work around?Thanks!

On Lightroom mobile web (lightroom.adobe.com), if I click once on an image to zoom in it is no longer possible to move / pan around the image. This was working fine a few weeks ago.For me the bug occurs both in shared galleries and on the main site. I tested this with Firefox 50.0 and Chrome 54.0.2840.99.

When i choose "edit original" in Photoshop then the LR develop module doesn't reload the image after i saved the tif in Photoshop. But the library module DOES refresh. So i end up with different previews in library and develop. Only solution is to restart LR. After the restart i can see the current preview in develop module too. Steps to reproduce: - Open your raw file (i use dng) in LR. - Choose "edit in Adope Photoshop". Make some changes and save. Lightroom will automatically import the created tif file. Switch to develop module in LR - Now make another change in PS and save. - LR should detect that change to the tif file and refresh the preview. Maybe you need to switch to the next image and back to have LR refresh the image. But it should work. - Now close LR and PS. - Start LR again. - Select the tif file again, switch to develop module and choose "edit original" in Photoshop. - Make changes in PS and save. - LR will not refresh the preview in the develop module! But it will refr

I am receiving sync errors when creating tif files passed between Lightroom and Photoshop. I’ll detail the issues in the steps below but first my setup and some definitions: Using Lightroom 5.4 on Windows 7 64-bit and Photoshop CC 14.2.1 with latest Camera Raw 8.4 Using Lightroom mobile version 1.0.1 on iPad Air (32 Gb version) Lrd = Lightroom desktop Lrw = Lightroom on the web (lightroom.adobe.com) Lrm = Lightroom mobile app Ps = Photoshop CC What I did: Sync a collection of Lrd photos to Lrm. In my case I successfully synced 50 dng photos to the mobile app. Lrw also shows photos correctly. Pass a photo from Lrd to Ps using Lightroom’s Edit In command. In Ps add a text layer (or an adjustment layer). The intent is to have a simple way to make a visible change and have the ability to easily turn the layer on or off. Save the file (Ctrl+W) which automatically adds the new tif file to Lrd and automatically syncs to Lrm. All Lightroom instances (Lrd, Lrw, and Lrm) all correctly show th

With Lightroom 2015.7 on macOS Sierra (released today) the scrolling behaviour for changing brush sizes using the trackpad is very "twitchy".  It will jump from tiny to large with very small scroll movements.  All other scrolling in the OS as well as the rest of Lightroom is unaffected and works as normal.Areas of issue: - Adjusting size of spot removal tool - Adjusting size of the adjustment brushUnaffected: - Scrolling the grid view - Panning around the image with 2 fingersI've tried with the GPU on and off.Hardware:15" 2014 MacBook Pro with 16G ram and SSD (65% full).  2.2Ghz i7.Actual behaviour:The best I can do is describe it as twitchy.  In the previous version using the scroll action (two fingers on the trackpad moving up and down) the brush sizes would adjust in a smooth and linear manner.  The current behaviour has the size jumping (smoothly, no going from big to small with nothing in the middle) very fast from big to small or back.

Pressing the "^" Key in Lightroom (language English) on my Macbook Pro 13' (German key layout) running macOS Sierra produces an "Internal Error" because "Range or index out of bounds" prompting me to "continue" or "crash" Lightroom.Anyone else with this problem?

Export preset where you chose "Open in other application" and you have selected a droplet (I have a folder with many droplets) does not work, because the droplet utilized by photoshop is not the one chosen in the export preset

Right after doing the updates to the newest versions of both LR and PS on the same computer that all was working on, Edit it Photoshop command from LR does not work if Photoshop is not already open and running.  LR is unable to launch PS is the problem. I can manually launch PS while LR is stuck trying to send the image file and launch PS, and if I manually launch PS, it opens and receives the image from LR.  If I don't lunch PS myself, LR does not succeed in opening it and eventually error's simply saying that photoshop failed to open.

The lensprofile for the Zeiss Batis 2/25 is obviously faulty. The vignette correctiongoes either the wrong direction or is way too bright. It creates a sort of awhite vignette to the images. Who’s to address this issue – Adobe or Zeiss?

During import, most import settings have disappeared save for a couple. Strangely, import presets still apply the settings that are missing. This happens during Copy & Copy as DNG (my default choice).I'm running MacOS Sierra Beta and the latest LR available on CC.

I have created a NEW post because of the MANY other posts about this problem.I have seen several posts on the Lightroom forum and this Photoshop Family forum of the adjustment brush stops working.  Many of these were unsolved.   A recent post on the Lightroom forum has a REPEATABLE scenario to make the adjustment brush stop working. See here in posts #9, 10 and 11  https://forums.adobe.com/thread/2082068The scenario is as follows and as the forum post shows happens on Windows and Mac.Use the Adjustment BrushRemove any photo - chose Delete from DiskAdjustment brush stops working (no new pins, can't select old pins, nothing in history)Select Spot Tool and create random spot/heal and immediately delete spot/healSelect Adjustment Brush and the Adjustment Brush will start working again.This behavior is completely REPEATABLE.