need to delete and re-enter locations after forecast menu item crash fix

Bug #748854 reported by Felix Lawrence
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Weather Indicator
Won't Fix

Bug Description

While bug #739420 (et al.) has been fixed, the problem occurred when locations were created. So the fix for #739420 won't help people who created their locations before the bug was fixed, unless they delete their locations and re-enter them. We need to do either:
1) Somehow automatically update only the affected locations, and ideally only run this once per computer, or
2) Catch the exception and instead of crashing, either update the affected locations or tell the user to delete and re-enter the location.

We should also explicitly check that Google doesn't return empty weather info.

Revision history for this message
Vadim Rutkovsky (roignac) wrote :

I don't think we should add the code, which will convert incorrect locations - as it would result in unnecessary server requests and parts of code, which will be not safe to remove.
Second option would better - a simple message box on Preferences dialog would be enough

Changed in weather-indicator:
importance: Undecided → Low
milestone: none → foggy
status: New → Confirmed
Changed in weather-indicator:
milestone: foggy → cloudy-4
Changed in weather-indicator:
milestone: cloudy-4 → foggy
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

As foggy version now uses dconf to store settings, I don't think we should migrate user data (due to the bug with incorrectly stored coordinates) - this will cause way too much desktopcouch dependencies

Changed in weather-indicator:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.