Summary: | Wrong timezone for events shown in clock and calendar plasma widgets | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Kubicle <kde.bugs> |
Component: | widget-clock | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | daniel, david.narvaez, kde.dev, kde, masterdany88, maystar, sander79 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.7.4 | |
Sentry Crash Report: |
Description
Kubicle
2011-08-05 09:06:45 UTC
Just in case it makes a difference, the events are stored on an imap server, and fetched via the akonadi kolab resource. I can confirm this bug in kde 4.7.1. An event with these start information in its *.ics file DTSTART:20110913T081500Z is in Germany shown at 8:15 in the clock widget. In contrast Korganizer shows this event at 10:15. One more confirmation. The following event: DTSTART:20111004T133000Z DTEND:20111004T143000Z is shown at 13:30-14:30 (CEST, UTC/GMT+2) in the digital clock widget. Korganizer shows the event at the correct time, 15:30-16:30 CEST. Btw, my events are stored in an Akonadi Calendar resource, backed by an .ics file. This is width Akonadi 1.6.1 + KDE 4.7.1. I can confirm this bug. Events are correct everywhere except for the plasma widget where instead of GMT+0530 they are at GMT/UTC. Seems to be a bug in the widget itself. I can confirm this bug and will be working on it. Git commit 959c60f47222c241419bfc4837e57005813a798f by David E. Narváez. Committed on 10/11/2011 at 22:00. Pushed by narvaez into branch 'master'. Adjust TimeSpecs in the Calendar Dataengine to Reflect Local Time Adjust events start and end dates to local time at the Dataengine. BUG: 279427 FIXED-IN: 4.7.4 REVIEW: 103104 M +10 -10 plasma/generic/dataengines/calendar/eventdatacontainer.cpp http://commits.kde.org/kde-workspace/959c60f47222c241419bfc4837e57005813a798f *** Bug 286480 has been marked as a duplicate of this bug. *** *** Bug 283803 has been marked as a duplicate of this bug. *** *** Bug 278508 has been marked as a duplicate of this bug. *** |