Bug 207570

Summary:	kalarm skips today's alarm if computer was shutdown yesterday
Product:	[Applications] kalarm	Reporter:	Bartemius Crouch <egxoun8uya67izy>
Component:	general	Assignee:	David Jarvie <djarvie>
Status:	CLOSED WAITINGFORINFO
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bartemius Crouch 2009-09-16 13:12:37 UTC

Version:           4:4.3.1-2 (using KDE 4.3.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I have an alarm set to 20:00 every day. At 19:50 I power off the computer and leave. When I come back the next morning, kalarm displays a notification of yesterday's alarm. So far so good. But if I take a look at the scheduled alarms, the next one is set to more than 30 hours, that is, it skips today's alarm and starts the countdown for the next one.

Comment 1 David Jarvie 2009-09-22 07:23:21 UTC

That is the expected behaviour. KAlarm only ever displays one message for any given alarm - if a message is still visible for a previous occurrence of the alarm, no new message is displayed when it is next triggered. This prevents multiple messages piling up if the user isn't sitting at the computer, or if the user doesn't want to acknowledge the alarm yet. If you consider it important to be able to display a separate alarm window for each occurrence, regardless of whether windows from previous occurrences are still visible, please raise this as a wishlist item.

Comment 2 David Jarvie 2009-09-22 07:25:55 UTC

Oops, sorry - I didn't read your report properly. Please ignore what I wrote.

Comment 3 David Jarvie 2009-09-22 16:10:37 UTC

Do you hibernate your computer when you power it off, or do you shut it down?

Could you please attach the following two files:
~/.kde/share/config/kalarmrc
~/.kde/share/apps/kalarm/calendar.ics

The latter file is the KAlarm calendar file - if you want details to remain private, you can edit out all the other alarms except the one you're having trouble with, or alternatively change the alarm texts.

Comment 4 David Jarvie 2009-10-10 21:38:38 UTC

Can you please supply the information requested in comment 3. Without this, it won't be possible to investigate the bug.

Comment 5 David Jarvie 2009-11-08 23:42:11 UTC

Marking as resolved, because the reporter has not responded to requests for information which would enable the bug to be investigated.

Comment 6 David Jarvie 2010-03-10 20:40:03 UTC

Closing because no information has been supplied after 6 months.