Summary: | Kalarm crashes on start | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | Vit Pelcak <vit> |
Component: | Akonadi | Assignee: | David Jarvie <djarvie> |
Status: | CLOSED FIXED | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.8.1 | |
Attachments: | kdebug.dbg |
Description
Vit Pelcak
2012-02-03 09:39:50 UTC
I have created new user. Kalarm doesn't crash for him. But it displays several error messages on start. Failed to create default calendar “Alarm templates” Location: /home/test/.kde4/share/apps/kalarm/template.ics (Agent instance creation timeout.) Failed to create default calendar “Archived alarms” Location: /home/test/.kde4/share/apps/kalarm/expired.ics (Agent instance creation timeout.) Failed to create default calendar “Active alarms” Location: /home/test/.kde4/share/apps/kalarm/calendar.ics (Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_kalarm_resource_0': no such name) I'm just translating those messages from Czech, but in general, it should be OK. Concerning the crash, can you please check (using View -> Show Calendars) that the correct number of active alarm calendars have been created. If you only have a single calendar (the default), the list should show only one entry. Can you also capture debug output from KAlarm into a file and attach it to this bug, using the following method: 1) Run 'kdebugdialog --fullmode' and select each of 5950 kalarm 5952 akonadiresource (kalarm) 5955 kdepimlibs (kalarmcal) 2) For each one, select output to File for each of debug, warning and error, and set the same filename for each level. 3) Quit KAlarm. 4) Delete the file whose name was entered in kdebugdialog. 5) Restart KAlarm. 6) Create a new alarm and check that it is displayed twice. 7) As soon as this happens, quit KAlarm to stop more debug output from accumulating in the file. 7) Attach the file to the bug report. 8) Run 'kdebugdialog --fullmode' again to revert the output to its old destination (to avoid filling up the file needlessly). 9) Delete the file and restart KAlarm. Concerning your second comment about the test user, could you please raise a separate bug for this. That will help to keep that bug visible and make sure it doesn't get forgotten. Created attachment 68465 [details]
kdebug.dbg
There are two identical calendars.
I have 2 identical alarms already.
I did as you asked me to do, however now only one alarm is created, not two (what is rather weird since I always had duplicates before).
However when I try to delete one of those two duplicate alarms, kalarm crashes.
I cannot reproduce that bug. Weird.
But I still have 2 calendars. But I have no problem with that. Duplicate entries and crashes bothered me.
Can you check the two identical active alarm calendars, to verify whether they are both for the same file. If you hover over each calendar in the list, a tooltip will appear which shows the calendar file's location. If the calendars are duplicated in this way, you can probably stop the crash occurring by deleting one of the two duplicate calendars, using the Remove button in the calendar list panel. You should also do this for archived alarms and alarm templates. Yes, paths are the same. I also tried to delete any of those two before, but kalarm resfused to delete "Default calendar of active alarms". I cleaned that up by akonadiconsole. No issues since then. Except I have to refill alarms :-/ Thank you. There are really two bugs here: 1) KAlarm is creating duplicate resources when the Akonadi version is first run. 2) It needs to ensure that if duplicate resources exist, only one of them is used. This should prevent duplication of alarms and the crashes you have seen. Duplicate calendars are now automatically disabled, which will prevent duplicate alarms and the crashes you saw. Git commits fa294799294fb4bb17375400f52c86b730724b22 (4.8) and a123ad732cd9210b0e355cac91ebefa38d581a4b (master). Still to do: there should be a message to the user when this happens, and the creation of duplicate resources needs to be prevented. This crash should, I hope, be fixed by commit c55b943be61cded1cedd05e9e6b04612b2d6058c (4.8 branch). If it occurs again after updating to 4.8.1, please reopen it. |