(*** This bug was imported into bugs.kde.org ***) Package: kicker Severity: normal Version: 1.1 OS: Linux (i686) release 2.4.18 Compiler: gcc version 2.95.2 19991024 (release) KDE: 3.0.5 CVS HEAD from 2002-06-04 (compiled sources) Qt: 3.0.4 CVS HEAD from 2002-05-03 (compiled sources) After changes around 2002-05-10 multiple clock applets with different timezones don't work any more. Try this: - start kicker with one clock applet - add second clock applet: now you can select the timezone on each as expected using the middle mouse button; - leave the second clock with a different timezone - restart kicker: dcop kicker "" restart = first bug: both clock applets start with the same local time! Mind that people only have two or more clock applets because they need the New York time alongside with their local time (read: stock market etc.) Requiring the user to set up timezones after every restart is not acceptable. - now change the timezone in one of the clocks (MMB) = second bug: the timezone changes in =all= clocks! (The label "New York" etc. however remain the same.) Tested with a KDE-clean account. m.
I can confirm this on my PC. This is what I did: I have my normal local time clock I added a new applet 'Clock'. Changed the timezone to Australia/Melbourne, it labeled (correctly) the new clock as 'Melbourne'. But then my local clock changed to the same time as the melbourne clock! (Yet it didn't change its label). Then I went to the local clock, it had 'local timezone' still selected, but I clicked it again, and then both clocks changed to local timezone. I couldn't get them to be different. David
Oh, aditional comment: this happens with kde 3.1beta2 from gentoo packages.
Same here with RPMs 3.1beta2 on SuSE 8.1. Lost Timezone or correct timezone is shown but with the local time. When switch the clock-type it happens too.
Subject: Fwd: kdebase/kicker/applets/clock Fix various kpanelclock problems as discussed on kde-core-devel, like incorrect time, timezone problems, time zones on multiple clocks not reset at startup, multihead-problems, ... Patch tested by Melchior FRANZ and Lauri Watts. CCMAIL: 30869-done@bugs.kde.org CCMAIL: 32912-done@bugs.kde.org CCMAIL: 42702-done@bugs.kde.org CCMAIL: 43586-done@bugs.kde.org M +30 -16 clock.cpp 1.98 M +4 -1 clock.h 1.32 M +17 -10 settings.cpp 1.7 M +2 -3 settings.h 1.3
I have a mandrake KDE 3.1.0 version and I have the same problem. Is it now fixed on current KDE versions ? Which version I must download to have this function (different timezone not reminded at kicker restart) ?
> Is it now fixed on current KDE versions ? If the bug report says "RESOLVED" and "FIXED" and the bug report is closed, what do you think this wants to tell us, other than the bug is fixed? :-} Since when? Since around 2002-11-07 21:00 or KDE 3.0.1. m.
> Since when? Since around 2002-11-07 21:00 or KDE 3.0.1. So : fixed in 3.0.2 and later ? Why have I this bug in 3.1.0 (doesn't remember timezone) ?
I still experience the first bug (the timezone of the second clock is not remembered) in KDE 3.2.2, and it didn't work in 3.1.x either (Debian Testing/Unstable). It's certainly not a critical bug, but still slightly annoying...