Created attachment 170175 [details] KDE system notification settings SUMMARY When a KClock timer has run out, it shows a popup within KClock as well as a system notification. The latter only triggers once per timer, so it you have a timer intended to remind you after e.g. 10 minutes and you then restart it to be reminded again, it won't work as expected. The system notification may be the only thing indicating that the timer has triggered in some scenarios, e.g. if you have minimized XClock (or it is on another workspace) and don't have the audio turned on. STEPS TO REPRODUCE 1. Create a 5-second timer and start it. 2. The "Timer complete" system notification will appear. Dismiss it (and the one within KClock, if needed). 3. Click the start button for the same timer, restarting it. OBSERVED RESULT After 5 seconds, there is no "Timer complete" system notification this time, while the internal popup does work the same. EXPECTED RESULT After restarting the timer, I expected it to trigger in the same way as it did before, i.e. with a system notification as well as the internal popup. The latter can easily be missed in a desktop environment, e.g. if KClock is minimized or on another desktop and the sound is turned off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04.4 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I have attached a screenshot of my KDE system notification settings. There doesn't seem to be an application-specific setting for KClock (but under "Other Applications", "Show popups" is enabled while the other options are not.)
I am currently unable to reproduce this issue on 24.08, please confirm if this still occurs for you on the latest version.
(In reply to Devin Lin from comment #1) > I am currently unable to reproduce this issue on 24.08, please confirm if > this still occurs for you on the latest version. I just tried it with 24.08.1, and can still reproduce it (reported version updated). However, it doesn't seem to be 100% reproducible for me either – sometimes it actually works! But usually not. Two things are consistent, though: a) Once a timer fails to trigger system notifications, it continues to fail. b) A newly created timer always works correctly the first time. Here is my latest attempt at reproducing it, based on a newly started kclock: 1. Created a 5-second timer, and let it run to completion. Correctly got both the system notification and kclock notification. Dismissed them both (system notification first). 2. Re-used the same timer, and let it run to completion. Correctly(!) got both the system notification and kclock notification. Dismissed them both (system notification first). 3. Re-used the same timer, and let it run to completion. Only got the kclock notification, and dismissed it. 4. Repeated step 3 two times with the same negative result. 5. Created a new 6-second timer without removing the previous one. So I now have a 5-second timer A, and a 6-second timer B. B is now displayed above A. 6. Repeated test with timer A, just to see if it's affected by the creation of a new timer (B). But with the same result. 7. Ran the rest with timer B for the first time. Worked correctly. This time I dismissed the kclock notification first, and this automatically removed the system notification. 8. Ran the test with timer B for the second time. Only got the kclock notification. 9. Ran the test with timer B three more times. All failed in the same way. 10. Ran the test with timer A two more times. Both failed, as before. So I could reproduce it like originally reported every time except one. Just to see if the first success above was reproducible, I restarted kclock and repeated steps 1 through 10 exactly as before. But this time, the odd success in step 2 didn't happen. Changed the status to REOPENED, since I provided some info and didn't want to leave it as NEEDINFO.
I apologize for missing notifications for this issue, it appears to have gotten buried in my inbox I still seem to be unable to reproduce it with the steps you provided, I wonder if it's some sort of strange race condition happening with the notification daemon on your system... > There doesn't seem to be an application-specific setting for KClock (but under "Other Applications", "Show popups" is enabled while the other options are not.) There is actually one, if you search for "Clock" in Notifications -> Application Settings, you should be able to see the "Timer finished" notification type. Make sure popups are enabled.
> (In reply to Rickard Westman from comment #2) I was able to almost able to reproduce via these instructions: > 1. [Created a 5-second timer, and let it run to completion. Correctly got both the system notification and kclock notification. Dismissed them both (system notification first).] > 2. Re-used the same timer, and let it run to completion. Correctly(!) got both the system notification and kclock notification. Dismissed them both (system notification first). > 3. Re-used the same timer, and let it run to completion. Only got the kclock notification, and dismissed it. Here is where I was unable to follow the instructions so I closed the kclock window and reopened it. After, I am able to reproduce step 3: Re-used the same timer, and let it run to completion. Only got the kclock notification, and dismissed it. > 4. Repeated step 3 two times with the same negative result. > 5. Created a new 6-second timer without removing the previous one. So I now have a 5-second timer A, and a 6-second timer B. B is now displayed above A. For convenience, at this point I renamed both timers and notice that A's progress bar is reset from 100% to 0%. This leads me to believe it has to do with the timer reset action with the refresh icon. > 6. Repeated test with timer A, just to see if it's affected by the creation of a new timer (B). But with the same result. > 7. Ran the rest with timer B for the first time. Worked correctly. This time I dismissed the kclock notification first, and this automatically removed the system notification. In contrast, B exhibits same issue as A. My reproduction instructions below. I included an example using a preset timer, but I don't think it doesn't make a difference. 1. Create timer preset named repro with 1 second duration, then create timer. Click new timer, set minutes to 0, set seconds to 1, set label to repro, click save as preset, click done. 2. Start timer: click timer icon. 3. Observe system notification as expected. 4. Dismiss KClock done alert: click dismiss 5. Observe system notification closed. 6. Reset timer: click reset icon. 7. Start timer: click timer icon. 8. Observe lack of system notification. 9. Dismiss KClock done alert: click dismiss 10. Observe system notification not present in notification history. 1. Create timer with 1 second duration. Click new timer, set minutes to 0, set seconds to 1, click done. 2. Start timer: click timer icon. 3. Observe system notification as expected. 4. Dismiss KClock done alert: click dismiss 5. Observe system notification closed. 6. Reset timer: click reset icon. 7. Start timer: click timer icon. 8. Observe lack of system notification. 9. Dismiss KClock done alert: click dismiss 10. Observe lack system notification in history. SOFTWARE/OS VERSIONS $ kinfo Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i5-10500T CPU @ 2.30GHz Memory: 64 GiB of RAM (62.5 GiB usable) Graphics Processor: Intel® UHD Graphics 630