Bug 378120 - Missing error message when trying to create an appointment at a non-existent point in time (daylight-saving)
Summary: Missing error message when trying to create an appointment at a non-existent ...
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-26 19:23 UTC by mkamp
Modified: 2022-11-03 18:16 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 mkamp 2017-03-26 19:23:20 UTC
I tried to create an appointment in my calendar as a reminder to set some old clocks manually to daylight-saving time. 
My timezone is CET / CEST or Europe/Berlin.

When setting the start time to 02:00 on the last sunday in march, the end time fields were empty instead of the expected value start-time +1h ... On another try the end date suddenly was 01.01.1970... I also couldn't finish the dialog, klicking the Okay-Button just did nothing.

It took some time until I realized that the point in time I wanted to address simply doesn't exist: The clock jumps from 01:59 to 03:00 in this night. <facepalm />

---
Expected Behaviour:
When I klicked the Okay-Button, an error message would have been helpful to explain what I was missing. This might also a nice place to hide an easter egg ;-)
---

P.S.:
I did not check what happens if you try this on the last Sunday in October when every minute between 02:00 an 03:00 is doubled?
Comment 1 Justin Zobel 2022-11-03 01:40:02 UTC
Thank you for reporting this issue 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!
Comment 2 mkamp 2022-11-03 18:16:46 UTC
Someone has reminded me that this bug still exists and I just tried to reproduce it on Kubuntu. I'm happy to see that it was fixed in the meantime: Now korganizer complains that I tried to set an invalid start date. :-)