Bug 93308 - events in kontact/korganizer are randomly moving by -/+ x hours
Summary: events in kontact/korganizer are randomly moving by -/+ x hours
Status: RESOLVED DUPLICATE of bug 84229
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Reinhold Kainhofer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-15 12:55 UTC by Gilles Gagniard
Modified: 2005-07-24 16:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gilles Gagniard 2004-11-15 12:55:23 UTC
Version:            (using KDE KDE 3.3.1)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 3.4.2 20041025 (Gentoo Linux 3.4.2-r3, ssp-3.4.1-1, pie-8.7.6.5) 
OS:                Linux

Sometimes, when I open korganizer or kontact, all my events are shifted by +/- x hours (in facts it is always 2 for me, but if it is a time zone related problem, it may be another value for you ...). In facts, it looks very similar to bug #84229, but the fun part is that it is not easily reproducible, it is not every time I open the app but it occurs randomly (in facts it occured 4 times in 2 months and I use korganizer on a daily basis, and the last time was 10 minutes ago). Of course, my timezone doesn't change, it was and it is still GMT, and in the configuration of korganizer, the exact same timezone is selected.
Comment 1 Reinhold Kainhofer 2005-02-13 19:42:54 UTC
Do you have your computer's BIOS clock set to UTC or to local time?

Cheers,
Reinhold
Comment 2 Matija Šuklje 2005-03-22 07:08:18 UTC
I can confirm this behavour!

I'm also running Gentoo, am in GMT, and this has been happening to me in random occasions for quite some time - so it's not been fixed in 3.3.2 (if it's a KDE problem). And always for +/- 2 hours.

You can imagine how very annoying and frustrating this is!

p.s. My BIOS is AFAIK ok, btw and the clock was set to local, last time I checked.
Comment 3 Reinhold Kainhofer 2005-07-24 16:01:17 UTC
Thanks for the bug report!

It's the same time zone problem as in 84229. However, I haven't been able to reproduce that one ever :-((

Cheers,
Reinhold

*** This bug has been marked as a duplicate of 84229 ***