Version: 3.5.2 (using KDE KDE 3.5.2) Installed from: Ubuntu Packages OS: Linux My event are all 5 hours incorrect, which is the current difference between my timezone and GMT. After a recent reboot my KOrganizer has not been working properly. Sometime in the past Ubuntu did a small security patch kdelibs-bin, kdelibs-data, kdelibs4c2a (from 4:3.5.2-0ubuntu18.1 to 4:3.5.2-0ubuntu18.2) but that doesn't for sure mean the cause of my issue. I did have to import my calendars into my program, but the bug report on that doesn't match my experience. I tried to 'trick' the program into moving the events by changing my timezone and checking keep times / move times. Interestingly this did not move my events at all. When I view the calendar on another computer or through Google the events are at the correct time so it appear the .ics file is correct, but my view in KOrganizer is wrong. I've looked at the other settings for date/time in my .kde directory and they all have America/Toronto which is correct. It's also set to that in /etc/localtime If I create a new event (not importing now) and then look at it from another program, the time is 5 hours off. Is there some setting somewhere that might be messing things up? Thanks!
Under Configure , look at the Time&Date page. Do you see your Timezone set in there as America/Toronto? PS. you really should consider upgrading to a more modern KDE version :)
Yes, my timezone under Configure KOrg->Time&Date is America / Toronto. I am running Ubuntu 6.06 Long Term Support and that is the newest version in the repository. I would like to be newer, but would have to upgrade my whole system, and I'm not ready to do that. Sorry!
I am seeing the same thing with KDE-3.5.6, Kontact-1.2.4 on Fedora Core 6. I am on Easter Time (GMT-5:00). Events that I imported from Google Calendar are shifted +5 hours. Event that I exported from KDE and imported to Google Calendar are shifted -5 hours
I'm using Kontact-1.2.9, KOrganizer-3.5.9 and all exported events has wrong DTSTART and DTEND fields: Meeting is sheduled to take place beetween 17:30 and 18:30 LOCAL time (15:30 - 16:30 UTC). Unfortunately exported ics file has: DTSTART:20080603T173000Z DTEND:20080603T183000Z Which is wrong. It should be either: DTSTART:20080603T153000Z DTEND:20080603T163000Z or DTSTART:20080603T173000 DTEND:20080603T183000 (without trailing Z which if present means UTC)
Don't know if this is a new bug, or a variation on this one. I've noticed this on both my Kubuntu systems. One is still using KDE 4.1.3, while the other is using 4.2b2. I have a Kolab server where all my events are saved in a shared folder. When Kontact (Korganizer) starts up, events show in their text boxes with the correct time/date/timezone information, and for the most part are in the correct position on the grid. However, for late evening events, they will straddle two days. For instance, I am in the New York timezone (USA Eastern) and I have an event for 6pm to 9pm (18:00 to 21:00) on Wednesday nights. When I start Kontact, that event shows up on the grid at 6pm Wednesday AND 6pm Thursday. The box on the left side says: Time: 01/07/09 06:00 pm - 01/07/09 09:00 pm Next Occurrence: 1/14/09 11:00 pm Notice the next occurrence time is for the wrong timezone. Here's how I fix it for the current session only: I open the "Configure Calendar" settings, select "Time and Date". The time zone is listed as "America/New York". I change that to something else (like America/Nassau), click Apply, and "Keep Times" in the popup dialog box. Then I change the time zone setting back to "America/New York", but this time I click "Move Times", then all the duplicate boxes in the grid disappear. Also, the text on the left hand side changes slightly to this: Time: 06:00:00 pm - 9:00:00 pm Date: 01/07/09 Next Occurrence: 01/14/09 06:00 pm Creation Date: 12/17/08 04:58pm You can see that this includes much more information about the event. The date has moved to a separate line and the next occurrence time has corrected itself. There is even a line now for the creation date that wasn't there before. When I restart Kontact, the original behavior returns and I must jump through the hoops again as outlined above.
*** This bug has been confirmed by popular vote. ***
This bug is still present in version 4.13.3 on Arch Linux (so 'Platform' should be 'Linux' I think; I'm not authorized to change it myself). If someone can point me to how to fix it, I can try to come up with a patch someday.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
I have a similar problem with korganizer 4.14.7, on kubuntu 15.04. The time zone for both my system and korganizer is set to EST (UTC-4h), and so is the time zone in my google calendar. When I import a calendar from google, all events that occur only once are displayed correctly in the agenda view in korganizer. However, when I try to edit one of those events, the time is shown for UTC instead of EST. For example, the agenda is showing an event from 1pm-2pm EST (which is correct), but when I try to edit this event, it shows 5pm-6pm UTC instead. This is not much of an issue and can be solved by just changing both the time and time zone to what it should be. For recurring events, it's different: There, the time zone is set correctly to EST, however, the imported times are all wrong. Some events are shifted by 4, others by 5 hours. For example, I have two events displayed at 3pm-4pm EST, but actually one of them should be from 10am-11am and the other from 11am to 12pm. Exporting events from korganizer to google works fine.
(In reply to Denis Kurz from comment #8) > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still > present? > > If noone confirms this bug for a Framework-based version of korganizer > (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets > closed in about three months. See also https://bugs.kde.org/show_bug.cgi?id=373988 Seems actually more appropriate and possibly the central cause.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!