Bug 115763 - Change timezone ends up with wrong location displayed
Summary: Change timezone ends up with wrong location displayed
Status: RESOLVED FIXED
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmclock (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Paul Campbell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-06 08:39 UTC by Odd Arild Olsen
Modified: 2010-04-07 10:39 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Odd Arild Olsen 2005-11-06 08:39:05 UTC 
Version:           from the 3.4 beta 2 (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

When I select Oslo Europe/NO the clock is correctly set, but the displayed local timezone below the table is set to Arctic/Longyearbyen.

When I mouse over the clock the correct name is displayed in the bubble.

If I open the timezone configurator again the selected timezone in the table is Longyearbyen.
Comment 1 Ralph Janke 2007-03-26 02:07:37 UTC 
I have the same behaviour with the default timezone being set to Europe/London, but kcmclock shows in the configuration Europe/Guernsey (BST). If I change to London, it stays the same. When I change it to Oslo it shows Arctic/Longyearbyen. When I change it back to London it shows Guernsey again.

Version 3.5.2 on Kubuntu Dapper and also on 3.5.6 on Feisty Beta.
Comment 2 James Kerr 2007-10-05 13:32:16 UTC 
This bug still exists in 3.5.7 (Mandriva 2008)
Comment 3 Odd Arild Olsen 2007-10-08 09:17:22 UTC 
Also still in Kubuntu Feisty Fawn kde ver 3.5.6
Comment 4 Ralph Janke 2008-03-21 01:33:40 UTC 
Also still on Kubuntu Gutsy KDE Version 3.5.8
Comment 5 Ralph Janke 2008-06-16 02:07:33 UTC 
This also occurs in KDE 4.0.4
Comment 6 info 2008-10-25 10:17:02 UTC 
Still in 4.1.2 on Fedora 9... quite annyoing.
Comment 7 info 2008-12-05 18:36:13 UTC 
Still in 4.1.3 in Fedora 10. Bug 159171 seems a duplicate of this one.
Comment 8 Jeffrey Lau 2009-01-17 22:28:57 UTC 
Still in 4.1.96 (4.2 RC1) in Fedora 10...
Comment 9 Harald Sitter 2010-04-07 00:14:49 UTC 
I suppose this does not occur anymore in >= 4.4?
Comment 10 Odd Arild Olsen 2010-04-07 08:28:18 UTC 
I do not see this problem now, KDE 4.3.2
Comment 11 Harald Sitter 2010-04-07 10:39:29 UTC 
Cool, thanks.