Bug 720043 - Clock/Weather Location Incorrect Default
Summary: Clock/Weather Location Incorrect Default
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-applets
Version: 6.1
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-08 20:10 UTC by Andrew Case
Modified: 2018-11-14 11:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 20:12:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Andrew Case 2011-07-08 20:10:22 UTC 
System location is set to New York, NY during install but the clock-weather applet location defaults to Boston.

Wasn't sure if this should be filed under libgweather or gnome-applets.
Comment 2 RHEL Program Management 2011-07-08 20:38:26 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 Andrew Case 2011-07-08 21:28:55 UTC 
Thanks.  I'll do that.  In the interim, do you know if there a way to configure the default clock-weather location system-wide so all my users aren't confused why they get weather from Boston?
Comment 9 Jeremy West 2012-06-25 20:12:05 UTC 
Andrew,

I see that your support case has now been closed/resolved and so I'm going to close this bug report out as well.  If you have any questions or concerns with this, please contact our support team.

Thanks
Note You need to log in before you can comment on or make changes to this bug.