https://bugs.kde.org/show_bug.cgi?id=488082
Rickard Westman <rwest...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|24.05.0 |24.08.1
Resolution|WORKSFORME |---
Ever confirmed|0 |1
Status|NEEDSINFO |REOPENED
--- Comment #2 from Rickard Westman <rwest...@gmail.com> ---
(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.
--
You are receiving this mail because:
You are watching all bug changes.
