Bug#1021884: libical3 bug was responsible

Sorry, I should have closed this bug. The problem was caused by a regression in libical3: see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021698 Mind you, korganizer should not have dumped core... ael

Bug#1021938: libical bug

huge pain to clear away. I could find no way to get kAlarm to suppress such old alarms. Perhaps I missed it somewhere. I guess this bug should now be closed. Should I do that? ael

Bug#1021938: kalarm: .local/share/kalarm/expired.ics is not a valid iCalendar file

cannot be read. These are files that the previous version wrote. Example from a "gdb kalarm" run: kf.calendarcore: "/home/ael/.local/share/kalarm/expired.ics" is not a valid iCalendar file kf.calendarcore: Error parsing vCalendar file: pop on empty Object Stack at line 106

Bug#1021884: korganizer segfaults when adding new event

, but now I get a consistent segfault when adding a new event. That new event might overlap the time slot for an existing event. But whatever, a seg fault is always serious I ran under gdb to try to get some diagnostics. gdb.txt session log attached. ael -- System Information: Debian Release

Bug#539253: korganizer: Appointments lost (hidden) after email setting silently changed

Package: korganizer Version: 4:4.2.2-1 Severity: normal This may be related to #505770 All my appointments were lost - not displayed - because they were attached to nob...@nowhere (by default from earlier versions?). I discovered under 'settings' that Use email settings from System settings had