"Location" auto-complete menu doesn't understand "london"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Indicator Date and Time |
Fix Released
|
Undecided
|
Unassigned | |
| | indicator-datetime (Ubuntu) |
Undecided
|
Michael Terry | ||
Bug Description
Binary package hint: indicator-datetime
indicator-datetime 0.1.98-0ubuntu1, Ubuntu Natty
0. Make sure you aren't connected to the Internet
1. From the clock menu, choose "Time & Date Settings..."
2. Click "Unlock to change these settings".
3. In the "Location" field, enter "london".
What happens: A hundred or so options appear, none of which are "London" or even have the string "London" in them.
What should happen: London UK, London Ontario, and any other places called London appear.
Related branches
- Indicator Applet Developers: Pending requested 2011-03-23
-
Diff: 53 lines (+14/-9)1 file modifiedsrc/timezone-completion.c (+14/-9)
- Ken VanDine: Pending requested 2011-10-13
-
Diff: 301 lines (+59/-27) (has conflicts)8 files modifiedChangeLog (+32/-0)
configure (+10/-19)
configure.ac (+1/-2)
data/datetime-dialog.ui (+0/-1)
debian/changelog (+14/-0)
debian/control (+0/-2)
src/datetime-prefs.c (+0/-1)
src/datetime-service.c (+2/-2)
| Changed in indicator-datetime (Ubuntu): | |
| assignee: | nobody → Michael Terry (mterry) |
| description: | updated |
| Michael Terry (mterry) wrote : | #1 |
| Michael Terry (mterry) wrote : | #2 |
Nope, London is in the default database. Yay! branch filed
| Changed in indicator-datetime: | |
| status: | New → Fix Committed |
| Changed in indicator-datetime: | |
| milestone: | none → 0.2.0 |
| Changed in indicator-datetime: | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote : | #3 |
This bug was fixed in the package indicator-datetime - 0.2.0-0ubuntu1
---------------
indicator-datetime (0.2.0-0ubuntu1) natty; urgency=low
* New upstream release.
∘ Remove unused liboobs
∘ Add translator comments and make strings translatable (LP: #737326)
∘ Remove password dialog for calendars not the keyring
∘ Use default matching when geonames aren't available (LP: #740870)
∘ UI Cleanups and naming fixes (LP: #740806, LP: #740819)
∘ Free JSON parser data
∘ Avoid duplicates in GeoNames data (LP: #740884)
∘ Make location completion more robust
* debian/control: Dropping liboobs
-- Ted Gould <email address hidden> Wed, 23 Mar 2011 16:22:50 -0500
| Changed in indicator-datetime (Ubuntu): | |
| status: | New → Fix Released |
So I can only see this bug when I'm not connected to the Internet (and I added that to the reproduction steps above). If you are sure you saw this when connected, perhaps there are two bugs here. But working on the non-connected bug, obviously, you wouldn't expect lots of London results. We'll match the tiny database we ship with, but it may not have London (I think it doesn't, in fact).