Bug 479774 - Timer does not decrease, break event does not start
Summary: Timer does not decrease, break event does not start
Status: RESOLVED DUPLICATE of bug 422033
Alias: None
Product: rsibreak
Classification: Applications
Component: general (show other bugs)
Version: 0.12.14
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-13 22:46 UTC by valdikss
Modified: 2024-01-13 22:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description valdikss 2024-01-13 22:46:45 UTC
SUMMARY
(version 0.12.15, not 0.12.14)
When the break event occur, the timer ("for a duration of") does not decrease for more than 1 second.

I have 40 seconds short break. When the timer for break event kicks in and window appears, there's constantly either "please relax for 40 seconds" or "please relax for 39 seconds" message, switching between 40 and 39 seconds. It never decreases to 38 seconds or more. After 39 seconds, 40 seconds again.

The window disappears after 5-10 seconds.

Could it be a Wayland-related issue and the application fails to receive keyboard/mouse activity data? I tried to put my mouse cursor inside the window, but that didn't change anything.


STEPS TO REPRODUCE
1. Wait until break event occur and new window appears
2. Do not touch the keyboard or mouse

OBSERVED RESULT
The timer on break event beginning never decreases past 1 second 

EXPECTED RESULT
Break event starts

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.6.9-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 13th Gen Intel® Core™ i5-1340P
Memory: 30,9 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Intel(R) Client Systems
Product Name: NUC13ANKi5
System Version: N11211-203
Comment 1 valdikss 2024-01-13 22:48:20 UTC
*** This bug has been marked as a duplicate of bug 422033 ***