https://bugs.kde.org/show_bug.cgi?id=434026
--- Comment #7 from Vojtěch Bartoň <gamingforyou...@gmail.com> --- (In reply to Alois Wohlschlager from comment #6) > Ok, so what happens is the following: > > * The applet doesn't know that year 0 is not a thing, so it happily passes > year 0 around. The "10" is actually a leftover from the decade previously > visited, when you run plasmashell from the terminal, you will see the > message ".../DayDelegate.qml:108:9: Unable to assign [undefined] to QString". > * Due to this, in > .../plasma-framework/src/declarativeimports/calendar/daysmodel.cpp:90, two > null (invalid) dates will be passed to eventsPlugin->loadEventsForDateRange. > * This function will enter an infinite loop because the loop variable "date" > will be the null date, and hence always compare less-or-equal to the null > date that was specified as the end of the range. > > So this problem is confined to year 0, and possible fixes are either > correctly treating it as year -1 or outright disallowing access to years > that early. > > (As an unrelated note, moon phases of dates not in the range of years 1933 > to 2047 should be taken with a grain of salt due to overflow issues in the > vendored Berkeley code. I will fix this soon.) Very interesting! If you're planning on fixing the issue, don't treat year 0 as -1. Negative years crash plasmashell, if you have Astronomical events or Holidays turned on. -- You are receiving this mail because: You are watching all bug changes.
