Lightroom 5.3 Fullscreen bug

Hi!
After I updated my LR to version 5.3 I immediately noticed that the shortcut Shift + F doesn't work anymore. And I can't switch to fullscreen at all. Is there anyone else having the same problem?

I'm also on 5.3, and have no problem with Shift F (or F for that matter). I'm on Win 7. What is your operating system?
Hal

Similar Messages

Lightroom 1.2: XMP-bug still present and some other things

* I just upgraded to 1.2, but the XMP-bug is still present. When I turn on autowrite XMP LR starts using 50% (1 of 2 cores) of my CPU for quite a long time (15+ minutes) after startup. During that time the interface is somewhat sluggish (probably because of the lack of multi threading).
This behavior was also present in LR1.1. Turn off autoxmp and the cpu-usage will drop to 1-2% within a few moments of starting LR. Turn it on, and it will use your cpu for quite a long time (29.000 photos in my DB).
* One other thing I still notice: when using identity plates for printing, the identity plate doesn't rotate with the photo when switch from a landscape to a portrait photo (auto rotate is on to make things a lot easier). The print module is one of the greatest things in LR, but this still annoys me)
* Decent support for multi core CPU's is still lacking it seems. I have to run two export batches simultaneously to get my CPU to 100% cpu usage. Maybe it's an idea to split one export batch into several smaller ones so the can be processed at the same time using both cores.

1.2 fixes a bug in the auto-write mechanism that severely effected the performance of auto-write when files with changes were offline. Unfortunately, we didn't have time in the cycle to drastically enhance performance of the XMP auto-write mechanism for making large batches of changes or toggling the option on and off. The Lightroom team is aware of these issues and is working to resolve them for a later release.
The wording of the download page is pretty obscure. For a more accurate, detailed review of the changes in 1.2, please refer to the blog post at http://blogs.adobe.com/lightroomjournal/ . For a better understanding of ways to use the auto-write mechanism in the interim, check out my post at
Dustin Bruzenak, "Performance & Auto-write XMP" #, 10 Jul 2007 8:29 am
Dustin Bruzenak
Lightroom Engineering

[Mac, Win] Fullscreen Bug?

Hello!
Sorry for the lenghty post but maybe someone can confirm the problems I am seeing:
There seems to be a bug in both Windows and Mac versions of Photoshop CS6. The problem manifests itself MUCH clearer on a Windows machine, but is present to some degree on a Mac, too. The last version without it seems to be CS3 (OpenSth problem?).
Steps to reproduce: Any image open, full screen mode, all pannels UNDOCKED:
Correct behoviour: The image should not move while pressing Tab (ideally it shouldn't even redraw).
On Windows:
With every press of a Tab key to show/hide the panels the image jumps up several pixels (sometimes also towards the center of the screen if the image is smaller than the screen area). Also (and MUCH more annoyingly) when the image is moved off center and is at certain magnification (the most reproducible seems to be 33%) after pressing Tab it jumps ALL THE WAY to the center of the screen.
On Mac:
Similar things happen, but more rarely, and the image jumps by only ~1 pixel. (Easier to observe if you first zoom the image smoothly a bit by dragging with a zoom tool).
Also as it currently is (after CS3?) pressing F produces the same outcome as pressing Shift+F - there is no way of just showing the menu in Fullscreen mode and then quickly hiding it after use - one have to go through the whole screen mode cycle. Also on Windows there is no way to access the menu when hidden with Alt + Letter speedkey (Alt + F for file menu etc.). Both these functions worked perfectly well in CS3.
Both machines have latest Photoshop, OS updates and drivers (but old graphics cards: Win - Nvidia 9800GT, Mac Nvidia 880GT). I suspect these changes for the worse has been introduced while switching to OpenGL. Hopefully it is not necessary for it to be that way or maybe even it works as expected on newer graphics hardware - anyone care to check?
Last time similar problems occured was, if I remember correctly, in Photoshop 7 when Status Bar has been moved into an image window :-)
I know it may sound as if it's not important, but it certainly is annoying. It has nothing to do with not embracing change - I do find OpenWhatever to be a huge leap for Photoshop - even if I have to put up with a slower image redraw most of the time...
So, I hope, my rumblings aren't comparable to:
http://imgs.xkcd.com/comics/workflow.png
Regards
m.

Thank you.
Unfortunately, I don't have Navigator open (opening it doesn't make any difference). The image jumps in fullscreen mode without the menu, because when I press Tab, the menu shows anyway and the image (incorrectly) moves down to accommodate it and then up again, after another Tab press.
The wholly unreasonable behaviour of image being centred with Tab pressing has no such explanation and is not happening on a Mac at all.
Your suggestion to use Shift F and then F works, but since Tab shows the menu anyway - it kind of doubles that functionality.
I just think that the old behaviour of being able to show just the menu, separately from the panels or access it with Alt + Letter keys was more convenient than current behaviour. The image always stayed exactly where it was - no need to redraw. And it NEVER jumped whole way to the center - which makes dealing with image corners extremely difficult.
I can understand that some of that may be the a requirement of using OpenGL on Windows, but I kind of doubt it.
Regards
m.

Lightroom 6 photo jumping bug

So I'm trying LR6 and I have this really strange and quite annoying bug. Whenever I make some action in Development module. A previous photo momentarily shows up, then screen jumps back to proper. See the video... any clues as to what this may be???

Please ask in the Lightroom forum. Look the forum up in the forums directory.

[Solved] Chromium Fullscreen bug

Hi everybody!
Please help me to resolve chromium bug.
After going to fullscreen by pressing F11 everything OK.
But after returning to windowed screen by pressing F11 again chromium disappears from the screen and becomes unaccessable.
But it still remains running in the list of precesses and its icon seen under Alt-Tab switching.
This bug exist even in empty window with no URL connected.
Linux 3.15.8-1-ARCH #1 SMP PREEMPT x86_64 GNU/Linux
Window manager: openbox 3.5.2-6 (lxde) [installed]
Also idesk program for icons running.
Last edited by roina (2014-09-17 19:05:15)

Sam_DM, thank you for help, but it doesn't work.
This bug takes place on 3 PC that I use, 2 of them with Intel video and the rest with Nvidia card.
On one of Intel PC you suggestion leads to different behavior of chromium. After disappearing it becomes possible to return browser to a visible state by another pressing F11. Ironically, even if you method worked it was useless for me, because I use chromium only for one online game which supports hardware acceleration under linux only in chromium. But my main browser is firefox.
Also I examined chromium on the same computers under ubuntu live distribution and it worked fine.
Therefore I conclude that something wrong in chromium package for archlinux or maybe more installed supported programs needed.
I shall try to report a bug to chromium officials but don't have experience in that.

Fullscreen Bug

Hi
There is a big bug with fullscreen Aps
When, for example, the Mail Application runs in Fullscreen Mode and I open Firefox (for example) on the main desktop and switch to the fullscreen app while firefox is loading, Firefox will be opened on the same desktop as the fullscreen app.
Another Bug is: When in Fullscreen Mode some dialog boxes (like Search Text) will open on the main desktop
Any solutions or bugfixes yet?

well, the dock does not give me any usefull possibilities... the only solution is to close the app and reopen it.
5 minutes ago, a message from an installer told me to close 2 application to continue the current installation (xcode).
first i thought, the installer stopped because it did not do anything else than showing a status bar... then i looked on the fullscreen mail desktop and there was the information box

Lightroom 3 - Flickr Publish Bug

I am experiencing an issue where when I publish images to Flickr they immediately show up as "Modified Photos to Re-Publish" and will not ever move to the "Published" section even though I have not changed a thing.
Anyone have any ideas as to what I am missing?
Thanks!

Although not related to the original post – “Stuck in republish”, which I think is now fixed; here is my take on the situation you are describing -
I suspect there is a bug in the LR software which is still present in LR 3.4RC.
I believe this bug manifests itself in two ways when an attempt is made to republish an existing published photo …
1)      If you are privately publishing and attempt to republish an existing photo, then LR sends a parameter (“Hidden” from public searches) incorrectly and out of bounds in accordance with the Flickr API, and Flickr quite rightly rejects it.   I suspect LR is sending values of 1 or 2 (Hidden or not) for this “hidden” parameter when it should be sending 0 or 1 to the set safety level function.
2)      Probably related to the same technical reason as point 1 - if a non-private photo is republished then instead of the photo continuing to be made available in public searches it is now erroneously made hidden from public searches when it reaches Flickr – again 1 or 2 instead of 0 or 1.   This is somewhat annoying if you go through a re tagging exercise for the benefit of public searching only to find that they are now hidden from searches once re-published.
I have seen no confirmation from any other user of point 2 above despite posting the question here ...   http://forums.adobe.com/thread/796350
Further points …
Since the Lightroom Software Development Kit contains a sample of the Lua code which is used for publishing, I have pointed to the actual lines of code I suspect are in error in this thread which also contains some technical dialog with Matt Dawson a Community Professional …
http://forums.adobe.com/thread/821148?tstart=0
I have raised a bug report with this technical detail, and raised a bug report for each of the two cases I mentioned above.     Hopefully this may result in some action, but I would suggest that if this important to you that you also raise a bug report, as there appears to be, to some an extent, a principle of - they who shout loudest or most often will get priority.
As a side note … to cure the problem for the moment, although I don’t want to use third party software long term, I have adopted a Flickr publishing plugin by Friedl for my private publishing until this is fixed.    If you Google “Friedl Flickr” you will find it.     I have not yet decided to adopt this plugin for my public publish due to concern about the possibility of losing all comments and favourite tagging by other Flickr members – I simply do not know at this point.
It is also interesting that the change log for this Friedl plugin on his web site also describes being tripped up by the same peculiarity present in the Flickr API which probably gave rise to this mistake by Adobe.    The Flickr API may have its peculiarities, but it is well defined and this is a Lightroom bug in my opinion.
Alan.

Fullscreen bug in AIR 2.5

We built a flash application which was packed with AIR v1.0(current
version at that time), which by default opens in full screen mode
we had added a button within the application which uses the following
code to minimise the application
This code minimises the application till AIR runtime v2.03. Once the
runtime is upgraded to V2.5 the application stops to go fullscreen in
the below scenario
After upgradation if the user clicks minimise button, and then tries
to restore the application by clicking the application tab in the
taskbar, the application fails to go fullscreen
It remains as a borderless window with a partial portion of the
application displayed
Thereafter the user has to force quit the application and relaunch
This application series is our largest seller, and we are deeply
concerned of the Windows and Macintosh versions
We would really appreciate a quick response
Sanjay
Code
/* To minimize the window- on click the minimize method is called*/
windowChanger.minimise.
addEventListener(MouseEvent.CLICK,minimize);
private function minimize(event:MouseEvent):void
            myWindow.minimize();
            trace("minimize the window");
/* To maximize the window- onActiviate method is called*/
this.addEventListener(Event.ACTIVATE, onActivate);
public function onActivate(evt:Event) {
            stageDetails();
public function stageDetails():void {
            stage.scaleMode=StageScaleMode.NO_SCALE;
            stage.displayState = StageDisplayState.FULL_SCREEN;
            stage.displayState = StageDisplayState.FULL_SCREEN_INTERACTIVE;

For those following along, Sanjay and I have taken the discussion offline and he provided me with a couple of sample projects. I've been able to reproduce the issue on AIR 2.5 and it has now been entered as a bug in our internal database, #2751098.
I've also proposed a workaround that appears to work on both Mac and Win. Instead of
this.addEventListener(Event.ACTIVATE, onActivate);
public function onActivate(evt:Event):void
     stageDetails();
I've suggested using
stage.nativeWindow.addEventListener(NativeWindowDisplayStateEvent.DISPLAY_STATE_CHANGE, onDisplayStateChange);
public function onDisplayStateChange(evt:NativeWindowDisplayStateEvent):void
     if (evt.afterDisplayState == NativeWindowDisplayState.NORMAL)
     stageDetails();
I hope this helps anyone else that might encounter this issue.
Thanks,
Chris

Lightroom 5 Final, Big bug with Function "Light Dim"

Hello,
Found this bug in many Pcs (With Win 7) in x64 Bits AND x32
When i use the option "Lights Dim" (in Menu "Lights Out") when i quit Lightroom 5, lr 5 Crashes after the ending.
Receive windows message "Lightroom 5 Has Chrashing ...etc..."
I search to understand, and i think have know.
Before the V5, no crash (V4.4. for exemple), and with this versions, "Lights Dim" function is intergrate into "lightroom.exe"
With the Lr5 Version ONLY "Lights Dim" is extrenal ans is used by "Slideshow.Dll"
For verify this, very easy, just move "Slideshow.Dll" in you desktop, and you see the "Lights Dim" not run.
After always testing, you see also the Option "Light Off" runs always good, and "Light On" same.
This in one little piece of this 3 function is external, it's very dirty, and crashes.
Pse (developpers) note this bug and in 5.1, integrate this 3 functions into Lightroom5.Exe
Best regards, and sorry for my very bad English

I am having the same issue and wondered what was the issue. Thank you for posting; now I remember Lightroom didn't start doing this until I updated to Mac OS Maverick. The only time I don't have that problem is when I physically disconnect my secondary display from my computer.

Fullscreen bugs in Air 2 apps under client Air 2.5 runtime?

We produce video distribution apps handling DRM in Air 2.0
We've encountered quite a serious bug in our Air applications' handling of Flash when going fullscreen.
Under Air 2.0, our apps were fully functional. No issues.
After the upgrade to Air 2.5, all PC installs no onger display video content in full screen when prompted to do so.
We have noticed the same error occurs in AMP 1.8 and are yet to find an example of an Air application that does not experience this issue.
As the bug is isolated to PC (not present on Mac at all), is it related to either:
a) Flash handling of the Output protection enacted with this update or
b) h264 hardware decoding
We have over 30K apps deployed and seek information regarding a resolution for this asap.
We have drafted a workaround, but it is not an ideal situation.
Is Air 2.5 being updated again (within 48hrs)?

Hello,
I'm sorry you've run into this fullscreen playback bug. We found this issue with AMP after the release of 2.5 (internal bug #2732895) and it will be fixed in our next release. Adobe announced yesterday that an update to Flash Player would occur on or before November 9th. Typically AIR and FP releases occur in tandem.
In our testing, we were only able to reproduce the issue with Adobe's Media Player, attempts to reproduce using AOL, BBC iPlayer, or MovieFone were unsuccessful. Could you point me to another example where this bug occurs? I'd like to verify it's fixed on more than one application.
I'm going to follow up with you via the forums private message system, you can also email me at [email protected]
Thanks,
Chris

Fullscreen bug with specific button on Mavericks rMBP 2013

Hi Everyone,
Encountered a weird bug on my GF's new rMBP with facetime. The camera will turn itself off during face time if she fullscreens the app using the fade in fullscreen button on the top right corner of the app. Sometimes the green light will stay off the whole time it is fullscreened, sometimes it will stay off for a second, then turn back on and the other end of the conversation may or may not see the pause icon. This doesn't happen when she uses the menu or the persistant bottom right hand corner fullscreen button.
I don't know why it is only that particular button, but it happens. Not a major issue, but just a weird annoyance and wonder if anyone else has seen this problem or if this is a know bug that will be addressed in the future. I've tried to clear out the keychain, thinking it was that, but no go.
Regards,
Mike

For those following along, Sanjay and I have taken the discussion offline and he provided me with a couple of sample projects. I've been able to reproduce the issue on AIR 2.5 and it has now been entered as a bug in our internal database, #2751098.
I've also proposed a workaround that appears to work on both Mac and Win. Instead of
this.addEventListener(Event.ACTIVATE, onActivate);
public function onActivate(evt:Event):void
     stageDetails();
I've suggested using
stage.nativeWindow.addEventListener(NativeWindowDisplayStateEvent.DISPLAY_STATE_CHANGE, onDisplayStateChange);
public function onDisplayStateChange(evt:NativeWindowDisplayStateEvent):void
     if (evt.afterDisplayState == NativeWindowDisplayState.NORMAL)
     stageDetails();
I hope this helps anyone else that might encounter this issue.
Thanks,
Chris

Lightroom 4.3 import bug

Why is an image imported into Lightroom 4.3 significantly lighter than the same image displayed in Windows Photo Viewer at the same time and on the same screen?
This basic problem also applies when using an external editor such as Elements 11 where the image is returned much lighter than what appeared in Elements.

Thanks for your reply.
I take your point about windows Photo Viewer but what about Elements 11? Also if the two versions of the image were displayed on the same monitor at the same time would that not invalidate the need for screen calibration?
As perhaps a better demonstration of the problem, if I export an image to a jpg with "add to this catalog" checked the added jpg is returned significantly lighter.

Lightroom 5.3 Export Bug

During and after exporting a batch of photos, Lightroom will apply changes to the group of photos being exported, even if they are not selected and another photo (not being exported) is selected. I haven't seen a discussion on this, but I do know that 5.0 had major selection issues. This problem has caused me more than 3 hours of pain tonight!!
Steps to repro:
1) Select several photos to export
2) Start exporting
3) Select another photo in the catalog not being exported
4) Make changes (such as set the rating or paste settings from previous or look at keywords)
     Expected result: only the photo selected is changes
     Actual result: the group of photos being exported changes and not the photo selected!!
This continues to happen even after the export completes. Setting the rating or pasting settings from previous or setting keywords affects all of the previously exported images and not the image selected. The only way to get around this is to quit Lightroom and restart it.

I tried a new catalog with 10 pictures. I exported 1 and I do not see the problem. Will let you know when I find out more.
Here's the system info:
Lightroom version: 5.3 [938183]
Operating system: Windows 7 Business Edition
Version: 6.1 [7601]
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.1 GHz
Built-in memory: 18422.9 MB
Real memory available to Lightroom: 18422.9 MB
Real memory used by Lightroom: 2094.1 MB (11.3%)
Virtual memory used by Lightroom: 2086.6 MB
Memory cache size: 1899.0 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440, 2) 1200x1600
Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.3
Library Path: C:\Users\Noah Wardrip\Pictures\20140101 5D Scratch\20140101 5D Scratch\20140101 5D Scratch.lrcat
Settings Folder: C:\Users\Noah Wardrip\AppData\Roaming\Adobe\Lightroom
Installed Plugins:
1) Behance
2) Canon Tether Plugin
3) Facebook
4) Flickr
5) HDR Efex Pro
6) HDR Efex Pro 2
7) Leica Tether Plugin
8) Nikon Tether Plugin
9) SmugMug
Config.lua flags: None
Adapter #1: Vendor : 1002
    Device : 6898
    Subsystem : b001002
    Revision : 0
    Video Memory : 1002
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
CardID: 26776
Direct2DEnabled: false
GPUDevice: D3D
MaxTexture2DSize: 8192
OGLEnabled: true
Renderer: ATI Radeon HD 5800 Series
ShaderModel: 11.1
Vendor: AMD
VendorID: 4098
Version: 1002:6898:b001002:0000

Lightroom 2.1 History Bug with Edited File

I downloaded Lightroom 2.1 and now when I edit a file in Photoshop and then it comes back into Lightroom, if I click on one of the Presets, such as a B&W preset, then there is no way to get back to the edited file in color. The first entry in the History is the B&W preset, and I can't undo past that point to return to the color version of the edited file.
Seems like it's not making a "edit in photoshop" history item that allows me to return to the original.

I'm back trying to sort this problem out (got distracted for a couple of days by trying to get my monitor calibrated).
Rearranging the folder structure didn't help. But I now have a better organized catalog, so that's ok :)
What I did find is that if I import files into lightroom using the "file/import photos from device", then I can edit them normally afterwards (that is, when I save the file in photoshop cs3, the new file gets picked up correctly by lightroom and gets correctly stacked with the original). This is true even if the new files get added into the same directory structure that I'm having troubles with.
So it looks like the directory structure is a red herring. It looks like the problem is in the catalog, with the way that lightroom originally imported my files. I created my original catalog by allowing lightroom to read my elements 6 catalog.
It seems that I have this edit problem with all catalog entries that were imported from elements 6, but I don't have any problem with catalog entries that lightroom brings in directly (either through "import photos from device" or by adding a new folder to the lightroom catalog).
So right now it looks like there is a problem with the elements catalog conversion.
Is this a problem that anybody else has seen? Any suggestions for getting around it?
Doug

Safari weird fullscreen bug

I've got a window in fullscreen mode in Safari that's causing all kinds of weirdness.
With no other windows open, whenever I use the App Switcher to go from another app to Safari, the window shows briefly, then the OS switches to System Preferences with the Desktop & Screensaver pane on display. (??)
Same behavior when I select that window from Safari's Window menu. This behavior persists even when I quit and relaunch Safari.
The problematic window doesn't stay onscreen long enough for me to click the widget to exit fullscreen mode and close the window. Anybody know *** is going on?

I've got a window in fullscreen mode in Safari that's causing all kinds of weirdness.
With no other windows open, whenever I use the App Switcher to go from another app to Safari, the window shows briefly, then the OS switches to System Preferences with the Desktop & Screensaver pane on display. (??)
Same behavior when I select that window from Safari's Window menu. This behavior persists even when I quit and relaunch Safari.
The problematic window doesn't stay onscreen long enough for me to click the widget to exit fullscreen mode and close the window. Anybody know *** is going on?

Lightroom 5.3 Fullscreen bug

Similar Messages

Maybe you are looking for