Bug 398404

Summary: Imported alarms from a old kalarm
Product: [Applications] kalarm Reporter: turcovadio <turcovadio>
Component: generalAssignee: David Jarvie <djarvie>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In: 20.08
Attachments: My exported alarms
The present kalarm calendar
attachment-30297-0.html

Description turcovadio 2018-09-08 21:00:52 UTC
Created attachment 114849 [details]
My exported alarms

I am using Kalarm 2.10-11-ak with Debian Jessie (8.10.0) with Xfce 4.10.
Earlier I used Kalarm in Debian Wheezy (7.10.0), from where I export the alarms and I created a file.

In the new OS (Jessie) I imported the alarms from the above mentioned file, and I added a few new alarms.

The Kalarm is configured to start automatically at the start-up of the SO. A lot of times, the displayed alarms are the new ones. The old ones, only appear when I close the Kalarm daemon and start it again.

The old alarms must appear at same time the new ones.
Comment 1 David Jarvie 2018-09-27 17:25:08 UTC
Did you import the alarms into a new calendar file, or into the default file?

Could you please attach your default calendar file (probably ~/.local/share/kalarm/calendar.ics).
Comment 2 turcovadio 2018-09-28 10:07:33 UTC
Created attachment 115290 [details]
The present kalarm calendar
Comment 3 David Jarvie 2018-09-28 18:32:29 UTC
Does the fault happen every time you log in, or did it only happen the first time after importing the alarms?
Comment 4 turcovadio 2018-09-29 06:09:28 UTC
Yes, it happens every time I log in. 

I just discovered the bug - usually I configure an alarm starting at 05:00 and repeating every hour. I have a lot of alarms repeating every day and every hour (I am a procrastinator). Suppose I create an alarm configured to start 10:41 and repeating every hour. 

So, when I open my computer the day after, at some time, only the alarm 10:41 fires. After, I close the kalarm demon, and restart again, all the other alarms 05:00 fire.
Comment 5 David Jarvie 2019-08-31 10:52:20 UTC
I'm sorry this bug report has been left for a long time now.

Can you tell me whether you imported the alarms into the default alarm calendar, or did you import them into a new calendar?
Comment 6 turcovadio 2019-08-31 20:16:13 UTC
Created attachment 122439 [details]
attachment-30297-0.html

I imported the alarms to the default alarm calendar (the default directory).
My best wishes
Luis Duarte

David Jarvie <bugzilla_noreply@kde.org> escreveu no dia sábado, 31/08/2019
à(s) 11:52:

> https://bugs.kde.org/show_bug.cgi?id=398404
>
> --- Comment #5 from David Jarvie <djarvie@kde.org> ---
> I'm sorry this bug report has been left for a long time now.
>
> Can you tell me whether you imported the alarms into the default alarm
> calendar, or did you import them into a new calendar?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 7 David Jarvie 2020-05-22 22:18:25 UTC
I think that this bug probably arose from Akonadi, which acted as an interface between KAlarm and the alarm calendars. A new method of accessing alarm calendars has now been implemented, which will be in the 20.08 KDE release in August, KAlarm version 3.0.0-F.