Version: 0 (using KDE Continue) Compiler: kcontrol/kcmclock OS: .....X..... If I change my timezone using kcmclock, the current time is adjusted to reflect that - e.g. moving from "UTC" to "Europe/London" adds one hour because London is currently on British Summer Time (GMT+1). I can see the logic behind this: if you change the timezone, you haven't changed the time. So the system time (presumably set as UTC) stays the same, and the displayed time adds the timezone to it. The problem is that people will tend to do as follows: * open the kcmclock dialog * set the time to their current time * set the timezone - oh wait, now it's changed my time and I have to alter it again! So I suggest that kcmclock should accept the time entered as the time that should get displayed on the clock, and set the "system clock" to take account of the timezone offset.
and if we did this we would equally we have the situation: * open the kcmclock dialog * set the timezone and click save (from a tab where you can't even see the clock) the clock would changes, and you set the time to the wrong thing Given this is the correct workflow, as opposed to yours where you have the user compensating for the wrong timezone twice, I'm going to close this.