Still no fix for two annoying Lightroom 5 bugs

I'm very disappointed that Adobe still hasn't fixed two of the most annoying bugs in Lightroom 5. The first is the issue with full screen mode. Unpredictably, the screen will occasionally become trapped in full screen. The only way I know to escape is to quit the software, restart and hit Shift F. The second, even more annoying issue is that, when moving from image to image or going to Loupe view, images will often open blurred. This can usually be fixed by moving back and forth between images.
I have these bugs on a Macbook Pro Retina and an iMac running Maverick and on a Mac Pro running Lion. They occur with Nikon and Fuji JPEGs and RAW files.

I'm encountering the very same issues on Windows 7 x64 with Canon and Sony RAW files. So it looks like a general LR problem.
I have a second monitor plugged to my notebook and when the screen turns off after the inactivity period, the secondary LR screen is moved to the primary monitor with no possibility to move it back, even if the second monitor is turned back on.

Similar Messages

My iPad makes a high low high tune every fifteen to twenty minutes, anyone know of this and have a fix for this annoying sound.

My iPad makes a high low high tune every fifteen to twenty minutes, anyone know of this and have a fix for this annoying sound.

I Also have this problem!!
In my situation, the screen simply started exhibiting the same symptoms a few weeks ago (early February) for no apparent reason. At first I thought the screen was dead, but discovered the heat solution by accident. Now I turn it on and keep it from going to sleep until I go to bed. Thank goodness the battery is still awesome on this thing.
I bought it new and still has the original screen, I keep it at home (never below 62 degrees). Coincidentally, this happened a day or two after the expiration of the warranty!! Any help figuring this one out would be eternally appreciated.
iPad mini retina Wi-Fi, iOS 8.1.3

[svn:fx-trunk] 12994: * Fixes for two issues that were showing up in FB.

Revision: 12994
Revision: 12994
Author:   [email protected]
Date:     2009-12-16 06:44:45 -0800 (Wed, 16 Dec 2009)
Log Message:
Fixes for two issues that were showing up in FB.
QE notes:
Doc notes:
Bugs: SDK-24669, SDK-24686
Reviewer: Corey
Cycloner: George
Tests run: checkintests
Is noteworthy for integration: yes, fixes two FB issues.
Code-level description of changes:
modules/compiler/src/java/flex2/tools/PreLink.java
    Modified postRun() to swap in the root CompilationUnit's Logger
    when validating it's StyleContainer. This allows the warnings
    from StylesContainer.validate() to be persisted across incremental
    compilations. This fixes SDK-24686.
modules/compiler/src/java/flex2/compiler/Source.java
    Made getLogger() public, so it could be called from PreLink.
modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    Modified compile() to check forcedToStop() after each PreLink
    batch. This fixes SDK-24669.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24669
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24686
    http://bugs.adobe.com/jira/browse/SDK-24669
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

[svn:fx-trunk] 13169: * Fixes for two FB issues and two regressions caused by recent fixes.

Revision: 13169
Revision: 13169
Author:   [email protected]
Date:     2009-12-22 14:39:59 -0800 (Tue, 22 Dec 2009)
Log Message:
Fixes for two FB issues and two regressions caused by recent fixes.
QE notes:
Doc notes:
Bugs: SDK-24708, SDK-24668, SDK-24827, SDK-24829
Reviewer: Corey
Tests run: checkintests, com.adobe.flexbuilder.project JUnit tests
Is noteworthy for integration: Yes, fixes two FB issues
Code-level description of changes:
modules/compiler/src/java/flex2/tools/oem/Library.java
modules/compiler/src/java/flex2/tools/Compc.java
modules/compiler/src/java/flex2/tools/Fcsh.java
modules/compiler/src/java/flex2/compiler/asdoc/AsDocAPI.java
    Modified calls into SwcAPI's setupClasses() and
    setupNamespaceComponents() to pass in the SourceList.
modules/compiler/src/java/flex2/tools/VersionInfo.java
    Added null check to getBuild().
modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    Modified compile() to only add elements of "classes" to "sources"
    if not already contained. This covers the case of a Source being
    in the SourceList and the manifest.
modules/compiler/src/java/flex2/compiler/swc/SwcAPI.java
    Modified setupClasses() and setupNamespaceComponents() to check the
    SourceList before the SourcePath when looking up sources.
modules/compiler/src/java/flex2/compiler/SourceList.java
    Made getPaths() public.
modules/compiler/src/java/flex2/compiler/CompilationUnit.java
    Modified setState() to skip disconnecting the root's Logger. This
    fixes SDK-24827 and SDK-24829.
modules/compiler/src/java/flex2/tools/oem/internal/OEMReport.java
    Added sourceList variable, modified procressSources() to
    initialize it, and modified init() to recursively store a
    timestamp for each path in the SourceList. This fixes SDK-24708.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24708
    http://bugs.adobe.com/jira/browse/SDK-24668
    http://bugs.adobe.com/jira/browse/SDK-24827
    http://bugs.adobe.com/jira/browse/SDK-24829
    http://bugs.adobe.com/jira/browse/SDK-24827
    http://bugs.adobe.com/jira/browse/SDK-24829
    http://bugs.adobe.com/jira/browse/SDK-24708
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilationUnit.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/SourceList.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/SignatureExtension.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/Compc.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/Fcsh.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/VersionInfo.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/Library.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/internal/OEMReport.java

IOS 6.0.1 update still no fix for App Store Purchased section

iOS 6.0.1 update still no fix for App Store Purchased section. Keep crashing after few seconds and kicked back to home.
Does apple even aware of this problem???

Hi, thanks for your comment.
The steps that I have dines so far is similar to you I think. I have all so tried a restore on all my devices running 6.0.1 and still nothing. Have spoke to staff in an Apple shop and they were no help at all and kind said it was my devices that had the issue and nothing to do with anything at Apples end. Have all s spoke to staff in a premium retail seller of Apple products and again, no he,o what so ever. I think it's clearly a issue at Apples end with the serves sending out that data when request. IOS6 is full of bugs and runs so slow it silly.
I'm thinking that Android is the way the forward after all the problems I've had with iOS6.

Temporary Fix for Smart Playlist order bug

I stumbled across a Smart Playlist that was keeping the correct order and discovered why. It was a Smart Playlist that contained 2 other Smart Playlists. The original Smart Playlists didn't keep their order but the new one that combined them did. So I experimented on a few other Smart Playlists by making new Smart Playlists that only contained another Smart Playlist. And it works. I've also been able to keep Live Updating enabled.
Hopefully this will help everyone who reads this get by until Apple fixes this bug, which they seem to reintroduce about once a year.

I'm sorry but none of these suggested fixes work, including sort before sync, media kind as music, not referring to other smart playlists, turning live update off, setting Play Order; nothing worked. Plus, on large smart playlists (2000+ songs), not only were they not ordered correctly but the phone (4S no less) pauses 20 seconds to think every time you go into the playlist after a sync.
In fact the only "fix" for me was Apple's last suggestion in their KB article on the subject of smart playlists not syncing in order: in iTunes select my smart playlist, then select all, then make a new playlist (using I believe Edit/New Playlist) based on that selection (which is now not smart), order as needed and sync. It works great but of course the list is now is non-self-updating and I have to manually update it when I add new songs. Not a big deal but still a pain.
For me, order is critical only on my Recently Added playlist, so I went manual with that one. The others I tend to shuffle so the lack of ordering isn't as big of a deal.

Anybody found a fix for the netstream.seek bug?

The bug I am talking about is only being able to seek to a point in a video that the play head has been before.
Here is how the bug is described at :http://www.brooksandrus.com/blog/2005/12/17/5-reasons-netstream-sucks/
"Seeking is super slow until all keyframes are cached. No bull, if you have a file which you’ve completely preloaded, the keyframes aren’t cached until the video playhead reaches that point in time for the first time. If I load a file and seek to the end, the player has to chug through all of the keyframes prior to my seek point. This is slow, slow if I have video of even several minutes."
That was posted 5 years ago. I have found the bug referenced in the following posts:
http://forums.adobe.com/message/1917914#1917914
http://forums.adobe.com/message/692394?tstart=0
I would assume that since this bug has been around for at least 5 years, there would a bug report filed for it or a work around found. But I can't seem to find either.
I have tried multiple codecs and encodings with no luck. I'm having a hard time accepting that there is not fix for this problem. Flash has to read and cache the key frame information of the entire video before being able to seek to the end. Does anybody know where the flash player writes this information? Let me be clear, this is not streaming video, this is video that is running local off the hard drive. The flash player stores this key frame information somewhere until the computer is restarted. At that point when the video is played again, it has to read the entire file again. You can close and open the player multiple times and it will only perform the caching the first time and not again until a computer restart.
again, I am not trying to seek to a point that has not been loaded yet. This is a swf that loads a video off the hard drive.
One that that I have noticed is that when H.264 files are loaded, the player immediately performs the caching scan before it begins to play. When it is finished, you can seek to any point quickly. The time it takes for the caching scan is dependent upon the size of the file and the number of keyframes it has. Whereas the rest of the video codecs will play immediately but will only seek quickly to cached keyframes.
I have only seen this problem discussed in a few spots, with no solutions. it is a very old bug. Has anybody found a fix, work around or bug report on it?
Thanks for your help
-Mike

package {
    import flash.display.Sprite;
    import flash.events.NetStatusEvent;
    import flash.events.SecurityErrorEvent;
    import flash.events.TimerEvent;
    import flash.media.Video;
    import flash.net.NetConnection;
    import flash.net.NetStream;
    import flash.text.TextField;
    import flash.utils.Timer;
    import flash.utils.getTimer;
     [SWF(width="400", height="600", backgroundColor="#FFFFFF")]
     public class SeekTest extends Sprite
          private var videoURL:String = "test.flv";
        private var connection:NetConnection;
        private var stream:NetStream;
          private var tick:Timer;
          private var startTime:int;
          private var skipCount:int;
          private var duration:Number;
          private var txt:TextField;
          public function SeekTest()
               txt = new TextField();
               txt.wordWrap = true;
               txt.height = 300;
               txt.width = 400;
               addChild(txt);
               tick = new Timer(0.1);
               tick.addEventListener(TimerEvent.TIMER, checkLoad);
               connection = new NetConnection();
            connection.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
            connection.addEventListener(SecurityErrorEvent.SECURITY_ERROR, securityErrorHandler);
            connection.connect(null);
          private function netStatusHandler(event:NetStatusEvent):void {
                //print("Net Status:", event.info.code);
            switch (event.info.code) {
                case "NetConnection.Connect.Success":
                    connectStream();
                    break;
                case "NetStream.Play.StreamNotFound":
                    print("Stream not found: " + videoURL);
                    break;
                    case "NetStream.Seek.Notify":
                         print("--- Seek Completed in", (flash.utils.getTimer() - startTime)/1000, "seconds.");
                         seekDone();
                         break;
        private function securityErrorHandler(event:SecurityErrorEvent):void {
            print("securityErrorHandler: " + event);
        private function connectStream():void {
            stream = new NetStream(connection);
            stream.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
            var metaOb:Object = new Object;
            metaOb.onMetaData = metadata;
            stream.client = metaOb;
            var video:Video = new Video();
                video.height = 300;
               video.width = 400;
               video.y = 300;
            video.attachNetStream(stream);
            startTime = flash.utils.getTimer();
            stream.play(videoURL);
            addChild(video);
            tick.start();
        public function metadata(info:Object):void
             duration = info.duration;
             print("Metadata: duration=" + info.duration + " width=" + info.width + " height=" + info.height + " framerate=" + info.framerate);
          private function checkLoad(e:TimerEvent):void
               var seconds:Number = (flash.utils.getTimer() - startTime) / 1000
               if(stream.bytesLoaded == stream.bytesTotal && stream.bytesTotal != 0 && seconds > 3)
                    skipCount = 0;
                    print("Video 100% Loaded. Performing first seek after 3 seconds of video playing.");
                    tick.stop();
                    startTime = flash.utils.getTimer();
                    stream.seek(duration - 2);
          private function seekDone():void
               if(skipCount == 0)
                    //just skipped to the end of the video the first time
                    //jump back to the begining and do it again.
                    startTime = flash.utils.getTimer();
                    print("Seeking back to the begining to time the second seek to the end.")
                    stream.seek(0);
               }else if(skipCount == 1)
                    startTime = flash.utils.getTimer();
                    print("Second seek to the end. ")
                    stream.seek(duration - 2);
               skipCount++;
          private function print(... args):void
               trace(args)
               txt.appendText(String(args.join(" ")) + "\n\n");
The above is a simple test I put together. Use a large FLV for the testing. Remember, the first seek to the end will be the longest and you may not get the same results unless you restart or use another FLV.

Still no fix for superdrive not reading any disc at all?

I've searched through the forum and it seems like there's still no solution for the superdrive not reading any sort disc at all. I have had this imac for almost a month. I rarely have used the superdrive but was trying to play a normal audio cd tonight and upon further investigation found that the drive is not reading any type of disc.
If a disc is loaded, the drive whirs/beeps 4-5 times while trying to read the disc and then ejects it. this happens for dvd movies, audio cds, osx install disc, etc.
I did successfully play and rip some cds a few weeks ago when the imac was first purchased. I have not inserted discs often enough in the past to substantiate that upgrading to 10.4.5 or 10.4.6 affected the drive's performance.
Think I need a new drive or could this be software related?
imac intel core duo 17" Mac OS X (10.4.6)

I want "solved"
You can add me to the list too - I check this page frequently for a reply from an apple representative - to no avail.
My computer is less than 2 years old, purchased brand spankin' new, w/o the warrantee - but hey when you pay that much for your 'puter it should not break down at ANY time during (at least) the first 5 years, unless gross negligence and disregard is involved (which is is not).
I would not categorize myself as being in the 'high usage' category for burning either dvd's or cd's, but here I am less than 2 yrs after purchase w/ a superdrive that can't even read a store-bought cd, and oddly enough the problems I am having DO seem to coincide w/ download of a 'security update.'
Hmmmm......
I would like, at the very least, a helpful suggestion from someone working for Apple - if not an acknowledgement of an actual issue with a faulty (expensive) product.
A guarantee of satisfaction with a purchase should not be wrapped up in purchase of a service plan - good customer service is good policy, and should be provided as a means of standing behind the quality of a product you both sell, and believe in.
There is no good reason why my computer should be broken, and there is no good reason why it shouldn't be fixed - and I see a lot of you have even more reason for complaint than I do. It is irksome in the extreme that this issue seems not to warrant the attention from anyone who can make a difference to our plight.
One would think that a drop-down menu on an official web-site would have a better response rate from affiliated 'professionals' - but we all know the old adage about assuming...
Hey - maybe customer service really is dead - and I might believe that if it weren't for the fact that I respond, personally, to customer e-mails on a daily basis...
Where is our response?
I apologize for the lengthy "blog" - but short and sweet hasn't done the trick..maybe this will?? We can only hope...

Is there still no fix for airtunes?

can not get airtunes to work at all with airport express. the speaker thing in the bottom right of itunes doesnt even show. ive seen posts for fixes for macs, but nothing for xp. and ive not seen anyone else complaining about it.. did i miss a fix or something?

Hi itsjustnoise,
Welcome to the forum! I trust you've tried the basics? In Airport admin (which I'm sure you have a form of on the XP side). Open it up, click configure on your AEX. You'll see tabs for Airport, Internet, Networking, Port Mapping, Access Control, WDS, and Music. Click "Music." Make sure you've checked "Enable Airtunes on this base station"
Over in your iTunes music player, go to preferences, make sure under the "Advanced" tab, in the "General" section, you have clicked "Look for remote speakers connected with Airtunes"
Check that. If still no love, I can't help you any farther.
Good luck

Still no fix for Thunderbolt front facing camera?

I have tried all the online known fixes for this issue , clearing data, restarting phone, removing all other camera applications, and still cannot get my front facing camera to work on my Thunderbolt. As soon as I select the front facing camera, the application closes-without any error message-and brings me to the home screen. What is going on? I was able to use it this Spring, and then all of a sudden I can't use it anymore. Please help.

This has to be an VZW OTA error or something, because my Moto Droid and my kid's HTC Droid's front-facing camera stopped working almost simultaneously. Very suspicious that would happen under any circumstances.
Before you do a hard reset, try this:
Pull the SD card and your camera should start to work again.
After that, you can put the SD card back in, and it should still be working.

Where is the "quick fix" for the "insuffient data" bug in 9.5.2?

Adobe alludes to a quick fix for this acknowledged but says contact a support team to request it.
Please consider this a request that the fix be PUBLISHED for all.
Thank you.

Acrobat engineering would like to inform users facing this issue that the latest Reader XI release (available for download from http://get.adobe.com/reader) fixes this problem. Users are requested to download the latest version at the earliest to avoid encountering this error going forward. As mentioned earlier, the team is working actively towards fixing the problem in earlier versions (10.x and 9.x) as well and expects to deliver a solution by Q1 2013. For more details, you may refer to the blog post here

So is there a fix for this Time Zone bug?

apple, is there a fix to this Time Zone bug in Calendar?

You are not talking to Apple, just other Apple users. If you are experiencing something you think is a bug, you will have to describe it or reference some description. I am unaware of any specific Time Zone bug.

Still no fix for Photoshop Install / Update Error? (Exit Code 15 - inconsistency in installer db)

I have tried every suggested fix to no avail... what gives Adobe?
- Removed all versions of Photoshop
- Started in safe mode
- Used cleaner tool
- Used plist method
All apps update except Photoshop and I can't install at all on other MacBook Pros.
Can we please get a fix for this? So many threads on this topic from other customers!!!

After using the Adobe Clean tool, I checked its output log and it mentioned it couldn't find a "caps.db" in the Common Files/Adobe/caps/ folder under Program Files or Program Files (x86).
So what I did: I manually deleted the Adobe folders from:
- Program Files
- Program Files (x86)
- Program Files (x86)/Common Files
After that, I was able to install successfully Photoshop CS5.1 and at this very moment I'm able to install PS CS6 (it's been already 50% of the installing progress).
So far, this action of deleting the Adobe folders from my Program Files folders seems to be sorting out the matter...

Still no fix for Chapter Markers exporting in H.264 Blu-ray for Encore import Error

Why didn't this fix take place in the recent PPRO 2014.2 update?
I still get the error in Encore that I can import the movie file due to chapter markers.
Does this mean we cant any more use Encore for authoring DVDs or Blurays?
Really don't like the Delete the chapter reference file to do this.

The bug appears fixed to me.
First, I updated only AME to 2014.2. I exported directly from PR 2014.1, and, as expected, the xmpses file is malformed and import to Encore fails. Export using the queue (and therefore clearly AME), the export shows a corrected xmpses file, and import to Encore works.
Then I updated PR to 2014.2. Now, direct export from PR also works.
I did not test updating PR and not AME, and that might present a different result.
What are your versions of PR and AME?
Edit: couldn't resist. Rolled back AME to 2014.1 with PR still updated to 2014.2. Direct Export from PR works.

Rings only once - still no fix for this flaw?

Any help here appreciated. I also have the problem where my 8310 rings only once after vibrating. In fact it goes back to vibrating after ringing the one time.
The suggestion to contact the carrier and lengthen the amount of time before sending to voicemail doesn't fix the problem, or even make an acceptable work-around in my opinion, because:
- It does no change the problem because it has nothing to do with the problem (the problem is with the phone)
- Even if it did work, it would inconvenience the caller to have to wait so long for me to either pick up or go to voicemail
- It worked fine on the Pearl, which had a 15-second time
The problem is that it goes:
vibrate - vibrate - vibrate - ring - vibrate - vibrate [off to voicemail]
15 seconds are enough time to what is normal and correct, but not happening for me:
vibrate - vibrate - vibrate - ring - ring - ring [off to voicemail]
If the waiting time is increased to 30 seconds, there is just more of the same problem:
vibrate - vibrate - vibrate - ring - vibrate - vibrate - vibrate - ring - vibrate [30 seconds up, off to voicemail]
Please tell me there is a solution to this apparent flaw. I would have gotten a proper phone if I had known there would be this hassle by getting a new BB. I feel like sending a bill to RIM for all my wasted time on this matter.
What I don't get is that this apparent bug has been around for a long time, yet my Curve bought last week still has it, and I have not found a proper solution to the problem yet. Either I am missing something or does BB not come out with patches for bugs / design flaws?

OK, here's what makes no sense - my coworker has a 8310 just like mine, but his works fine - it vibrates first, then it rings multiple times as it should. With the exact same settings in 'profiles', mine rings only once.

Still no fix for two annoying Lightroom 5 bugs

Similar Messages

Maybe you are looking for