Bug Reports

This sure feels like a bug: Steps: Create a stack Select it Choose Split Stack Result: All photos bar top are removed from catalog. Huh?...Help says: Note: The Split Stack command is not available if you only select the top photo in a stack. That's the behaviour I would expect. Is this a known bug?

LR 4.2 final 64 Bit on Win7. Steps to reproduce: 1. Select a folder containing about a dozen photos, all *not* part of a stack 2. Group photos so that three or four stacks are created and all photos are in a stack 3. Expand all stacks 4. Select all photos 5. Group into stack (now a single stack containing all photos of folder is there) 6. UNDO Expected result at step 6: Stacking goes back to the previous three or four stacks Actual result: Apparently only one of the stacks is restored, and all other photos are now contained in "single-photo-stack" displaying the "photo is part of the stack" badge with the number zero [!] in it. Expaning/collapsing those "stacks" seems to hide/show the previously existing stacks, but they are definitely gone. The "unstack" command is not available to "break up" the "single-photo-stacks". A restart of LR does not help. However, there seems to be a workaround: When selecting the "single-photo-stacks" together with a "normal stack", the "unstack" command w

LR 4.2 64bit Win7 SP1 64bit During catalog backup any mouse wheel movement brings this dialog [Window Title] Confirm [Main Instruction] Lightroom was unable to back up the catalog named “LR catalog”. [Content] Please check your folder permissions, and make sure that you have available space on your backup drive and main catalog's drive. [Try Again] [Choose Different Backup Folder...] [Exit]

On regular basis I get a crash in Lightroom when load a GPS track in the map module. This usually happen when I load more than one per session. When this happens restarting Lightroom and loading the GPS track again works. The GPS track in in .gpx, generated by HoudahGPS This problem exists since the initial beta of Lightroom 4. Still happen in the 4.3RC. This is on Mac. I have systematically sent the crash report to Adobe (check with my email address if you have access to them) The only reason I report it here is because I was told the crash reporting is not useful.

Cannot delete missing photos in LR4.3 Please try this: 1. Find missing photographs 2. Select All 3. Pick "delete photos" from the menu. 4. Nothing will happen! We had a discussion here: http://forums.adobe.com/message/49182... This is probably newly formed LR 4.3 bug.

I note RW2 Files from the Panasonic GH3 and imported as DNG in LightRoom do not show GPS location in EXIF data even though it is present in the original file and the DNG file. I'd like to report this as a bug. (LR4.3/Win 7 64bit)

Using ctrl+scroll wheel while showing an image on the second screen zooms and scrolls to the next image at the same time. But it should only zoom.

They work as expected in Folders, but no icon shows up in collections. In collections, if I choose Expand All Stacks the stacked photos do expand, but no other stack commands can be executed on them. Photos which were not stacked in Elements can be stacked, unstacked etc. Only the ones that were in stacks in elements have this problem, which unfortunately is every photo I ever edited in PSE8.0.

When you want to paste metadata from one picture to others (ctrl+shift+alt+C and ctrl+shift+alt+V) and you select altitude it isn't inserted into the metadata of the target picture. Copying/pasting of GPS coordinates, location information, keywords, ... do work fine, but the altitude isn't working at all!

According to listing on http://labs.adobe.com/technologies/li... there should now be support for Canon 24-70 f/4L IS When I try this out I can't find the lens i the list.

Lightroom 4.4RC1 won't import a tiff file more than 2 gb. 4.3 would to this.

In LR5 when I go to use one of the 5 zone adjustment areas in the Develop module histogram, there is a 2 - 2.5 second delay before I can use them for each image. The individual sliders below, e.g., exposure, contrast, etc, don't exhibit the delay.This is not the case with LR4.4... and it is a cause of frustration for me due to the slowdown in my wedding workflow. I'm on a Mac Quad Core, 12 GB, SSD, etc, so I'm not sure what the problem is, as I said there's no problem with 4.4. I searched but did not see this problem listed. Also, LR 5.2RC does not fix the problem.

The Crop Overlay tool is broken. I have tried both the panel option, as well as, the menu pulldown option (Tools | Crop). Select an image -> Activate the Crop Overlay tool -> Adjust size and/or orientation of your image to taste -> Select Done. Move to the next image. Move back to the image you just cropped. The image is then re-cropped to something arbitrary. This is happening 100% of the time (12 out of 12 images) on vertically oriented Canon 5D Mark III RAW images. I'm using LR5.2RC (downloaded 30 minutes ago) on a 2012 MBP w/ 2.2 i7 processor with 8GB DDR3.Please, please fix this in the official LR update!

Using the crop tool in the Develop module after using the auto Lens Correction tool will cause Lightroom to crash, if you try to rotate the photo to make it level.

I imported my JPEG collection and noted that several images have their lower half displayed in black and white with some orange hue, other are completely distorted. The original image looks fine when rendered by any other image viewer or editor I have (i.e. Preview, Picasa, Xee, Canon DPP, Firefox, Safari. Upgrading to 5.3 did not help. Here is a screenshot and an original image that can be used for comparison: https://www.dropbox.com/sh/89g6zglpz7...

LR4.2 When removing a photo from a collection and then pressing "undo" the photo is not returned to the collection and instead a preset is applied to the next photo.

Im using Lightroom and Mobile Light room. I live in the Eastern time zone and the times are all 3 hours behind (PDT). I checked my Adobe ID, iMac and iPad and the times are all set to EDT. Please fix.

When attempting to apply a crop to images using copy/paste an error dialogue is presented which isn't very clear or helpful containing the phrase: "An internal error has occurred: ?:0: attempt to perform arithmetic on a nil value" A more useful error message could instead be presented so that (such as in my case) the user is aware that they are attempting to apply a crop to a video file (which isn't possible in Lightroom) and therefore the entire operation will fail until the video file is removed from the selection. In addition to this when I was attempting to troubleshoot the problem the video file in question did not appear as a video file (when using a filter to view just video files in the selection - no video files were found - instead only an 'unknown' file which caused the problem). A video showing me recreate the issue before I discovered the solution is here: https://www.youtube.com/watch?v=M1sprA... A thread around this issue has been posted here: http://www.lightroomforums.

I asked this question 2 weeks ago but got no response so I am asking it again here. Suddenly on two of my pcs, one of which is a completely clean installation, when I click on Lightroom online within the help menu, Lightroom crashes and closes. This cannot be a one off because it started on both pcs at the same time. Has anyone else experinced this problem and what is the solution? Within photoshop, Photoshop online does not cause this problem

Lightroom: When I resize my right panel, the controls get screwed up in Develop. Where I click no longer lines up with what moves in the sliders. It has become out of alignment.

Lightroom mobile for android does not allow filtering by 0 stars. If I view a collection and set the filter options to '=' with no stars selected, it shows photos with any number of stars. It should set the filter to photos with 0 stars, as done in the desktop versions of lightroom. Setting the filter to 1 or more stars works as expected, but not 0 stars. sample screenshot:

Aperture information is different between desktop Lightroom CC 2015 (Windows 7) and the Android mobile app (Samsung S6). I've noticed this on a few photos and a few lenses. For example, when I look at some photos that I shot at f2.8 with a Canon 70-200 f2.8 IS II, on the desktop version of Lightroom the information is correct, but on the Android version the information says f3.0. Similarly, when shooting at f5.6 with a Canon 10-22mm, the desktop version shows f5.6, but the Android version shows f5.0.

I’ve just discovered a bug in the Develop Module in LR6.2 perpetual version. I have Photoshop CS6 perpetual updated as far as it will go (to ACR 9.1), Mac. I’ve not been affected by the changes to Import in LR6.2 which are causing many people so much stress, as I always copy files from the card to the computer drive before importing and do all my in initial file organisation outside of LR and apply all metadata after import. I set my default develop parameters by hitting alt-Reset in the Develop Module and I have these set in LR prefs as “specific to camera serial number”. My default setting are actually very close to the LR defaults except I tend to add a little Vibrance, turn off sharpening and I always have “Remove Chromatic Aberration” checked. However, since updating to 6.2, newly imported files do not have the CA tick box checked although all other settings that I have tried appears to be as they should be. Strangely, when I then hit the Reset button (which restores the Develop d

Mac OSX 10.11.1 Lightroom CC 2015.2.1 Whenever I develop a photo and use 'Manual' under lens corrections I get the following three messages recorded in the system logs: Adobe Lightroom[]: maybeAssignDesiredL had an unhandled key: slider_text_labels Adobe Lightroom[]: maybeAssignDesiredL had an unhandled key: slider_row_unit Adobe Lightroom[]: maybeAssignDesiredL had an unhandled key: slider_row_edit

I'm not sure if this is a Lightroom problem or an f.lux problem, so I'm posting in both places. F.lux is software that automatically cuts out blue light at night so your screen doesn't disturb your sleep cycles as much, but you can set it to shut of for particular software. Here's the bug report I posted at f.lux forums: https://justgetflux.com/forum/topic/1... I installed f.lux a week ago on a 2012 MacBook Pro Retina running OS X 10.11 El Capitan. When Lightroom was in the background, it would become unresponsive (beachball only, OS X reported it as not responding). I uninstalled f.lux and the problem stopped. I had disabled f.lux for Lightroom (latest CC release, mostly the same as 6.3) so I could get accurate colors for photo editing, which may or may not have been related to the problem. I forgot to check if reversing f.lux's Lightroom exception prevented LR from hanging before I uninstalled.