Comment 7 for bug 387738

That is good information to know. When is it apparent that something is wrong. Is the marker in the wrong place when you set the location, or after you save, you see that the mark has moved to the bad location?

Taking a look at the page source for three affected users I see:
    52.6332408717, 52.6333363734
    50.9198996102, 50.9197553212
    41.5305129031, 41.3850519497

Those are very surprising numbers, and they are in the database. Since geonames returned the right timezone, the correct lat-long pair was sent to geonames. The function that does that also stores that pair in the form that is submitted to launchpad.

So the error looks like it occurs between the moment the the location is set in the page and when it is stored in Launchpad. This is not as helpful as it would seem, because nothing in the script or the widget in Launchpad ever directly changes the lat-long. I say directly because these values are floats and there could be conversion issues moving the values from javascript number -> form string -> Python float.

I think the key to this issue is that the numbers are so similar. It looks like the lat is being used as the long. The numbers differ because of possible float conversions, lat and long do have different ranges, -90..90 and -180..180 respectively.

I am still very perplexed. I cannot reproduce the problem.