Summary: | If you pause a timer, KClock will ring an alarm at the moment the timer would have finished. | ||
---|---|---|---|
Product: | [Applications] KClock | Reporter: | pawlowski486 |
Component: | General | Assignee: | Devin Lin <espidev> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | hanyoung |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/powerdevil/commit/0dfefa03038650830c0797b03c66e6eb61ba3e40 | Version Fixed In: |
Description
pawlowski486
2023-01-13 20:08:23 UTC
I am having a hard time trying to reproduce this bug. Could you please try running kclockd manually (flatpak run --command=kclockd org.kde.kclock) and giving me the output when triggering the bug? (In reply to Devin Lin from comment #1) > I am having a hard time trying to reproduce this bug. Could you please try > running kclockd manually (flatpak run --command=kclockd org.kde.kclock) and > giving me the output when triggering the bug? First, here's a video of me performing the glitch: https://icefangvault.myusa.cloud/index.php/s/PL5aJstzJCPjfFd OBS used a format that Firefox can't play, so you may need to open it in VLC. Here's the console output, but it doesn't seem to have anything to do with the issue I'm having: [wolfi@The-Iceberg ~]$ flatpak run --command=kclockd org.kde.kclock [wolfi@The-Iceberg ~]$ flatpak run org.kde.kclock qrc:/qml/time/TimePage.qml:18:1: QML TimePage: Binding loop detected for property "implicitHeight" file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9: QML ListView: Binding loop detected for property "topMargin" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected for property "y" file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9: QML ListView: Binding loop detected for property "topMargin" file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9: QML ListView: Binding loop detected for property "topMargin" (In reply to pawlowski486 from comment #2) > (In reply to Devin Lin from comment #1) > > I am having a hard time trying to reproduce this bug. Could you please try > > running kclockd manually (flatpak run --command=kclockd org.kde.kclock) and > > giving me the output when triggering the bug? > > First, here's a video of me performing the glitch: > https://icefangvault.myusa.cloud/index.php/s/PL5aJstzJCPjfFd OBS used a > format that Firefox can't play, so you may need to open it in VLC. > > Here's the console output, but it doesn't seem to have anything to do with > the issue I'm having: > > [wolfi@The-Iceberg ~]$ flatpak run --command=kclockd org.kde.kclock > [wolfi@The-Iceberg ~]$ flatpak run org.kde.kclock > qrc:/qml/time/TimePage.qml:18:1: QML TimePage: Binding loop detected for > property "implicitHeight" > file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9: QML > ListView: Binding loop detected for property "topMargin" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > qrc:/qml/timer/TimerFormWrapper.qml:98:9: QML Dialog: Binding loop detected > for property "y" > file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9: QML > ListView: Binding loop detected for property "topMargin" > file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:132:9: QML > ListView: Binding loop detected for property "topMargin" Ahh, sorry for the delay. So if there are no logs when running kclockd, it means that it is already running, so we will need to stop it first with flatpak kill org.kde.kclock Aha, seems you actually found an issue in Plasma, here is the fix: https://invent.kde.org/plasma/powerdevil/-/merge_requests/129 Git commit a5575edc8bb7da61a7ae0e4237f699203b367b38 by Devin Lin. Committed on 19/01/2023 at 15:32. Pushed by devinlin into branch 'master'. daemon: Fix wakeup removal not rescheduling the timerfd wakeup Fixes wakeup removal for the current event from sometimes not rescheduling the timerfd wakeup for the next event, causing the current event to trigger for another cookie. This happens because error checking condition was invalid; events can get removed from the middle of the list as well. We experienced this issue in kclock, which can be read about here: https://bugs.kde.org/show_bug.cgi?id=464251 M +4 -2 daemon/powerdevilcore.cpp https://invent.kde.org/plasma/powerdevil/commit/a5575edc8bb7da61a7ae0e4237f699203b367b38 Git commit 0dfefa03038650830c0797b03c66e6eb61ba3e40 by Devin Lin. Committed on 19/01/2023 at 16:18. Pushed by devinlin into branch 'Plasma/5.27'. daemon: Fix wakeup removal not rescheduling the timerfd wakeup Fixes wakeup removal for the current event from sometimes not rescheduling the timerfd wakeup for the next event, causing the current event to trigger for another cookie. This happens because error checking condition was invalid; events can get removed from the middle of the list as well. We experienced this issue in kclock, which can be read about here: https://bugs.kde.org/show_bug.cgi?id=464251 Fix M +5 -3 daemon/powerdevilcore.cpp https://invent.kde.org/plasma/powerdevil/commit/0dfefa03038650830c0797b03c66e6eb61ba3e40 |