Lightroom: Map module keeps flashing "map offline" when it's not

  • 229
  • Problem
  • Updated 4 months ago
  • Solved
  • (Edited)
Photo of Dan Hartford

Dan Hartford

  • 122 Posts
  • 53 Reply Likes

Posted 1 year ago

  • 229
Photo of Patrick Fondanèche

Patrick Fondanèche

  • 13 Posts
  • 1 Reply Like
Same for me.
Photo of Søren Langkilde Madsen

Søren Langkilde Madsen

  • 34 Posts
  • 9 Reply Likes
Still having this annoying problem.

Does anyone actually look at this this bug?
Photo of Dayve Ward

Dayve Ward

  • 42 Posts
  • 2 Reply Likes
Yep, still having this issue. Why is it taking so long to fix it?
Photo of Noosabird

Noosabird

  • 1 Post
  • 0 Reply Likes
Yes, still going. Email notification of the thread comments has stopped too. Driving me nuts.
Photo of John McGeough

John McGeough

  • 13 Posts
  • 2 Reply Likes
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. 
(Edited)
Photo of downstreamer

downstreamer

  • 2 Posts
  • 1 Reply Like
Still having this problem .. anybody listening?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3100 Posts
  • 491 Reply Likes
If you are still having this problem, please go to Help>System Info... and copy and paste the Lightroom version number found there. 

Additionally attach a screen capture showing the issue as you are seeing it. With these we can go to the engineering team for evaluation. 

Most users are reporting this fixed and if it isn't for you we will need additional information. 
Photo of Joe Bloggs

Joe Bloggs

  • 1 Post
  • 0 Reply Likes
I have this problem with 6.10 under OS X 10.12.6
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3100 Posts
  • 491 Reply Likes
@Joe Bloggs, you need to update to Lightroom 6.12. 
Photo of Paul Perton

Paul Perton

  • 1 Post
  • 0 Reply Likes
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?
Photo of john beardsworth

john beardsworth

  • 957 Posts
  • 197 Reply Likes
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.
Photo of Franck Cazaux

Franck Cazaux

  • 1 Post
  • 1 Reply Like
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
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1041 Posts
  • 395 Reply Likes
As said before: Only Lightroom 6 is updated to solve this problem. Earlier version are not updated and will not be updated.
Photo of Sune Keller

Sune Keller

  • 6 Posts
  • 1 Reply Like
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
Photo of Niall Teskey

Niall Teskey

  • 4 Posts
  • 2 Reply Likes
Me too. If Adobe knows what the fix is why can't they issue an upgrade to V5. We all paid good money for a perpetual license for this.
Photo of Niall Teskey

Niall Teskey

  • 4 Posts
  • 2 Reply Likes
Or at least let us know if there is any work around.
Photo of Chris

Chris

  • 8 Posts
  • 0 Reply Likes
They must be joking for not fixing Lightroom 5.7. Adobe is really getting worse every year.
Photo of Paul van Uffelen

Paul van Uffelen

  • 2 Posts
  • 1 Reply Like
I think this is a shame. I will leave Adobe for this
Photo of Paul van Uffelen

Paul van Uffelen

  • 2 Posts
  • 1 Reply Like
I think this is a shame. I will leave Adobe for this
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1041 Posts
  • 395 Reply Likes
As far as Adobe is concerned, you already left (because you didn't buy Lr6).
Photo of Lars Jakt

Lars Jakt

  • 1 Post
  • 0 Reply Likes
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.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1041 Posts
  • 395 Reply Likes
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!
Photo of Chris

Chris

  • 8 Posts
  • 0 Reply Likes
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).
Photo of Dempsey Darrow

Dempsey Darrow

  • 1 Post
  • 0 Reply Likes
This is still an issue on Mac with the latest update for Lightroom Classic CC Release 7.3.1, Camera RAW 10.3
Photo of Pete Green

Pete Green, Customer Advocate

  • 710 Posts
  • 134 Reply Likes
Dan and Patrick, Sorry for the Map Module flickering offline.

Can you provide more details, such as OS and version? Lightroom exact version?

Regards
Pete
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
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.
(Edited)
Photo of Roelof Moorlag

Roelof Moorlag

  • 113 Posts
  • 27 Reply Likes
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
(Edited)
Photo of David Clark

David Clark

  • 2 Posts
  • 3 Reply Likes
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.
Photo of Kees van Surksum

Kees van Surksum

  • 17 Posts
  • 11 Reply Likes
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 ...
Photo of George Nichols

George Nichols

  • 37 Posts
  • 15 Reply Likes
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? 
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
What has a map location software problem to do with a perfect image coming out of a camera?
Photo of Scott Burnette

Scott Burnette

  • 7 Posts
  • 2 Reply Likes
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?
(Edited)
Photo of George Nichols

George Nichols

  • 37 Posts
  • 15 Reply Likes
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. 
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
Good that we have people like you that understand the system...
Photo of George Nichols

George Nichols

  • 37 Posts
  • 15 Reply Likes
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. 
Photo of Dave Rye

Dave Rye

  • 2 Posts
  • 0 Reply Likes

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
(Edited)
Photo of Ridgecrest Photo

Ridgecrest Photo

  • 8 Posts
  • 0 Reply Likes
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
Photo of garin

garin

  • 1 Post
  • 0 Reply Likes
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
Photo of Kees van Surksum

Kees van Surksum

  • 17 Posts
  • 11 Reply Likes
@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.
(Edited)
Photo of Iain Burke

Iain Burke

  • 2 Posts
  • 2 Reply Likes
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.
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
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.
(Edited)
Photo of Yves Vandermeer

Yves Vandermeer

  • 2 Posts
  • 1 Reply Like
Same issue on Sierra 12.5 .. map flash for a second, no way to zoom very close and this message flashing with grey world map
Photo of Alan Harper

Alan Harper

  • 426 Posts
  • 84 Reply Likes
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

LR hasn't crashed yet (as others have reported).

Let me know if I can help track this down.
Photo of chris laurens

chris laurens

  • 1 Post
  • 1 Reply Like
I have the same configuration and same problem (and indeed very annoying)
Photo of Paul Gibson

Paul Gibson

  • 9 Posts
  • 1 Reply Like
Been happening to me for about 3 days now.

Mac OS 10.12.5.  Lightroom - most recent version, whatever number it is.
Photo of Steve Chasey

Steve Chasey

  • 19 Posts
  • 6 Reply Likes
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.
Photo of Paul Gibson

Paul Gibson

  • 9 Posts
  • 1 Reply Like
I've tried completely reinstalling LR (letting it trash preferences).  Doesn't solve the problem.  So I don't think it's a cache related issue.
Photo of Chris Parry

Chris Parry

  • 3 Posts
  • 3 Reply Likes
I get the same. 

Windows 10 64 Bit
Lightroom 2015.10.1

Tried restarting PC and still happens.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1074 Posts
  • 347 Reply Likes
Same issue with Windows 7, LR 2015.10.1
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
It must be a Google server problem. Any idea how to tackle this?
Photo of andre naus

andre naus

  • 3 Posts
  • 2 Reply Likes
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.
Photo of John Rangtveit

John Rangtveit

  • 4 Posts
  • 0 Reply Likes
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.
Photo of John Rangtveit

John Rangtveit

  • 4 Posts
  • 0 Reply Likes
Problem solved with tonights Lightroom update (July 19. 2017)
THANKS!
Photo of Wouter van de Weerd

Wouter van de Weerd

  • 1 Post
  • 0 Reply Likes
Same problem here, very annoying!

Windows 10
Lightroom CC 2015.10.1
Internet connection via ethernet cable (not wifi)
Photo of Mark den Hartog

Mark den Hartog

  • 42 Posts
  • 1 Reply Like
same here! how do we go back to previous version?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4261 Posts
  • 1544 Reply Likes
Photo of Mark den Hartog

Mark den Hartog

  • 42 Posts
  • 1 Reply Like
Thanks Victoria!
Photo of Søren Langkilde Madsen

Søren Langkilde Madsen

  • 34 Posts
  • 9 Reply Likes

Doing a roolback, just gets you back to older bugs. Moving forward is the only way.

This many customers now bleeding money to Adobe every month - should be possible to do a bit of testing and fixing problems as they are discovvered.


Photo of michal.cizek

michal.cizek

  • 3 Posts
  • 1 Reply Like
same problem here, win10, CC2015.10.1
Photo of Mick McKean

Mick McKean

  • 1 Post
  • 0 Reply Likes
Same problem here.
Windows 10 Pro x64
LR CC2015.9
Internet connection ADSL2+ Ethernet connected (not WiFi)
Photo of McLion

McLion

  • 24 Posts
  • 5 Reply Likes
Same here: W10 x64, CC 2015.10.1
Photo of Bruce Bracken

Bruce Bracken

  • 2 Posts
  • 0 Reply Likes
Same as everyone else apparently, Win 10 LR CC, all fully updated. LR CC 2015.10.1

Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
Alright guys and gals. Enough of the postings about the map offline error flashing. We have all learned that this has NOTHING To do what computer system one is on or what LR version is installed either . It pertains to all kinds of configurations. HOW ARE WE PROCEEDING FROM HERE ON? Can we push Adobe to get its bacon moved and give us an explanation of what to do about this or at least can we have a statement that they recognize the problem and working on it? This can NOT go uncommented on their behalf any longer. Any ideas? Thanks 
Photo of Gwen Gelting LaPlante

Gwen Gelting LaPlante

  • 1 Post
  • 0 Reply Likes
I also noticed also that when backing up catalog, in the optimizing step the white box flickers and turns black before closing. Both issues just started yesterday!
 
Photo of Robert Frost

Robert Frost

  • 394 Posts
  • 53 Reply Likes

I can also confirm this blackout and 'map offline' dialog is occurring everytime I move the map. Win10 and LRCC latest. Never happened before.


Bob Frost

Photo of Melanie Alvarez

Melanie Alvarez

  • 1 Post
  • 0 Reply Likes
Same problem here. It is annoying and I can't work with the map module.
I am running Mac OS Sierra 10.12.5 and Lightroom CC 10.6.1.
Seeing that many different OS version have this problem, it does not seem that it is a computer issue but more likely an LR or even a google map issue.
Photo of Hans Verleysen

Hans Verleysen

  • 13 Posts
  • 0 Reply Likes
Same problem here... Mac OS 10.12.5; Lightroom CC 2015.10.1
Photo of nick normal

nick normal

  • 1 Post
  • 1 Reply Like
Here is video of the behavior (tip: it's annoying):
https://drive.google.com/file/d/0B4fNTUYL6CmdUnZlRDRTei1zblE/view?usp=sharing

Addendum: dragging a photo onto the map, it takes the software around 12-15 seconds to 'locate' the GPS and append the 'geotag' icon to the image in Lightroom; I have 200+ images to geotag in my current session, so that's ~50 minutes of waiting for the item to be geotagged (15 secs * 200 images = 3000 seconds). Unbelievable.
(Edited)
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
Adobe where are you hiding. We need relief - SOON !!!!
Photo of McLion

McLion

  • 24 Posts
  • 5 Reply Likes
Probably enjoying the weekend ... like most of us too ;-)
Wait for Monday morning US time. I have filed a bug with Adobe.
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
Thanks for filing my friend. Adobe has officially responded in the meantime as you might have read and is looking into it. I just hope they look hard, deep and fast and also catch the NEW bugs that were introduced into LR with CC 2015 6.10.1 and forced me to downgrade to 6.10.0
(Edited)
Photo of Steve Chasey

Steve Chasey

  • 19 Posts
  • 6 Reply Likes
Issue found in 6.9 as well (and poss also 6.8)  - reported on the LR Forum by me with no solution offered, other than restarting LR which does work (in 6.9 at least).  So it's not just a 6.10.1 issue alone, the underlying problem been there for some of us for a lot longer
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4261 Posts
  • 1544 Reply Likes
It's looking like it's possibly a server-side change at Google Steve, because it's affecting much older LR versions (e.g LR5) over the last few days too, and we'd have been sure to notice it for THAT long!
Photo of Steve Chasey

Steve Chasey

  • 19 Posts
  • 6 Reply Likes
Maybe part of the explanation why the number of users reporting the issue has escalated and that it's not just the latest iterations affected. However, it's been there for a while in the background.
Photo of Norbert Pauli

Norbert Pauli

  • 12 Posts
  • 12 Reply Likes
What are you talking about? The problem just started about six days ago. Everything was fine before !
Photo of Steve Chasey

Steve Chasey

  • 19 Posts
  • 6 Reply Likes
Norbert - I raised this on the Lightroom Forum last October.  It clears for me if I reload LR.  So it has some potential to be cache related as well as being a long standing bug that the recent changes to Google's servers has brought out.
Photo of Bruce Houstoun

Bruce Houstoun

  • 61 Posts
  • 14 Reply Likes
Google was changing their web certificate authority for Google Cloud Services starting June 12 so that may have something to do with this? Timing is about right.
https://gsuiteupdates.googleblog.com/2017/06/google-cloud-services-are-switching.html

-bh
Photo of Paul Gibson

Paul Gibson

  • 9 Posts
  • 1 Reply Like
My tweet to Adobe 2 days ago has been left unanswered.  Not even an acknowledgement of said tweet.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4261 Posts
  • 1544 Reply Likes
They've acknowledged it as a problem here Paul (although I can't answer for why the social team didn't respond).
(Edited)
Photo of Paul Gibson

Paul Gibson

  • 9 Posts
  • 1 Reply Like
Ah... I missed that response.  (Their social team did respond just a little while ago saying this thread would have the most up-to-date info).
Photo of Ilya Belevich

Ilya Belevich

  • 1 Post
  • 0 Reply Likes
Exactly the same problem, extremely annoying!
Photo of August Linnman

August Linnman

  • 1 Post
  • 0 Reply Likes
Same problem here. Running Lightroom CC 2015.10.1
Windows 10 Home. 
Photo of Gavin Dodds

Gavin Dodds

  • 1 Post
  • 1 Reply Like
Same problem for me. Makes using the maps useless