Bug Reports

Yesterday I "upgraded" to the Lightroom Classic CC version. I began trying to import some photos into my library and each and every time it crashes after a little while and doesn't actually import them.I thought I would start a new catalog, to see if there was something incompatible or wrong with my previous library, however that too crashes. I can import about 2-3,000 photos and then each and every time I go to import a new folder of images -- bam.  I've tried importing small batches, also crashes. Extremely disappointed!

Lightroom 7.x broke the ability to show placeholder_string in text input fields created by LrView.osFactory():edit_field and password_field.This is visible e.g. in Hard drive publish service description fields, first Lightroom Classic CC 7.3.1 and then Lightroom 5.7.1 (sadly I couldnt run 6.14 concurrently with latest release, all I got was error 1 on startup) LR 7.3.1:LR 5.7.1As you can see, the placeholder string "Untitled export" is not visible in Classic CC, and so are not any other placeholder_strings.  I think this used to work fine in 6.x, and I've used for example login/password fields in my plugins.  Now the users are pretty confused because all they see is empty text field.Tested on Lightroom 7.3.1, macOS 10.13.4.  Sorry, didn't try it on Windows.

Hi,This one, I can reproduce at will. Using a dual monitor configuration under Windows.1. Launch LR. Go to the Library module. Main screen in Loupe mode, secondary display in Grid mode.2. Select a smart collection.3. Select an image.4. Exit LR.5. Relaunch6. The main display shows again the lastly selected image. The secondary display says "No photos in selected smart collection".7. Now if you select another smart collection and go back to the previously selected one, all the images of the smart collection are shown on the secondary display.Sigh! Yet another bug introduced with version 7.3.

I am running LR 3.4.1 on OS X 10.6.8. The Library>Enable Filters command does not work properly when I have a Library Filter set up to filter on more than on criterion. For example, I have a Library Filter preset called "Needs Location Keywords" that selects all images for which don't have "Location" as one of their keywords and which are not flagged as Rejected. In other words, there are two filter criteria applied: 1) TEXT: Keywords "Don't Contain" "Location" 2) ATTRIBUTE: Flag = Flagged OR Flag = Unflagged Toggling the Filter State by choosing Library>Enable Filters works as desired when the Filter State is changed to OFF; all images in the selected folder are displayed. However, when Library>Enable Filters is selected a second time, changing the Filter State back to ON, only one of the original filter criteria is applied, namely: 1) TEXT: Keywords "Don't Contain" "Location" However, ATTRIBUTE Filtering is NOT re-enabled as one would expect. This is repeatable with differen

There appears to be a bug in Lightroom Classic CC 7.3 with regards to camera default settings: they're only partially applied on Import.For example, in my default settings, I apply a camera profile (Camera Neutral) - this works.I also use a fixed, custom white balance - this doesn't work. Lightroom always uses the "As Shot" white balance from the camera instead on import."Remove Chromatic Aberration" is on in my default settings (why does that default to off, anyway?), but it's off after importing.Only when I use "Reset" on a newly imported photo, ALL of my custom default settings are applied.I reverted to version 7.2, and my default settings are applied right on import, as expected.I'm using Windows 7 64bit.Thanks for looking into itAlexander.

[Update: The GPS Data Metadata browser column disappears when returning from Map to Library when there are more than four columns in the browser.  See this recipe from Louis Sherwin for reproducing the bug: https://feedback.photoshop.com/photoshop_family/topics/bug_report_filtering_for_metadata_gps_informa... Last tested in CC 2015.12 / OS X 10.12.6.  -- John R. Ellis]Hej,I think I found a bug in LR 5.2 which can be reproduced as follows (my LR is german, so the english translations might be a little off of the actual labels):- go to library (Bibliothek) module- under library filter (Bibliotheksfilter) select meta data (Metadatan)- go all the way to the right and select add column (Spalte hinzufügen)- click none (ohne) and select GPS data (GPS-Daten)- go to map module- got back to library module- the newly created column is gone now.If you can or can't reproduce this or know a workaround, please let me know.Thanks, Tobi

Step 1: In order to apply my standard changes by Camera and ISO to imported raw files I first set up one image carefully in the develop module and then hit Option+Update to Current Settings. (screen print)   Step2:   I then perform an import from that Camera and ISO however none of the changes that I established in step 1 are applied.  (this used to work in LR 6). Nothing happens to the imported raw files, no edits are applied.  I shut down LR, restart it and then I see the edits.  I reported this on another post but just discovered restarting LR allowed me to view the edits - none were applied on the initial import.  No idea why. Screen Print 

When clicking on Preview or Play I get the message "An internal error has occurred: ?:0: attempto index a nil value". Had no problems prior t0 latest update. Windows 10 Pro with latest updates 32GB ram

When you apply Auto Tone to a large batch of photos, LR does not consistently update all the photos, and subsequent batch changes to the photos’ develop settings can get lost.  This happens when using any of the mechanisms for batch changes: Photo > Develop Settings > Paste Settings, Auto Sync, Quick Develop > Saved Preset, or via the SDK.This problem has existed for many years (see all the reports merged below), at least since LR 5, and probably at least since LR 4.Apparently, when you apply Auto Tone to a batch of photos, internally LR just sets a flag on each photo, deferring the actual computation of the Auto Tone until later. It won’t actually compute the Auto Tone develop settings until the photo’s thumbnail becomes visible in Library or you edit the photo.  But any other develop settings you’ve applied to the photo in the meantime will get silently overwritten by the deferred Auto Tone.To reproduce the problem: 1. In Develop, define a develop preset “Test

After installing the Feb 2018 update yesterday, portrait movies imported from my iPhone (6S) are strangely rotated 90o to landscape orientation. Previously, no problem with such files.As part of my weekly collation of images from my phone, I export originals from Apple Photos, then import them into Lightroom. The specific files I am now having problems with, but didn't have before, are portrait movie files that are part of "live photos". The associated jpegs from live photos are all rotated correctly, and landscape "live photos" have no problem.I tested and this extends to all portrait movies, not just the .mov parts of "live photos". The problematic imported .mov files look fine in Quicktime and Finder.

Say I'm in Lightroom and I want to open 5 or 6 shots into PS CC, and while they're opening I want to jump over to Chrome and check my email. Is PS supposed to keep jumping to the front every time another file opens? It's pretty frustrating and I don't remember it happening in previous versions of PS.

After conversion of tiffs to dngs, I have multiple dngs!!!Here's the details...After importing a series of tiff images, I converted the tiffs into Adobe dngs files.  After restasrting LR 7.5, I find that I have multiple dngs!?!   At least three (3)!Really?  Seriously?My Finder does not show these duplicates as actually existing.  So where in the heck did they come from?

Lightroom 3.6 - on some photos I get a ! mark saying there is a unknown error while writing metadata to this photo. retry? - which I do and it still will not save. No other message is displayed. I've verified there are no 'read-only' permissions on both my folder and photos as well as the catalog folder and files. Ever photo that I have noticed this on as a exif version of 0210. ( not sure if it's related or not ).

After upgrading from 7.2 to 7.4, all of a sudden the option to update any pre existing personalised presets with 'Update with Current Settings' has been removed and replaced with only 'Apply on Import'. I'd like to know why and if this is a bug can it be repaired please as I use this function on every Lightroom session. Thanks,

When a photo is synced from LR iPhone, the capture date in LR Classic is set inconsistently, causing the photos in Library grid view to sort incorrectly.  A workaround is to select all of the synced photos, do the menu command Metadata > Edit Capture Time, and click Change All. This appears to set the catalog's internal capture date fields consistently.This is yet another instance of LR's internal architecture maintaining multiple fields for capture date in the catalog database and a programmer incorrectly setting some of them.  There are other bugs (outstanding for years) caused by this architectural defect: https://feedback.photoshop.com/photoshop_family/topics/lightroom-still-inconsistent-capture-date-tim...I'm not merging this bug report with that one, though, because all the symptoms in that one are caused by importing photos missing EXIF capture dates. Whereas this bug occurs cloud-syncing photos with valid EXIF capture dates.In this instance, one of the ca

When  applying the warm contrast preset (under creative)   applied lens profiles are removed.  Seems to happen only this one preset.  Not a big deal just thought you should know - if  you don't already.btw: applying lens profiles after applying the warm contrast preset works just fine.

While in develop mode i try to synchronize some of the settings and i find that when i check some of color adjustments box, Lightroom 7.3.1 check the Treatment & Profile box.This is a problem when i have photos taken with different lenses and i have profiles for each of this lenses. And i don't want to sync the profile only color adjustments.EDIT: I have color profiles for specific lenses (i don't mean the lens profiles)

Hi,I've been having problems saving metadata under certain conditions in 2015.8..  LR will say saving metadata, but the badge will come back on after.So far, I've been able to narrow down that it seems to happen most often when an adjustment brush is used along with guided upright.  The problem comes in when I try to replicate it in photos that are ok with it.On problem photos - copying, then deleting the problem adjustment brush will allow it to save ok.  But if I re-paste that copied brush, it wont save again.  Even more puzzling is that if that if there are more than one brush, then it seems to only have a problem with ONE of them.  And again, I haven't been able to determine a pattern as of yet..  It took me quite a while to even narrow it down to an adjustment brush issue, recently.Also of note is that it will have problems saving even if there are snapshots with the offending brush, even if the 'current' doesn't include the problem brush.Also importa

I have been eager to try the new RAW Profiles released recently.  But they don't seem to work within the Develop Compare function.  For example, let's say I apply 4-5 profiles successively.  And then I want to use the Compare function to help me choose the one I like best.  The program won't let me click-and-drag previous states from the History panel.I am a long-time user of Lr and I know  how it is supposed to work.  You choose the Y|Y Compare function and it is supposed to allow you to click previous Develop steps and drag them into the left pane of Before/After.  With these new profiles, the clicking-and-dragging does not work, or if it does at all, it is very sporadic: maybe you can drag one earlier version in, but if you try to click-and-drag another one, nothing changes in the Before panel.  But substantially, it just doesn't work.

After updating to Lightroom Classic, the crop overlay lines are thinner and lighter than before. Can't see them on most photos. 

Found this thread in the U2U forum, and can confirm it is not working for me either. The OP of that thread is using a Surface, while I'm on a Wacom MobileStudio Pro, so I don't think it is a driver issue. Here's what happens: - starting in Grid view with a few thumbnails showing in a folder, and one photo selected - tap the Touch icon - the view switches to Develop, and all thumbnails vanish - pressing the G key switches back to Grid view, and thumbnails appear in the main area, but Filmstrip is empty - changing sources via the Folders panel never populates the Filmstrip, though the main area loads with thumbnails - restarting Lr is the only way to get it back to normalThis is not a function I use, but I did use it once on 7.2 and it did work. Just wanting to bring it to the team's attention. 

This issue is on Lightroom Classic 7.4.   If you export using Width&Height, Long Edge, Short Edge or Dimensions with no number in the size value fields and then do an export using Percentage than the percentage value is ignored.  If correct values are in the above 4 dialogs than the Percentage export will work correctly.  The dialogs for Width&Height, Long Edge, Short Edge or Dimensions should not allow an export if the length fields are not filled in with valid values.  The problem does not seem to correct itself unless you do an export with a valid value is the above four export choices.  See this U2U thread for more detailed explanations and examples.  https://forums.adobe.com/thread/2508201

This post contains a video, for a full easy explanation of my situation. Videohttps://www.youtube.com/watch?v=sThVzs0Q5pc&feature=youtu.beThe Issue in a NutshellYou might say Import does not detect duplicate photos. So you have no way to point at various folders and be sure you imported that data. So I have no easy way to find out if my master catalog contains all my various drives (that I am sorting out) data.I discovered this after doing a catalog import, I then did a standard import, not clicking import, pointing it at the photos folder of the catalog I just catalog imported, just to check if catalog import had worked. I selecting 'Don't import suspected duplicates', expecting to see zero or only a handful of orphaned files caused by incorrect deletion. It sees everything, every photo in the catalog! The main things I tried which I think relevant to say... Since pointing it at the original /photos location on the other catalog drive did not work... I copied

When I use {Date(yyyymmdd)>>} Under the menu options  Library > Rename Photo > Edit >  does not work correctly for videos. It will rename the file with the date of the import into Lightroom.  Please fix this so that the video will rename to the date the videos to reflect when it was shot. When I use  When I use {Date(yyyymmdd)>>} Under the menu options  Library > Rename Photo > Edit > for my photos, it will rename the photo with the date that the photo was taken. This is working great for my photos.Sample of what I would enter into the Filename Template Editor{Date (YYYYMMDD)>>}_FallsPark{Sequence # (0001)>>}for both photos and videos.I process a significant number of photos and videos. (Over 9000 over a 20 days period). I need a fast turnaround. If I have to manually change each of my video file name  with the correct date taken. This will slow me down significantly. Please get it where the rename f

Since the new Adobe Color profile was introduced, I decided to adopt it as my default profile for my raw images. I had previously been using Adobe Standard. I have tried several times to change my default settings to include that profile as part of my default settings. However, every time I import new images the Adobe Standard profile is applied. I have reset my preferences in an attempt to correct the problem, but that didn't work either. I'm using Lightroom Classic CC 7.3.1 on Windows 10.If I update my camera defaults and reset the images, Lightroom will apply the Adobe Color profile as it should as long as I'm using Lightroom following the import. However, if I close Lightroom and then use it the next time to import, it will apply the Adobe Standard profile to the raw images. This is an anomaly that I have replicated several times before I have bothered to report It.Incidentally, I attempted updating the defaults by the alt-reset method as well as using the update default settings o