Using Ubuntu 14.04, KOrganizer worked fine when the time was inserted on a new event. It showed and printed off properly. When the operating system was upgraded to 16.04 the time shows properly on the event but on the calendar and when printed out it is five hours in advance. This occurred both on a machine that was upgraded from 14.04 to 16.04 and on a machine in which 16.04 was freshly installed. When you go to Settings, Configure Date and Time, you receive an error message “Could not start control module for date and time format.” In the new event menu, the only time zone options available are UTC and Floating. This problem does not occur when the time zone is set at Floating. However, the default is UTC. Events entered prior to the operating system upgrade show the prior time zone (Chicago) and the correct time but when closed, show on the calendar (and print) five hours in advance. I would appreciate any help in correcting this problem. Thank you. John Reproducible: Couldn't Reproduce
Follow up to bug report. We have three calendars created on KOrganizer. If we adjust all the existing appointments (that show up 5 hours in advance) to Floating so that they appear on the calendar at the right time, the adjustments only works on the machine they are being done on. The calendars on the other two machines do not adjust. There is a server that the calendar is on so all three calendars should update to reflect the same changes. The calendar is not updating. It is not keeping new appointments and they aren't appearing on the other two computers. They are not syncing. One of our calendars keeps crashing with the following error: There was a problem with the request. The item has not been detected. The file or folder on machine4 does not exist. We have not moved or removed any files or folders. All three calendars are set up the same except for username.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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 mark the bug 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!
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!