Summary: | KAlarm crashed after trying to upgrade the alarms' format [AlarmCalendar::atLoginAlarms, KAlarmApp::processQueue, KAlarmApp::qt_metacall] | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | Raphael Kubo da Costa <rakuco> |
Component: | general | Assignee: | David Jarvie <djarvie> |
Status: | CLOSED FIXED | ||
Severity: | crash | CC: | kde.org, maurice, shaligm, vshader |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | KDE 4.3.3 | |
Attachments: |
.ics files
kalarmrc |
Description
Raphael Kubo da Costa
2009-10-14 16:00:26 UTC
Could you please attach your calendar files: calendar.ics, expired.ics and template.ics in the directory ~/.kde/share/apps/kalarm/ or ~/.kde4/... and also the KAlarm config file ~/.kde/share/config/kalarmrc. Feel free to change the message texts if you want to keep them private. Created attachment 37581 [details]
.ics files
Created attachment 37582 [details]
kalarmrc
The bug occurs when KAlarm is being session restored on login, and when the calendars also have to be updated. The calendar update is done before the KAlarm window is restored, and for some reason after the update, the session restoration data has changed so that no valid window is then found to restore. It turned out that the wrong (non-existent) session configuration file was being accessed if it wasn't read before the calendar file updates. Forcing a read before the calendar updates fixes this. But why does this happen?? Fixed for KDE 4.3.3 (SVN commits 1035835, 1035836). Thanks for reporting this bug. *** Bug 211005 has been marked as a duplicate of this bug. *** *** Bug 195562 has been marked as a duplicate of this bug. *** *** Bug 225618 has been marked as a duplicate of this bug. *** *** Bug 229603 has been marked as a duplicate of this bug. *** |