Bug 484978 - alarms triggered at wrong time
Summary: alarms triggered at wrong time
Status: REPORTED
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: 3.6.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-03 13:19 UTC by meex
Modified: 2024-04-05 23:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description meex 2024-04-03 13:19:03 UTC 
SUMMARY

this issue has been present for some time, likely in previous version(s)

had an alarm set for 4/4/24 6:30a - it was triggered at 4/3/24 ~8:40a

STEPS TO REPRODUCE
1. set a simple alarm for specific date/time in the future
2. observe if the alarm trips at desired time 

OBSERVED RESULT
had an alarm set for 4/4/24 6:30a - it was triggered at 4/3/24 ~8:40a

EXPECTED RESULT
alarm should have triggered at set time

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.6.19-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 11 Graphics
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
System Version: 1.0

ADDITIONAL INFORMATION
```
$ date
Wed Apr  3 09:00:12 AM EDT 2024

$ sudo hwclock --show
2024-04-03 09:00:46.125718-04:00

$ timedatectl
               Local time: Wed 2024-04-03 09:01:35 EDT
           Universal time: Wed 2024-04-03 13:01:35 UTC
                 RTC time: Wed 2024-04-03 13:01:36
                Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
```
Comment 1 meex 2024-04-03 13:49:15 UTC 
i tested clock (kclock) and it works correctly
Comment 2 David Jarvie 2024-04-05 18:47:45 UTC 
Does this happen for all alarms, or only some?

If only some, does it happen for recurring alarms or single occurrence alarms, or both?

If it only happens for recurring alarms, does it happen for all types (e.g. daily, monthly) of recurrence?

Are there any other patterns to when it happens?
Comment 3 meex 2024-04-05 20:48:55 UTC 
i rarely used kalarm, but from my observation it happens for a single event, non-recurring alarm set for some time in the future (a few days in this instance)

i observed this behavior at least several months ago, so i'm not certain it's specific to 3.6.4
Comment 4 David Jarvie 2024-04-05 22:51:40 UTC 
Does it always go wrong?

If the archived alarms file ~/.local/share/kalarm/expired.ics contains the alarm which triggered at the wrong time, can you please attach it.
Comment 5 meex 2024-04-05 23:46:15 UTC 
> Does it always go wrong?

far as i remember, yes

sorry, i removed kalarm and all associated files