Lightroom CC2015.12/6.12 was released today and should address this issue. Please update your Lightroom to the latest version and let us know if you continue to see the issue. Thank you for your patience.
Why can't I update LR to fix this problem? I have a standalone version v6.3, but it tells me I need CC to do the update. However a few months ago I was asked to do an update and there was no problem with that. Help please!
Use the Adobe Creative Cloud app to update Lightroom. If the update doesn't show as available after refreshing the app [Ctrl/Cmd+[Alt/Opt]+[R]. Use the CC App to uninstall Lightroom, restart, and then use the app to reinstall Lightroom.
Lightroom 4.4.1, camera raw 7.4, windows 7 and as of 2 Sept the map module is not working. Blank page with "map is offline" message when switching to map module or when switching map style. Interestingly, when I enter an address in the search window the search is performed, the address is updated, i.e. if I enter "Reno" the search returns "Reno, NV, US", and a yellow marker appears on the black screen. To me, this indicates that the map is in fact online. This is really annoying that the problem is not solved yet.
I am still having map problems after the July 2017 update. Now when I zoom in on the map, blank grey boxes appear on the map, sometimes with "sorry no imagery here" written on them, and the map zooms back out. This is in Hybrid and Satellite mode, the road map mode works properly.
MacOS 10.12.6, latest release of LR. This problem has been around for ever - why don't you just fix it (and all the other bugs that linger year after year) instead of constantly telling us CC users that you have our best interests at heart and want to make LR a world-beater?
This problem has not been around forever - it began in June when Google changed something. Are you really sure you do have the latest release? It fixed this problem. Go to Help > System Info, and copy the first line. It should show 2015.12.
Version de Lightroom: 5.7 [991162] Type de licence: Perpetual Système d'exploitation: Windows 7 Ultimate Edition Version: 6.1 [7601] Architecture de l'application: x64 Architecture du système: x64 Nombre de processeurs logiques: 4 Vitesse du processeur: 3,5 Ghz Mémoire intégrée: 8083,7 Mo Mémoire réelle disponible pour Lightroom: 8083,7 Mo Mémoire réelle utilisé par Lightroom: 480,6 Mo (5,9%) Mémoire virtuelle utilisé par Lightroom: 447,5 Mo Taille de la Mémoire cache: 1,3 Mo Nombre maximal de privilèges utilisés par Camera Raw: 4 Paramètre PPP du système: 96 PPP Composition sur le Bureau activée: Oui Affichages: 1) 1680x1050
So this means that as an otherwise happy version 5.7 user I should buy a new version again... That is not cool. I only bought my LR as my otherwise great Elements did not support my new camera raw. Maybe I should find some other product, GIMp or similar to do basic RAW editing and conversion
I just want my current Lightroom 5.7 to continue working with the GPS-map function, which was fine until some time ago. I am not interested in monthly subscription methods or any new features, however fantastic they may be. I think it is nearly criminal by Adobe to require expensive updating to a otherwise working programme.
Yeah, of course you want that. Free updates for the rest of your life. Who wouldn't want that? It is absolutely criminal that people at Adobe want to get paid for their work!
As if providing an essential fix for for free has anything to do with people's pay-checks at Adobe. That is not how things work at an organization like Adobe. So that comment is nonsense and does not help anyone here (not even the people at Adobe).
Johan Elzenga; This is not a question of updates for life. It is a question of Adobe breaking something that was working thus forcing customers with a perpetual license to upgrade to maintain functionality. This is typical of Adobe. I did not originally choose Lightroom. Adobe bought another software company to eliminate it from the market place and a "upgrade" to that software put me in the Adobe dependency.
Pete, there is plenty of feedback now that the problem is NOT related to a specific computer system nor LR version. Can you please take action and contact Google for verification if their server acts up and give us feedback? Thanks in advance.
Indeed, i'm having it on both Windows 10 creators update as MacOS 10.12.5. On both machines it appears with the latest LR update. https://youtu.be/wZ8rmDGOg-Y
Pete, you seem to be the only Adobe person taking any note of this issue. This is a serious problem for many of us. Can you provide some update on the status of an Adobe response.
I would like to copy all of the above. The issue is so widely discused that it seems (at the least) a matter of ignorance to scale this down to a personal and individual issue. Since some two years every "update" comes along with new bugs. That's not what I know from my long Adobe-past ... Over a decade you produced solid and stable software with new features in every yearly upgrade. With the big business succes, those days seem to be over. That the newest Version still has "2015" in it is a good indication, that real progress stopped and since then updates are merely bug-fixes, introducing new bugs every time. So stop asking "standard questions" and start doing your job properly!! If I as a photographer and designer would deliver that way to my customers, I would have been long out of business by now ...
And as a photographer you shouldn't require Lightroom because your photos would be perfect out of camera. Why does every little hiccup bring out the trolls?
George's other comments don't seem like he's trolling so I have no idea what to make of such a moronic assessment of the situation. Not wanting to keep paying for a broken product does not make someone a troll, or an unreasonable consumer, or a bad photographer. And Kees is not alone. I have zero use for Lightroom in the next 30 days other than to geotag photos from a recent cross-country trip. Why on earth wouldn't I cancel my subscription until they resolve this issue?
For starters, if the name didn't include "2015" the features in the 10 releases (plus sub releases) would not be perceived as bug fixes. I geotag every image so this is important to me as well, yet I am able to geotag even with this nuisance glitch. The fact that Smit Keniya and Victoria have confirmed that Adobe has acknowledged the issue after a couple of days of it being reports suggests to me that Adobe is indeed listening and responding. To Norbert, the point is that software is extremely complicated of interrelated functions where minor issues can sometimes results in bugs. Adobe does not claim to be perfect, and evidently unnamed photographers aren't perfect either, or they wouldn't need software like LR. This simply is not a catastrophic situation, message boards like this are to raise issues that come up, and it has been my experience that Adobe address such issues when brought to their attention. Using this forum for whining dribble is simply addle.
5 days ago "must be a Google server problem".... I'm glad we have people like you that understand the system. Let's hope Adobe is using this time interval to do more research than you demonstrate before drawing a conclusion.
Same here, w/ the addition of error emphasis. It grows somewhat wearisome considering the lease fee I pay every month never to own this software that never even came with any paper books (that I didn't buy separately on my own for extra money) to help me learn it.
It also doesn't tend to produce things that look the same on my 4K monitor, someone else's SVGA setup, or on paper no matter what I tell it.
This is all using the combo of Windoze 10 / 64 bit & Adobe PS/LR CC 2015.10.1 Release Camera Raw 9.10.1
I'm having this problem lately. I have a MacPro (mid 2010) running 10.12.5 Sierra and Lightroom CC 2015.10. I have lots of RAM (32 GB) but the system seems really slow lately
Me Too, Lightroom version: CC 2015.10.1 [ 1117303 ]License: Creative Cloud Operating system: Mac OS 10 Version: 10.11 [6] Application architecture: x64 Logical processor count: 8 Processor speed: 2.0 GHz Built-in memory: 8,192.0 MB Real memory available to Lightroom: 8,192.0 MB Real memory used by Lightroom: 2,412.1 MB (29.4%) Virtual memory used by Lightroom: 4,416.8 MB Memory cache size: 1,352.0MB / 1,856.4MB (72.8%) Maximum thread count used by Camera Raw: 8 Camera Raw SIMD optimization: SSE2,AVX Camera Raw virtual memory: 1291MB / 4095MB (31%) Displays: 1) 1440x900
Graphics Processor Info: Check OpenGL support: Failed Vendor: ATI Technologies Inc. Version: 4.1 ATI-1.42.15 Renderer: AMD Radeon HD 6490M OpenGL Engine LanguageVersion: 4.10
Me Too, Lightroom version: CC 2015.10.1 [ 1117303 ]License: Creative Cloud Operating system: Mac OS 10 Version: 10.11 [6] Application architecture: x64 Logical processor count: 8 Processor speed: 2.0 GHz Built-in memory: 8,192.0 MB Real memory available to Lightroom: 8,192.0 MB Real memory used by Lightroom: 2,412.1 MB (29.4%) Virtual memory used by Lightroom: 4,416.8 MB Memory cache size: 1,352.0MB / 1,856.4MB (72.8%) Maximum thread count used by Camera Raw: 8 Camera Raw SIMD optimization: SSE2,AVX Camera Raw virtual memory: 1291MB / 4095MB (31%) Displays: 1) 1440x900
Graphics Processor Info: Check OpenGL support: Failed Vendor: ATI Technologies Inc. Version: 4.1 ATI-1.42.15 Renderer: AMD Radeon HD 6490M OpenGL Engine LanguageVersion: 4.10
@Georg Nichols: Pro photographers do use Lightroom in the first place as a RAW converter and catalogue application. This has nothing to do with being perfect or not ... Your comment on that is out of line and just shows you have no idea ... It's not that we respond to every hickup immediately, in fact this is my first contribution whatsoever. If you read well, you'll see I was over many many years a very satisfied Adobe-customer, but it is a stonecold fact that every update comes with NEW flaws over the last two years, that are time consuming, irritating and in some cases cost plain money. For instance buying an expensive new graphic card (recommended by Adobe) that doesn't work well with both Lr and Ps after all and is a waist of money. That is not why you pay for a professional tool, that can be toroughly tested before bringing out. Adobe is no small shop around the corner and their shares are exploding. So can't be a financial problem to do a good job in advance, instead of annoying us with work frustrating issues. When things get to complicated to have it running stable, one should consider being on the right path. That's what every professional should do ... I stick to my comment that quality (in stability) has dropped shortly after anybody got neatly caught in cloud construction and one has no longer to convince customers buying new stuff ... That's almost a business rule of thumb and was therefor a predictable development. And another rule of thumb in business: If customers complain, they are ALWAYS right. Your product is customer satisfaction after all .... The least you may expect is a newsletter saying "sorry customers, we have acknowledged a problem, we are on it and we expect to have it fixed by .... " That's what we pay for 50 bucks month after month, not to be ignored or having to find out in groups like this, that Adobe is working on it (if this information is right). You know Franz Kafka?? Well, that is exactly what this is all about. Small customer knocking without reaction on the door of a big powerful ruler of the system little man is caught in.
Also have the problem. I'm running Windows 8.1 and Lightroom 6.10.1, build 1117303. I first noticed the problem yesterday after a big Windows update, but this might be a coincidence.
I hadn't updated Lightroom until after I noticed this problem - I hoped it would cure it - but I'm not sure of the exact version I was running before. Everything else on the laptop seems to be OK. The broadband connection's fastish, but pretty reliable.
Same problem here with Mac OS Sierra 12.4 and LR CC 2016 2015.10 Everytime I resize or move the map in map module I get a 3 second blacked out map and an error window Map Offline and then map is back to work. It all started 3 days ago out of the blue. Please research and fix. Its very annoying.
I haven't been using Lightroom for a week or so, but this was not happening to me when I last used it. Now it is happening big-time (and, boy, is it annoying).
Lightroom 2015.10.1 Camera Raw 9.10.1 MacOS 10.12.5 iMac 5K 27 inch, late 2014
Happens with my set up and been so for a number of LR iterations. Found best way to clear it is to restart LR which suggests it's a cache related issue.
I agree. Problem occured on iMac and MBP at the same time about 5 days ago. Both on the latest OS. Both LR 6.10.1. Problem started when on LR 6.8. Upgraded in the hope that that would cure it, but no.
Same problem here, started two days ago when Adobe CC LR was updated. System: MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports) macOS Sierra v.10.12.5. (16F73) Lightroom Map function has worked fine from year of launching, on differents Mac computers, but crashed when I updated LR on June 14.
Same here. It's clearly not specific to any OS or hardware.
ps: this site would benefit from providing an error message to people who try to log in but don't have third party cookies enabled. As it works now, they just have their login accepted but nothing happens and they can't do anything and get no feedback as to what's going on.
Responses
Official Solution
Rikk
Adobe Administrator
•
8.2K Messages
•
118.3K Points
3 years ago
http://blogs.adobe.com/lightroomjournal/2017/07/lightroom-cc-2015-12-now-available.html
Adobe Photography Products
Quality Engineering - Customer Advocacy
10
patrick_fondan_che
14 Messages
•
276 Points
3 years ago
26
petegreen
Adobe Administrator
•
780 Messages
•
16.7K Points
3 years ago
Can you provide more details, such as OS and version? Lightroom exact version?
Regards
Pete
15
iain_burke
2 Messages
•
110 Points
3 years ago
I hadn't updated Lightroom until after I noticed this problem - I hoped it would cure it - but I'm not sure of the exact version I was running before. Everything else on the laptop seems to be OK. The broadband connection's fastish, but pretty reliable.
2
0
alan_harper
474 Messages
•
10.5K Points
3 years ago
Lightroom 2015.10.1
Camera Raw 9.10.1
MacOS 10.12.5
iMac 5K 27 inch, late 2014
LR hasn't crashed yet (as others have reported).
Let me know if I can help track this down.
1
0
paul_gibson_eq1bvv7d3e0us
9 Messages
•
162 Points
3 years ago
Mac OS 10.12.5. Lightroom - most recent version, whatever number it is.
0
0
steve_chasey
22 Messages
•
460 Points
3 years ago
1
0
chris_parry_cobbch3gssq85
3 Messages
•
140 Points
3 years ago
Windows 10 64 Bit
Lightroom 2015.10.1
Tried restarting PC and still happens.
0
todd_shaner_6660895
Champion
•
2.2K Messages
•
37.1K Points
3 years ago
0
0
norbert_pauli
12 Messages
•
422 Points
3 years ago
1
0
john_rangtveit
4 Messages
•
120 Points
3 years ago
System:
MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports)
macOS Sierra v.10.12.5. (16F73)
Lightroom Map function has worked fine from year of launching, on differents Mac computers, but crashed when I updated LR on June 14.
1
0
wouter_van_de_weerd
1 Message
•
66 Points
3 years ago
Windows 10
Lightroom CC 2015.10.1
Internet connection via ethernet cable (not wifi)
0
0
mark_den_hartog_6737258
49 Messages
•
752 Points
3 years ago
3
0
michalcizek
3 Messages
•
104 Points
3 years ago
0
0
scott_burnette_e2ywma4hsvqrk
9 Messages
•
174 Points
3 years ago
ps: this site would benefit from providing an error message to people who try to log in but don't have third party cookies enabled. As it works now, they just have their login accepted but nothing happens and they can't do anything and get no feedback as to what's going on.
0
0