Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 100468 - kworldclock doesn't display local times
kworldclock doesn't display local times
Status: CLOSED UPSTREAM
Product: Red Hat Linux
Classification: Retired
Component: kdetoys (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2003-07-22 15:06 EDT by Stephen Rasku
Modified: 2007-04-18 12:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-12 09:56:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Stephen Rasku 2003-07-22 15:06:46 EDT 
Description of problem:

When I select a city in kworldclock, it displays the same time for every city. 
The time it displays isn't the local time or GMT.  For example, now it is
displaying 10:02 pm.  It is currently 12:02 pm local time and 7:02 pm GMT.  This
used to work with kdetoys-3.0.5a-0.73.0.

Version-Release number of selected component (if applicable):

kdetoys-3.1-3

How reproducible:

100%

Steps to Reproduce:
1. Start kworldclock
2. Move cursor over various cities
    
Actual results:

The same time from an unknown timezone is displayed for every city.

Expected results:

The local time of the city should be displayed.
Additional info:
Comment 1 Ngo Than 2003-08-12 09:56:44 EDT 
it's fixed in kde-3.1.2 or newer, which is available for RHL 9 on ftp.kde.org
Comment 2 Ricky Ng-Adam 2003-11-04 04:19:12 EST 
Isn't this a dup of bug #88143 (which is at status assigned?)
Comment 3 Stephen Rasku 2003-11-04 18:39:13 EST 
Almost.  However, the time that was displayed for me was neither local
nor GMT.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.