Bug Reports

I use LR3 and have just upgraded to OS X Lion. When importing images from CF card, server mounted volumes are not displayed as an import destination. Drives are mounted and are visible when in the Library module, but not visible when importing. This was not the case under Snow Leopard. I can import the images to a locally attached drive then drag to the network volume in Library, but this requires adequate space on local drive and takes time to carry out the process.

I recently noted that in Lr 3.4 the metadata field "Date/time digital" does not show the correct date any more. It always shows the date/time of the other two date/time fields. I've tested my catalog again with Lr 3.3 and there it shows correctly. This seems to be bug introduced in Lr 3.4.

In the IPTC field Date Created...I enter 1906-01-01 and hit return....the field is now populated w/ 2042-02-6. Lightroom says that the metadata has been saved with the original file, but when I look at the image in Bridge (or one that has been exported from LR...) I get the correct date that I entered (1906-01-01). How can I get Lightroom to display the Date Created that is imbedded w/in the file? btw I'm using MacOS 10.6.7 & LR 3.4.1.....thanks!

Crash problem with Lightroom 3.5 32b RC. LR crashes repeatedly after I changed the Distorsion slider on the Lens Correction panel with the Nikon 17-35mm profile loaded. It seams that only certain pictures are affected. I can restart LR but as soon as I make a "problem" picture active it crashes again. I am using Windows 7, Swedish. Please let me know if I can provide more details for you. /Fredrik

Just worked in "lights out" mode (development module) and wanted to export a photo. I noticed that the export dialog is partially obscured like the main LR window - screenshot: Happens in 3.4.1 and 3.5RC. Does _not_ happen in full-screen mode. Also happens for the settings dialogs and the import (!) dialog. After switching to other applications and back, the dialogs become completely obscured (really confusing if you are in 100% lights out - screen goes completely black). Also, moving the dialogs causes some different areas of the dialogs to be affected by the lights out. Win XP 32 Bit SP3, 1600x1200 screen resolution. Edit: Video: NVidia GeForce 7600 GS, latest driver from NVidia website.

Hi, in a LR publishing service, when it comes to the deletion of images that were removed from the collection, it halts with the following error message: Image is not available I have found several reports of this happening when the file to be removed from the collection had already been removed manually outside of LR. But this is not the case with me - the file still exists on the hard drive. I rather believe that it can't handle the # character in file names properly, because the file's name is e.g. 2011-03-27_00-51-50_#165.jpg, but when I right-click on the image in LR and select "show published file in Explorer" it telles me it can't find the image but with the name "S:\\165.jpg, so the part of the file name until the # is missing! Image is not available This happens to all the files that have the # in their name. I am using Windows 7 64 bit, if that matters. # is an allowed character in filenames in any modern OS, so please fix this annoying bug as soon as possible. It seems to

Since I installed new Lion last week, the scroll bars of Lightroom 3.4.1 became crazy. They move less than the movement I make with the pen of my wacom or with the track pad or with a mouse. Each time I touch the bar it jumps moving away. I have checked in case the problem were in the drivers of the wacom intros 4, but it is not because it works ok in the rest of applications in my iMac, everywhere else it works properly. Any help? Thank you!

When LR 3.4 writes metadata, it is writing the wrong time zone into XMP:MetadataDate, using a "+" rather than a "-". For example, I'm in PDT (UTC-7:00), but LR writes the following value: 2011:05:13 09:10:17.082+07:00 A number of others have noticed this and wondered whether it has anything to do with LR's problems in spurious "Metadata needs to be updated" notifications; for example, see: http://forums.adobe.com/thread/849347 A sample image: Image is not available

The size of the adjustment brush can be controlled using the mouse wheel: Rolling it away from me increases the size, rolling it towards me reduces the size (same as in spot removal). When the mouse wheel is used while holding the shift key, it adjusts the feather. However, it does so in the opposite direction: Away from me decreases the feather, towards me increases it. IMHO this is completely counterintuitive and confusing. Was this intented (if yes, why?) or is it a bug? I use LR 3.4.1 on Win XP 32Bit SP3, no special mouse driver and a Logitech MX400 mouse.

For example: When the computer's date changes, and a smart collection "capture date in the last X days" contains e.g. 50 photos before midnight, and 40 after midnight on the new day, the smart collection as such works correctly, i.e. selecting something else and then the smart collection again will show only the 40 photos that match the rules *now* - and the film strip info shows correctly "... / 40 photos". However, the number of photos indicated to the right of the name of the smart collection still shows "50". The only thing that seems to refresh this number is to restart lightroom. This is of course not a severe bug, but it may be irritating sometimes. P.S. Seen on LR 3.4.1 on WinXP 32 Bit SP3. P.S. I have seen some other occasions (not date changes) when the number of photos to the right of the smart collection's name was not updated when something was changed for the photos. However, I was not able to pinpoint the exact circumstances. Normally, this number is updated correctly.

I found that the lightroom upload plugin can't convert and export psd files to viewable jpgs. Need to export them first to jpeg format, reimport them in lightroom to upload them then with the plugin. Wonder why this works with the third party jF-Facebook plugin, but adobe is not able to convert psd to jpeg? Is it possible to fix that?

I noticed a change of tones in one of my photos after upgrading to LR 3.4. This is how it used to look (and as it was uploaded to Flickr): And this is how it looks now in LR3.4: Image is not available Note especially the small patch of road on the lower right corner: it has distinctly green color cast in the current version. There are other changes in tone elsewhere in the photo, but they are much more subtle than the road. And as you can see from the history panel, the image has *not* been modified by me at all in Lightroom since it was uploaded to Flickr (which is the version above). So it seems that some sort of bug has caused this color shift. Which is not nice. Fortunately this is (at least so far) the only image which seems to be affected. Using latest version of Mac OSX here, LR running in 64bit mode.

Hi, I am currently using Lightroom 3.1.4, 64bits on windows, with EOS 10D Jpeg files. Everytime I edit those files Lightroom crashes. I can send you such a file, please let me know how to help. Regards Eric

Windows 7 64-Bit / Windows XP, LR 3.4.1: According to the manual, Shift + = / Shift + - should Increase / decrease Grid thumbnail size on secondary window. I can not make this happen. Can anybody confirm? Beat

Hello there, i spent 3 hours trying to get lightroom work. But ended up really frustrated. Lightroom keeps saying that it is not able to import my images for what ever reason. That is really annoying and frustrating. Why can't lightroom import my pictures?

After importing raw files into Lightroom, I want to work on some of them in Photoshop, then save it back to Lightroom as a JPEG file - not a huge TIFF. I used to be able to do this in previous versions, but not in CS5 and Lightroom 3. It is a pain to have to go re-import everything I work on. Any solutions?

I have two computers: an older XP laptop with lots of applications, and a 6 month old Win7 64-bit dedicated workstation for photography work. Each has Acrobat 10.1.0 and Lightroom 3.4.1 installed. Sometimes I print proof sheets of batches of photos using Lightroom Print, printing to Adobe PDF. On the XP, I have never had any difficulty printing to an Acrobat PDF from Lightroom. On the Win7, I have NEVER been able to print a proper Acrobat PDF from Lightroom. A PDF file is produced which is readable and contains all the expected text appropriately laid out in the expected grid pattern (filenames, page numbers), but it only contains a fraction of the photos, anywhere from zero to a significant percent. Each photo that actually shows up is complete, not partial. If I re-run the print job, sometimes different photos materialize than last time. The number of photos in the batch doesn't seem to make any difference to the result - even tiny batches have the problem. One more clue -- it takes

Lightroom: 3.4 unable to create slideshow video with soundtrack. I created a voice over for my slide show so that I can send the file to relatives to watch. Voice over created with as an iPod voice memo. That created a .wav file which LR does not support. Annoying, but fair enough. Next step was to create a .m4a file which LR claims to support. That runs within LR, but crashes when I attempt to create a video file (the intended recipients do not have LR). Error text: Log (6) Assertion failed: self->aenc info: Creating MainConcept H.264/AVC video encoder ... info: Version: 8.0.0.47059 info: Platform: OSX info: Using library: MainConcept optimized Software Encoder (mc_enc_avc.001) extendedOption: media_time_offset : 0.000000 -> 1000.000000 End error text Third step was to try a .mp3 file. That comes up with an exclamation sign beside it, and will not run withing LR. It also crashes the "create a video" subroutine within LR. Different error to above. I could find no explanation of w

Hello to the Community! This is my first post and, unfortunately, is for a possible bug, not a nasty one but it annoys me a bit: The "Keyword Set" sub-panel under the "Keywording" panel stays expanded no matter how much I close it. Upon Lightroom re-start I find it opened. It occurs with Lightroom 3.3/3.4 running on Snow Leopard 10.6.x. Does this happen to any others? Regards, Stefano

Adjusting slideshow options causes Lightroom to crash - every time. In fact, its in a state now where just scrolling the slideshow options causes Lightroom to crash - every time. In fact, it may have just been the scrolling that causes it, all along...

Facebook publishing doesn't work at all in LR 3.3. 😞 I get this error (see screenshot) every time. 😞 Image is not available Here's a corresponding excerpt of my console.log -- obviously a bug that needs to be fixed... 27.03.11 22:31:01 Adobe Lightroom 3[48905] Warning failed to send request 0: -1 27.03.11 22:31:02 Adobe Lightroom 3[48905] Warning failed to send request 0: -1 27.03.11 22:31:03 Adobe Lightroom 3[48905] Warning failed to send request 0: -1 27.03.11 22:31:13 [0x0-0x1d08d07].com.adobe.Lightroom3[48905] Notice 2011-03-27 22:31:13.353 Adobe Help[51959:903] NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be 'Editor', 'Viewer', 'None', or 'Shell'. 27.03.11 22:37:44 Adobe Lightroom 3[48905] Warning Oops! An untagged string (?:0: attempt to index field 'albumInfo' (a boolean value)) got thrown far enough that we display it to the user. This shouldn't happen. 27.03.11 22:38:01 Adobe Lightroom 3[48905] Warning AgNewCreationsDial