workrave
workrave copied to clipboard
rcaelers
Timers wont stop even not using keys or mouse // Possible issue win10
Describe the bug Micro breaks times wont stop, even the pop up says/ break in 20sec but even I stop using moving mouse, the pop up goes away with no micro pause success. Sometimes it shows up and locks screen but stays blinking (yellow) as someone using the pc and dont allow to rest and to count the time of that rest. Blinking for using.
To Reproduce Steps to reproduce the behavior: Just using the tool.
Expected behavior To detect the pause of not using the pc.
Screenshots If applicable, add screenshots to help explain your problem.
** Windows (please complete the following information in case you encountered the bug on Windows):
- Windows Version: Windows 10
- Workrave Version : 1.10.43
Can confirm this issue; but it seems to be random. I was able to use this application this morning, but my current break does not detect me not working.
Some extra information:
- Using a G502 wireless mouse.
- Windows 10 Pro
I have this issue on Linux/GNOME.
I definitely can reproduce it when my Firefox has an open tab with Google Music or YouTube Music. Whenever this tab is active, Workrave thinks I'm using the computer even if I don't. If I switch to another tab in the browser, after a few seconds Workrave reports no keyboard/mouse usage.
But sometimes switching to another tab doesn't help. Even if I close the browser and all visible windows, and let go of keyboard/mouse it still thinks I'm busy.
OS: Arch Linux GNOME: 3.36.2/Xorg Workrave version: 1.10.44
Restarting Workrave helps: after restart it correctly switches to idle state after some time.
Restarting Workrave helps: after restart it correctly switches to idle state after some time.
Unfortunately this is not the case for me.
I definitely can reproduce it when my Firefox...
Coincidentally, I also use Firefox. Opening a video page (Youtube) causes this behaviour. Pausing the video does the same.
@dimsuz: 1.10.44 fixes an issue in the activity monitor that Workrave uses when running on Gnome (see #181). The symptoms were exactly the same as what you describe. Is Workrave now running fine after the restart? if so, any chance the Workrave that was previously running was still 1.10.43 (1.10.44. was released May 27 on Arch)
@Querijn @ChriStef : In the preferences, in the timers section, monitoring tab. Does it help to toggle the 'Use alternate monitor checkbox'?
See also issue #168.
@rcaelers I am afraid that I am surely reproducing this bug on 1.10.44. Firstly, I have updated my arch packages yesterday, secondly, I have restarted it several times today and after some time of Workrave running this bug started occuring, and only then did I check the version number.
I'll try to come up with a more specific steps to reproduce. I will also try altertnative monitor, didn't know about it. If you'll need me to check something on my system, please ping.
Finally I'll use this opportunity to thank you for your work on Workrave, I have been using it occasionally for some years now and always have found it to be an excellent application, really well made!
@dimsuz: 1.10.44 fixes an issue in the activity monitor that Workrave uses when running on Gnome (see #188). The symptoms were exactly the same as what you describe. Is Workrave now running fine after the restart? if so, any chance the Workrave that was previously running was still 1.10.43 (1.10.44. was released May 27 on Arch)
@Querijn @ChriStef : In the preferences, in the timers section, monitoring tab. Does it help to toggle the 'Use alternate monitor checkbox'?
See also issue #168.
No its not helping... I think most of us have some issue with win/configuration and devices. Like wireless mouse/key. I've notice that my monitor wont go off after 1min that I set it to close and it never actually goes to sleep any time!!! So... I dont know how to help here or tests.
SOLUTION =
As I previously notice that some kind of usb devices connected to my win10 pc and not allowing to sleep my monitor and so the workrave timers.
I found that disabling the USB Selective Suspend setting to my power plan did the trick and all working fine now!!!!
Steps followed: https://windowsreport.com/windows-10-monitor-wont-sleep/
I hope you can give it a try and fix yours. I will keep on testing....
... I installed the last version 1.10.43. Seems ok with use alternate monitor option and 100 sensitivity!
I also think if you change the win time settings monitor off again to other, the problems appear again!!! :/
... I installed the last version 1.10.43. Seems ok with use alternate monitor option and 100 sensitivity!
I also think if you change the win time settings monitor off again to other, the problems appear again!!! :/
this worked for me ive also set usb selective suspend to disabled, but not sure if that did the trick 💯 I had to restart after making all changes.
Experiencing the same with 1.10.44 on Win10 with Micro Timers. When the timer dialog kicks in while I'm doing something typically it stays blinking with the orange frame forever (or at least for a long time). The reason I say it is because at least once, the micro timer resumed counting down after I waited for 30 seconds or so. At other times I waited for more than a minute and it just stand blinking. How much pause time is it needed for the timer to resume counting down? Is this something one can configure?
Could you try the alternate monitor? In the preferences, in the timers section, monitoring tab. Toggle the 'Use alternate monitor checkbox'. You need to restart Workrave after this change.
Could you try the alternate monitor? In the preferences, in the timers section, monitoring tab. Toggle the 'Use alternate monitor checkbox'. You need to restart Workrave after this change.
Thanks Rob. I'm going to give it a try. Although in my case I suspect the "problem" is the "idle" internal setting of 60 seconds. The micro timer kicks in and I have to wait for about this time so that it resumes counting.
Windows Registry Editor Version 5.00
[HKEY_USERS\S-1-5-21-3621534147-1582579059-3562118173-1001\Software\Workrave\monitor]
**"idle"="60000"**
"activity"="0"
"noise"="9000"
"sensitivity"="3"
For a micro timer this is excessive waiting time. I have set it up for 15 seconds every 15 minutes and I'd say people tend probably to use even shorter ones. So 60 seconds of waiting time to be considered idle so that the micro timer dialog stops blinking and resumes counting down is way too much. After testing with the alternate monitor I'm going to set "activity" to a few seconds to see if it helps.
So far problem seems to have been solved by setting "activity" to "5000". This 5 secs interval between subsequent activity confirmation checks seems to do the trick. The micro timer dialog kicks in and any ongoing activity at that moment is ignored, allowing the countdown to normally proceed.
To be more precise, any activity within 5 secs from the dialog start is ignored, After that, if activity persists, the dialog stops the counting and 60 seconds of idle time are then needed for it to resume counting down.
If you still encounter this issue in Workrave 1.10.45, and switching to the 'alternate monitor' does not solve the issue, please try the following:
When you encounter the problem, open the preferences, and go to the 'Monitoring' tab in the Timers section. Press the 'Debug monitoring' button. A new window should appear that shows some internal state and state changes. Wait a minute or so and copy/paste the content of the debug window and add it to this bug report or mail it to me (there should not be any personal data in the logs). Note that this requires version 1.10.45.