https://bugs.kde.org/show_bug.cgi?id=520615
Bug ID: 520615
Summary: Even numbered timers won't make sound and show
negative value in timer when more than 2 timers are
ran
Classification: Applications
Product: KClock
Version First 26.04.1
Reported In:
Platform: Flatpak
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
DESCRIPTION
When I run more than 2 timers in sequence, like 1, 2, 3, 4, the 2nd and 4th
timers won't ring a bell. Instead, they show a negative timer value in the UI
and only the odd ones in the sequence work as expected. I've tried increasing
the number of timers and the bug is consistent.
STEPS TO REPRODUCE
1. Create 4 timers with the following options: Timer1 (10 seconds), Timer2 (20
seconds), Timer3 (30 seconds), Timer4 (40 seconds).
2. Run the timers in order immediately: Timer1, Timer2, Timer3, and finally
Timer4.
3. Notice how Timer1 and Timer3 rings the *timer ended bell*, shows
notification, and stops. Meanwhile, Timer2 and Timer4 don't ring a bell, don't
show notification, and don't stop. Instead, they show negative timer value
going on endlessly.
OBSERVED RESULT
In a sequence of timers being run, the ones which are odd numbered don't run as
expected. They don't ring a bell and show negative timer value going on
endlessly.
EXPECTED RESULT
All timers work as expected, stop when their time is over, and ring a bell.
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
I've noticed that notifications also sometimes don't show for any timers when
multiple timers are ran, until I restart KClock and KClockD. But I couldn't
reproduce it reliably. I use KClock daily on my desktop to manage my time :)
--
You are receiving this mail because:
You are watching all bug changes.
