[Bug 370758] Re: unable to edit location name in clock

2010-09-15 Thread Bug Watch Updater
** Changed in: gnome-panel Status: New = Fix Released ** Changed in: gnome-panel Importance: Unknown = Wishlist -- unable to edit location name in clock https://bugs.launchpad.net/bugs/370758 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 370758] Re: unable to edit location name in clock

2010-01-14 Thread Pedro Villavicencio
This has been fixed upstream now, thanks for reporting. ** Changed in: gnome-panel (Ubuntu) Status: Triaged = Fix Committed -- unable to edit location name in clock https://bugs.launchpad.net/bugs/370758 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 370758] Re: unable to edit location name in clock

2010-01-14 Thread Sebastien Bacher
The bug has been fixed in karmic and lucid ** Changed in: gnome-panel (Ubuntu) Status: Fix Committed = Fix Released -- unable to edit location name in clock https://bugs.launchpad.net/bugs/370758 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 370758] Re: unable to edit location name in clock

2009-10-31 Thread Daniel Castro
The workaround I posted before still needs to be applied to 9.10. With a small difference: The string changed a bit, now it comes in the form of: Before: location name= city=Shannon timezone=Europe/Dublin latitude=52.71 longitude=-8.916667 code=EINN current=true/ After: location name=Galway

[Bug 370758] Re: unable to edit location name in clock

2009-07-22 Thread Daniel Castro
Here is a workaround. ~$ gconf-editor Go to: /apps/panel/applets/clock_screen0/prefs/cities and edit the key. On the 'Edit Key' window you will see values for your cities, select the one you want to change and click 'Edit'. Here is a before and after example of my string. Before: location

[Bug 370758] Re: unable to edit location name in clock

2009-07-22 Thread Pedro Villavicencio
I've sent this upstream at: http://bugzilla.gnome.org/show_bug.cgi?id=589422 ** Bug watch added: GNOME Bug Tracker #589422 http://bugzilla.gnome.org/show_bug.cgi?id=589422 ** Also affects: gnome-panel via http://bugzilla.gnome.org/show_bug.cgi?id=589422 Importance: Unknown

[Bug 370758] Re: unable to edit location name in clock

2009-07-22 Thread Bug Watch Updater
** Changed in: gnome-panel Status: Unknown = New -- unable to edit location name in clock https://bugs.launchpad.net/bugs/370758 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 370758] Re: unable to edit location name in clock

2009-07-22 Thread Simon
Ahh, a simple workaround, thanks Daniel! (and thanks too to Pedro for upstreaming this) -- unable to edit location name in clock https://bugs.launchpad.net/bugs/370758 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 370758] Re: unable to edit location name in clock

2009-07-20 Thread Daniel Castro
So this is a bug right? Regression. Or was this feature purposely removed by the developers? -- unable to edit location name in clock https://bugs.launchpad.net/bugs/370758 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 370758] Re: unable to edit location name in clock

2009-06-11 Thread Sebastien Bacher
the bug seems rather a feature request to display an another name that the weather station one, should be sent to the software writters on bugzilla.gnome.org since the ubuntu team will not work on this change in an ubuntu specific way ** Changed in: gnome-panel (Ubuntu) Importance: Low =

[Bug 370758] Re: unable to edit location name in clock

2009-05-02 Thread Simon
Hmm. On reflection, the workaround I described does work, cumbersome though it is, but it seems I can't get weather information for this location now. I guess the lat. and long. values aren't sufficient for it to work out that it's the same place. This is only a small bug, but I do think it