SUMMARY I always wanted to use KOrganizer, but it was broken in KDE4; now it's broken in other ways. I put in an appointment for 4:30 PM, and KOrganizer put it on my schedule at 8:30AM! This is unusable! STEPS TO REPRODUCE 1. While not at UTC/GMT, make an appointment. 2. Check appointment. 3. See it may be offset. OBSERVED RESULT Doesn't use time given. EXPECTED RESULT Use time given. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware 14-current/5.20.2 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION
What time zone are you using? (In the System Settings application, it is in Personalization » Regional Settings » Date and Time, on the Time Zone tab. On the command line, timedatectl will print it out.) When you create an event, does the dialog display a specific time zone next to the start date and time, or does it display a "Time zones >>" link? If you click that link, what time zone does it display? What kind of calendar did you create the event in? For instance, was it an ICS file, or a Google calendar, or something else?
FALSE; you need to learn more about Unix and strictly Unix-like GNU/Linux, the only such one being Slackware, listed above. Strictly Unix[-like] like Slackware GNU/Linux, FreeBSD Unix, etc., have /etc/localtime, not timedatectl, because that's part of the Apple-/Windows-like systemd which of course isn't Unix-like. The time zone I am using is US/Pacific (UTC-8/PST currently, otherwise UTC-7/PDT) and my clock is correct. However, as reported in another bug, KDE apparently no longer always (maybe sometimes) reads /etc/localtime and has set my time zone to UTC (unchangeable) despite showing the time for UTC-8. That happened about after US/Pacific switch from standard (PST) to daylight saving (PDT) time... before that KDE either used /etc/localtime or accepted input of US/Pacific or the main city used for it in my time zone, which was set fine since last year. I wanted to use a normal KOrganizer calendar but it seems that option has been removed. I am also using a Google calendar, but at least on calendar.google.com times work right! If I set something there and reload KOrganizer the time is correct. Even if I wanted to set an event just four hours ahead, with this bug, it wouldn't set the event because would revise the time I entered to four hours before, as if it already happened. So it's not always just what time zone KDE is using (without permission) but that times the user enters get modified (without permission)
To elaborate, my /etc/localtime is US/Pacific (not just Los Angeles) but in KDE's settings, some weeks ago (about when PDT became PST) KDE changed it's own settings from Los Angeles (standard city for most of USA's Pacific time, but not actually the zone) to UTC and it can't be changed to any other zone (described in the other bug report.) What KDE is using is not what my system is using except KDE for some reason does show the correct time, contradicting what zone KDE says it's using. My system clock isn't set to UTC (isn't a server) just is set to US/Pacific.
After KDE finally accepted my time zone (after several error messages & failures) this is currently not a problem... but would be if KDE was using my PC's internal clock time that's correct for my time zone (PT) but KDE automatically chose the wrong time zone and it didn't let me change (UTC, which is what had happened)... now it does.
korganizer-22.04.1-x86_64-1
I think fresh reinstall fixed this but something might cause it to reoccur, which I can't test because KOrganizer apparently can no longer use Google Calendar.