Summary: | Gnome-panel clock shows evolution event for the day after it occers as well | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Surakshan Mendis <bug.tracker> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Surakshan Mendis
2004-12-08 01:10:45 UTC
upgraded to Gnome 2.8.2 same issue, happens as other users as well Screnshots to show the problem. I think this is a major issue because it can mislead users! I only caught it after it claimed christmas day was on the 26th as well http://forums.gentoo.org/viewtopic.php?p=1866323#1866323 2.8.2 isn't in portage, I've only *just* added gnome-applets-2.8.2 to portage, can you upgrade and test that please. My bad, I have 2.8.1-r1 of gnome-base/gnome upgraded to 2.8.2 gnome-applets. logged out, made sure no processes were running, started gnome, problem occers. Do you think its the clock applet or EDS sending out bad data? I thinking (from a non technical thought) that it's the applet (or not EDS) since the applet's date is not bold if there are no events in evolution, yet shows events from the previous day anyway if there was data for the previous day in evolution. I have found the problem and the soluton. Allow me to define the trigger more clearly since I have found more information. This issue only affects ALL DAY Apointments in evolution. The problem was (and I still think its a bug) if I enter an all day appoint for eg 14 feb, then it displays correctly in evolution. However in the gnome panel clock it would claim the appoint is also on the 15th of feb (note that the 15 won't be in bold, but clicking on 15 clearly shows 14th's appointment). So we can see how this can play with your daily tasks. Trigger? I was in Perth Australia UTC 8+, then I moved to Sydney Australia which is +10 (although we are in Day light savings these days). Whilst I changed the time zone in the system, it was still Perth in Evolution. This it seems causes the above "problem". changing the timezone in evolution to match the system zone fixed the problem... This also explains why its not reproducable for most people I hope you find this information useful. |