Bug 191733 - Times are -3 hour earlier => timezone
Summary: Times are -3 hour earlier => timezone
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konsolekalendar
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Allen Winter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-05 20:52 UTC by Ilpo Kantonen
Modified: 2018-02-01 09:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilpo Kantonen 2009-05-05 20:52:02 UTC
Version:           konsolekalendar (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

I installed konsolekalendar to my Kubuntu Jaunty since Korganizer doesn't display day or week displays (month display ok). First, when I installed konsolekalendar and started it, it caused segmentation fault. Then I opened another window to konsole and then again konsolekalendar. It worked ok.

Then I found this day events. But the time was -3 hour earlier than in Korganizers calendar. -3h is just difference finnish summer time and GMT. The Konsolekalendar handbook said that no configuration is needed. So, I think that this is bug. In Kubuntu konsole date-command brings correct time.
Comment 1 Paul Thomas 2010-12-20 00:12:04 UTC
I'm also seeing this on KDE 4.5.1, kubuntu's default packages: konsolekalendar reports some (not all) events as if they were in UTC.  Korganizer reports (correctly) that they're all Australia/Sydney, and they appear correctly in the various graphical views.
Comment 2 Denis Kurz 2017-06-23 19:58:55 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:54:18 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.