Bug 178180 - Timezone forgotten using network time
Summary: Timezone forgotten using network time
Status: CLOSED DUPLICATE of bug 177815
Alias: None
Product: Fedora
Classification: Fedora
Component: ntp   
(Show other bugs)
Version: 5
Hardware: i686 Linux
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-01-18 11:04 UTC by Dag Bjerkeli
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-18 12:00:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Dag Bjerkeli 2006-01-18 11:04:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060103 Fedora/1.5-4 Firefox/1.5

Description of problem:
Selecting timezone in the gnome applet and having network time enabled does not
give me correct timezone.  Correct timezone for me is Europe/Oslo, but after
updating, timezone is back to America/New York.

Version-Release number of selected component (if applicable):
First installation of FC5 test 2

How reproducible:

Steps to Reproduce:
Steps are translated from norwegian installation, but should provide information to reproduce.

1. Rightclick om gnome time applet
2. Select Adjust date and time
3. Enable Network Time Protocol
4. Add server fartein.ifi.uio.no
5. Find Europe/Oslo under the timezone tab
6. hit OK

Actual Results:  After time is updated from server. timezone is back to America/New York

Expected Results:  Timezone should have been Europe/Oslo.

Additional info:

After some further investigation, it looks like its the applet that doesnt store the timezone indformation.

Comment 1 n0dalus 2006-01-18 12:00:55 UTC
This should be fixed in Rawhide now. See bug 177815 and bug 177779.

*** This bug has been marked as a duplicate of 177815 ***

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