https://bugs.kde.org/show_bug.cgi?id=524910
Bug ID: 524910
Summary: [Flatpak] Timer Goes to Negative Values if Previous
Alarm is Still Ringing
Classification: Applications
Product: KClock
Version First 26.04.3
Reported In:
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
DESCRIPTION
When [Two timers are active] the **First one rings**. If the (alarm is not
dismissed), then the **Second alarm, will not activate**. This causes the timer
to keep counting down to negative digits. Even after the **first alarm is
dismissed** the **Second timer stay counting down negative numbers**.
STEPS TO REPRODUCE
1. Start kclock (flatpak).
2. In the timers section set two timers. (ex: First alarm: 10s ; Second alarm:
15s)
3. Start the first alarm, and start the second one shortly before the first
countdown is finished.
4. The first alarm will sound.
5. Don't dismiss alarm.
6. The second alarm will fail to sound, and keeps counting down below zero. If
*loop timer* is active, the *loop timer* will not activate.
OBSERVED RESULT
Timers are able to interfere with each other. If one alarm has reached it's end
state, and sounded the alarm and notification; then until the alarm is
dismissed, other countdown timers are unable to initiate their end sequence.
This causes them to keep counting down below zero, and not alarming the user
via sound or notification.
EXPECTED RESULT
The alarms will act semi-independently.
- End state exists for each alarm.
- End state:
- The end state; sends a notification through desktop.
- puts notification on the app (multiple alarm notifications, should be
presented in a scrollable list in the app; respecting the app boundaries)
- Sound alarm if no other alarms are active, and only deactivates when all
alarms are dismissed:
- alarm_counter += 1
- if (alarm_counter > 0)
- Sound alarm
% a counter seems prone to miscounting by an improperly dismissed notification:
it might be better to have the state of the counters change to 'alarmActive' or
something similar. The sound then checks if any alarms are active | with a
different 'alarmActive' state based on notification sound; if notification
sound by countdown timer is to be added (auditory category: check food, take
break, check on agents, etc.). It is however your codebase your implementation
will likely be better.
SOFTWARE/OS VERSIONS
Operating System: Linux Mint 22.3
Kernel: Linux 6.8.0-138-generic
Kclock - flatpak: 26.04.3 stable
ADDITIONAL INFORMATION
Thank you for fixing the last bug report in a timely manner. The implementation
for the fix is purely a suggestion that you can do with as you please.
--
You are receiving this mail because:
You are watching all bug changes.
