[View this post in your web browser. It contains formatting and images that don't appear in email.]
@hans_onepicture Whether the map display works or not could depend on the username (user) in the Windows account. My Windows username contains an umlaut ("ü").
Excellent discovery! I tested 8 diacritical marks and 1 ligature in Windows account usernames, and some worked and some didn’t. This explains why the bug reports mostly came from the same European countries, with a few from South America and other countries.
So the workaround is to create a username without any diacritical marks.
Looking at the Unicode representations, all of the problem-causing diacritical marks have code points starting with U+00, while the non-problematic marks and ligatures don’t:
It’s pretty clear that some software component invoked by the Map module has a bug in its handling of Unicode strings. Given that similar bugs haven’t cropped up in other parts of LR, this strongly suggests the problem is somewhere in the third-party components such as the Google Maps JSON library. I think that library caches map data in hidden folders inside C:\Users\<username>\AppData, and the caching could be getting tripped up by the bug in the Unicode handling.
As of some months ago, Adobe hadn’t updated that component -- it was many years out-of-date. And the engineer who originally wrote that part of LR is likely long gone from the team.
Tested on LR 16.0 / Windows 11 running in the US region with US English.
Bonjour Joachim, comme indiqué plus haut, crée sur ton ordinateur une nouvelle session avec un nouveau compte dans Windows 10 ou 11 et tu retrouveras toutes le fonctionnalitées de Lighroom Classic même dans sa dernière version. Bien sûr Adobe aurait dû résoudre ce problème rencontré par certaines sessions de Windows, mais rien ne vaut le sytème D. Pour créer une nouvelle session avec un nouveau compte, recherche sur le net si tu ne sais pas faire. ! Tiens nous au courant de ton résultat ça aidera tout le monde.
Je le même problème. Ce n'est pas seulement un problème du module carte, c'est un problème de l'acess au adobe servers. La synchronisation avec Lihtroom mobel ne fonctionne pas non plus
Bonjour Raph-Oh, effectivement en passant par un autre utilisateur, le module carte semble fonctionner. Je suis sur la version LRC 14.5.1. Adobe met du temps à nous aider. Depuis 6 mois, je suis en difficulté alors que cela marche sur un portable.
Bonjour Ralf-Oh, merci pour cette solution qui fonctionne également parfaitement pour moi, même la recherche avec le nom des lieux fonctionne alors que dans la version 14.1.1 elle ne fonctionne pas. Dorénavant ce compte sera dédié exclusivement au travail sur Lightroom classic et évitera l'installation et la désinstallation des différentes versions. Il serait tout de même temps qu'Adobe résolve ce problème mais cela semble insurmontable !?
@Ralf_Oh�, thanks for the additional information. There must be some setting or cached file specific to the original Microsoft user that got left behind when you moved to the new local user, though you tried deleting the most obvious ones (preferences and LR's cached files).
But it's good you've found a (painful) workaround -- that could help others.
I doubt that Adobe will prioritize this bug -- there are lots of other Map bugs outstanding.
Hi John, thank you for your reply and your questions. Please see my answers below.
1) Yes I could open my existing catalog. Everything works as with my original user. Since it is located below "c:\users\public\" there are also no problems with access rights. 2) My original user is a "Microsoft user". 3) No, it's not synced with OneDrive. 4) I executed the steps, but the map module still does not work with my original user. With the new user it is working.
@Ralf_Oh�: "I created a new local user on Windows 11 and opened my existing catalog. This allowed the map module to work under version 14.5.1. Unfortunately, it still doesn't work with my default user."
Excellent.
There is all sorts of per-user data squirrelled away by LR, and creating a new user effectively resets all that per-user data. To help others and perhaps spur Adobe to track this down (we can always hope), it would be good if you could provide some more information:
1. Were you able to open your existing catalog from the new user, or did you have to create a new catalog?
2. Was the original user a "Microsoft" user that simultaneously signs you in to all the Microsoft services? Microsoft pushes you into creating such a user when you first initialize your computer (I don't know the precise terminology.)
3. Was the catalog path you published above being synced by One Drive?
C:\Users\Public\Lightroom\Lightroom Catalog\
Creating a new local user would have disabled any One Drive syncing. (Microsoft unwisely automatically enables One Drive syncing for "Microsoft" users but not local users.)
4. While logged in as the original user, do Edit > Preferences > General, hold down Alt, and click Reset All Preferences And Relaunch. In addition to resetting preferences, that will clear cached data, including all the Chromimum Embedded Framework (CEF) map data cached by the Map module. Does the map module now work?
I have found an other workaround. I created a new local user on Windows 11 and opened my existing catalog. This allowed the map module to work under version 14.5.1. Unfortunately, it still doesn't work with my default user.