Bug Reports

Many places in the Map View have active text that if you click on it, a little note comes up saying "This place is at this address, View on Google Maps." This includes National Forests, Parks, etc. In my opinion, this pop-up is totally useless.But, more importantly, it keeps one from being able to select photos if they overlap with the active text. If you click on one of the little numbered place markers, the photos at that place are selected, then immediately the pop-up from the text below is activated, and the photos are deslected! The only solution I have found is to use View > Map Style > Satellite, which gets rid of these active text elements.Otherwise, selecting photos in map view is impossible. I'm enclosing a movie, which I hope demonstrates the problem.Lightroom Classic CC 7.1. Mac OS High Sierra 10.13.2.  

After upgrade I noticed as follows:While creating background task (for example exporting approx 200 photos with adding them to the catalogue) LR behavior is changed in Library view:a) the filters are constantly deactivated when new photos are added in background, it is impossible to choose another set of photos to create new export taskb) the folders tree view is all the time repositioned in such a way, that at the top visible is a row which is currently updated. It is hard to scroll down/up to select other folder...

Since the installation of mojave on my mac lightroom try to synchronize all my photos making the application using dizaines of Go and making it crashing.

If you export a book to jpeg and have the Page Grid turned on under guides.  The guide lines actually export in the jpeg!  Guide lines are not supposed to show in the export, and they don't show in a pdf export.  I almost send in an order with grid lines on the pages.

[Update: The shortcuts for rotate left and right were incorrectly changed in German, Spanish, French, Italian, and Swedish.  See here for details:https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-cc-keyboard-shortcuts-for-r...- John Ellis]Hi Adboe,I like working with LR and it's the software product I use the most. It's a good piece of software and I never had any troubles working with it and I always was a happy user. (German keyboard layout on a Mac) But in the new LR version the keyboard shortcuts to rotate images have been changed, unfortunately to the worse. From (Command+) and (Command+.) to (Command+<) & (Command+#). You did fix something that was not broken.Here's what these new shortcuts do:1) They only work for me when an image I have fully zoomed into an image.2) The shortcut to rotate an image clockwise (Command+#) is the same as the one to zoom into an image (Seriously?! Did no one double check that before the release?).3) In the previous

I like the new feature in Lightroom 7.4 to add a color label to folders. However, when a (color added) folder is missing there is no way to remove the color lable. Also there is no way for adding a color lable to folders that are missing. Am i missing something?

... so it looks like in transform (CTRL-T) the movable center point with that crosshair icon doesn't snap correctly to the positions of the outer corner- and midpoint-handles.Please investigate.Seen in PS CC2019 (oct), Windows8, German.

Great to see the addition of the 'Has Edits' filter to the library of Lr 7.2 Classic. However, I was disappointed when I tried it on my library.During the catalogue upgrade from Lr 6 to Lr 7, I updated the Process Version on all images to the current Version 4. When the 'Has Edits' filter is applied, images that have had their process version updated are selected. Since this selects ALL my images since the upgrade to Lr 7, and only those images with actual develop settings that have been imported since the upgrade to Lr 7, the new 'Has Edits' filter is pretty well useless.In Collections, a Smart Collection can be created with Develop->Has Adjustments, which only includes images with develop adjustments, as expected. Using the new Develop->Has Edits in a Smart Collection includes images with develop adjustments and with the updated process version.The criteria for the Has Edits filter shouldn't include the images with an updated process version because over time, this will include

There's a bug in the Print module. Prints do not print as cropped on screen. It seems to only affect rotated images, here verticals, auto rotated to fit image cells. Notice on screen shots that the crop hasn't been maintained between screen/gui and print. It affects both Print to Printer and JPEG file, whether draft or not.The partial pixelation on screenshots are done in post. Focus on the borders/cropping on the top most row on the sheet of 4 image cells. Notice the bucket and shoe are cropped differently between gui and print.I hope you can quickly fix this, as it's frustrating not being sure my prints come out as intended.Using version 7.3.1 of Lightroom Classic CC, on macOS 10.13.5.

When you import a photo containing GPS coordinates and altitude, address lookup incorrectly overwrites that altitude with its own altitude derived from Google Maps. This bug was introduced in LR 7.3, 7.4, or 7.5, since it doesn't occur in 7.2, 6.14, or 5.7.1.To reproduce:1. Turn off Catalog Settings > Metadata > Look Up City, State and Country...2. Import this photo, which has an altitude of 32' recorded in its metadata:https://www.dropbox.com/s/dvrhnr59al2klf3/altitude-bug.2018.10.12.JPG?dl=03. Observe the Metadata panel correctly shows the altitude as 32.0'.4. Remove the photo from the catalog.5. Turn on Catalog Settings > Metadata > Look Up City, State and Country...6. Import the photo again.7. Observe the Metadata panel incorrectly shows the altitude as 0.0'.Note that the altitude provided by address lookup can differ by tens of feet from that shown by Google Earth Pro, which indicates that address lookup is not returning the altitude for the exact GPS coordinates

Create a preset called TEST that changes ONLY the Exposure.   This can be ANY adjustment but we will use exposure for this example.  Select a photo1. Apply preset. TEST. (Its added to History)2. Add Contrast.  (Its added to History).  This adjustment CAN NOT be an Exposure adjustment or the Preset will record in History in step 3.  3. Apply preset TEST  (Its not added to History) (It appears to the user it didn't work!)4. Add Highlights.  (Its added to History)5. Do an Undo.   (popup says "Undo Highlights")6. Do an Undo.  (popup says "Undo preset TEST" although this step is not in History)7. Do an Undo.  (popup says "Undo Contrast)IMPORTANT NOTE:  Step two can not be an Exposure change using the above Preset example.  If the Preset was only for Clarity than step two could not be Clarity.  It appears that for some reason Lr is checking to see if the preset is making changes to the sliders before recording a history step.It

Win10 / Lr Classic CC 8.0When using Synchronize Folder, Lr doesn't recognize HEIC files that need to be imported.If the only "new" file(s) are HEIC, Lr shows there are no files that need to be imported and therefore, no import is done.If the "new" files are a mix of recognized formats (jpg, cr2, etc.) and HEIC, Lr only counts the older recognized formats, but it does import all the files.To reproduce -  - In Lr, create a new folder. - In Windows Explorer, copy an HEIC file into the folder. - In Lr, right-click the folder and click Synchronize Folder.  The Synchronize dialog box shows 0 new photos to import, so you can't move on in the import process. - In Windows Explorer, copy a jpg file into the folder. - In Lr, right-click the folder and click Synchronize Folder.  The Synchronize dialog box shows 1 new photo to import, but Lr will import both the files.

LR CC Classic Version 8: When you use menu "Picture" - "Develop settings" - "Update to current process version" in library view on a photo, which has already the current process 5, it gives an unexpected error (maybee the menu's are labeled a bit different - i have the german verison installed), see picture below:The error does not occur, if the process is older.

So far I have only found this to affect Clarity and/or Dehaze alone. To reproduce:Start with an image that has no develop adjustments and is process version 4.Change Clarity or Dehaze, or both. The adjustment badge [+/-] shows on the film strip thumbnail.Update the image to process version 5 (Settings->Update to Current Process)The adjustment badge [+/-] disappears.In the Library module, if you filter Edits, the adjusted image doesn't show as I would expect if Lr doesn't consider it has any edits.If you change the process version to 5 in the Calibration panel, the problem doesn't occur.

Hello Adobe, could you please point out, that while using the new tether feature in Lightroom, it is essential, to follow the tether dialog box till the bottom. There you can choose "save copy to camera“. On a reason shoot i was tethering medium size jpg's because i want the process to be very fast. I was shooting like that many times before, so i overlooked the very tiny checkbox on the bottom of the page. The result was, that Lightroom forced the camera not only to "not" save the medium jpg's to my SD card, but also not save the raws to my CF card. At home i wanted to import the raw files to my computer, but there was nothing one on the cards. I've seen reports on the web, that other people have the same fatal loss of raw date because of that little checkbox, wich is new to Lightroom. Please try to make public, that your users have to take care of this. It would be sad, if more photographers loos more raw files, clients and money. Thank you.

There are a few other discussions where this issue is being reported but i believe they have other issues clouding the discussion   Since the update to .3 and subsequently 3.1 Lightroom Classic CC hangs after being idle for a time (i can;t be specific on time as it seem to change). It does not happen necessarily on sleeping from the computer or in one module or another or when changing windows or minimizing or maximizing   It hangs and i am forced to "end task" through Task Manager   I am on a completely up to date (drivers and software and Windows) Win 10 Pro 64 system with 128gb RAM and plenty of horsepower and disk space (NVME and SSD)   My system has no problems with any other programs   please fix this

[Note from John R Ellis: This was reported fixed in 2015.8, but there have been numerous reports of the symptoms coming back since then: See later posts in this topic.]It may sounds confusing, but when I select one collection or a published folder and go back to Folders and pick up one folder, Lightroom does not deselect that collection or published folder and I can not go back to that collection until I select another collection.A folder in Folders section is deselected when a collection or published folder is selected.I'm using LR CC 2015.1.1

After I create a new keyword set, alt+0 and alt+shift+0 do not toggle among my keyword sets.  If I close lightroom and come back in it works properly.I am running Lightroom Classic CC 7.5 on Windows 10.

I sometimes apply a filter combination of Flagged/Unflagged (so excluding rejected pics) and a red color label, using a custom color label set. When this filter was active on quitting Lightroom, the grid view stays empty when I start up Lightroom and only after doing some action (switching to a different folder and going back, changing the filter and undo the change) the photos show up like they should. If I also filter on the white color label (which isn't included in the custom color label set) the photos show up immediately on opening Lightroom.Library filter options: Lock Filters and Remember Each Source's Filter Separately are active. Lightroom version 7.3.1 on macOS High Sierra 10.13.4.

Lightroom 7.3 and osx 10.13.4First, I would like to note that this is not the same as RAW and non-RAW specific presets.  In this case the preset does work with both RAW and JPG files, just not consistently.   A preset in certain scenarios will work ALL the time with a RAW but only works SOME of the time with a JPGCreate a preset using the following methodSelect photo and do a RESET so no settings are appliedCreate a Preset called ZeroSaturation   (I think this can be any slider)Save the preset with ONLY Saturation selected DO THE FOLLOWING WITH BOTH  RAW AND JPG FILESSelect photoDo a RESETApply a Saturation that is not ZeroApply the ZeroSaturation Preset.   (The Preset works with BOTH JPG and RAW)Apply DehazeApply ClaritySelect DehazeApply the ZeroSaturation preset. (The Preset did NOT work the JPG)History on RAWAs you can see the preset works all the time on the RAW.  When you execute the preset on the Dehaze step the history is cleared above De

In LR 7.5, the array returned by LrLrApplication.developPresetFolders() includes buggy fake folder objects intended to represent separator rows in the user interface.  Invoking folder:getPath() on one of these bogus objects raises the internal error: ?:0: attempt to index field '_pathForFolder' (a nil value) This affects any plugin that attempts to access the develop preset folders. In particular, it broke a DxO plugin and my own Fix Presets plugin (which fixes many other preset bugs):https://forums.adobe.com/thread/2528220https://feedback.dxo.com/t/export-to-dxo-broken-after-update-to-lr-7-5/4514https://forums.adobe.com/thread/2527232http://www.johnrellis.com/lightroom/fixpresets.htmThe workaround is to detect such bogus objects by calling folder:getPath() and trapping any error with pcall().Details:Here are the results of calling folder:getName() on the array of preset folders:Note that the bogusly named folders correspond to the presence of separate rows in Develop's Prese

I have a very strange problem: I was on vacation in another timezone and I forgot to change the time on my DSLR. I imported part of the photos directly on my iPad LR app. Another part of the photos I imported into LR CC on my Mac after I got home.Since the capture time was off by 1h due to the wrong time on my DSLR, I corrected the capture time of all photos via LR CC on my mac.Here it is where it becomes strange: The time stamp on all photos is now correct in LR CC Mac but on the iPad or iPhone and also on the LR Webclient is still off by 1h for some of the photos. I first thought it to be a sync error that the changes did not get synced. But then I tried changing the time of 1 photo again to see if it would update. And it did update it just kept the 1h offsett (on my Mac the changed time was e.g. 16:15 and on my iPad it would show as 15:15).What I noticed was that this 1h offsett happens only and for all photos that have been imported via the iPad. On all photos t

Within the last several weeks, I have started to get errors when trying to sync from LR Classic.  Some problem images have been successfully synced for months, and others are new.  The problems seemed to begin when I removed some photos from All Photos in LR CC.  In the upper left corner, I see "Syncing 3 photos", though the number changes.  In Preferences, Sync Activity, the images have had the message "bad argument #1 to '?' (number expected, got nil)", and the Remove from All Synced Photos option doesn't seem to do anything.Is there some way I can reset the sync environment?  Would that be a solution? Thanks.

The Web module in CC 2015.7 / OS X 10.11.5 doesn't use the display's profile when showing photos. You can easily verify this:1. Install this display profile on your system. The profile swaps red for blue, green for red, and blue for green.2. In the Library module, view a photo and notice the colors have been garishly swapped, indicating that Library is using the display profile.3. In the Web module, use the default HTML gallery to view the same photo, and notice that the colors have not been swapped, indicating that the display profile is not being used.4. In the Web module, click Preview In Browser. If your browser is color-managed, the colors of the photo will be swapped. (You may have to completely restart your browser before doing this.)With a regular display profile, this bug can cause colors in the Web module to be more saturated.  See the original report from Bob Somrak here: https://forums.adobe.com/thread/2216419The problem doesn't occur with LR 5.7.1, and Bob t

my new Lightroom Classic does not work classic while exporting:In the export process (of course with the option "Add to this catalog") the exported files do not appear until the "work bar" has already disappeared long ago. So very, very slowly and sometimes not completely.If I redo the export process (with the identical settings) and the confirmed request to overwrite existing data, LR creates duplicates in the export folder. This is obviously a database error, because in the folder the exported data exist physically only once ...Have I described this complicated enough? :-))And yes, I have tried it with my existing (for LR Classic updated) catalog, as well as with a freshly produced new catalog. Always the same mistake.Thanks for any Help, Kai