982 – KDE Kicker clock displays wrong timezone entry

Bug 982 - KDE Kicker clock displays wrong timezone entry

Summary: KDE Kicker clock displays wrong timezone entry

Status:	RESOLVED OLD

Alias:	None

Product:	Mageia
Classification:	Unclassified
Component:	RPM Packages (show other bugs)
Version:	Cauldron
Hardware:	i586 Linux

Priority:	Normal Severity: normal
Target Milestone:	---
Assignee:	Mageia Bug Squad
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-04-25 14:21 CEST by DariuszSki
Modified:	2011-10-09 22:34 CEST (History)
CC List:	1 user (show)

See Also:
Source RPM:	kdebase4-workspace
CVE:
Status comment:

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

Description DariuszSki 2011-04-25 14:21:11 CEST

Description of problem:
Mandriva 2010.1 to Mageia Beta1 install.

If in MCC / "Manage Date and Time" you have your location set to "Europe/London", you cannot get rid of the local timezone being called "Belfast" (hovering over timezones displayed in Kicker), Belfast is in another country and hundreds of miles away, it is NOT local!!!!

Please correct the timezone entry so that if a user has selected Europe/London, the "local" time is London, not Belfast! Belfast can be selected separately.

No such problem existed in Mandriva 2010.1.


Version-Release number of selected component (if applicable):
Beta1 install of Mageia.


How reproducible:
Install Mageia Beta1 over Mandriva 2010.1

Comment 1 Ahmad Samir 2011-05-10 23:52:49 CEST

Using drakclock (drakconf .... -> "Manage Date and Time", doesn't affect the KDE clock widget settings (I've just tested in a newly created user account).

Assignee: bugsquad => balcaen.john
Source RPM: (none) => kdebase4-workspace

Ahmad Samir 2011-05-10 23:52:55 CEST

Component: Installer => RPM Packages
Assignee: balcaen.john => bugsquad

Comment 2 José Jorge 2011-10-09 22:34:26 CEST

This bug is old, and changes in Cauldron were huge. Please re-open it if it is still there.

Status: NEW => RESOLVED
CC: (none) => lists.jjorge
Resolution: (none) => OLD

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