Bug 1083 - Timer stops counting down during arrow key scrolling
Status:
RESOLVED INVALID
Component:
Core :: Win32
Version:
1.9.4
Hardware:
All All
Importance:
P5 normal
Target Milestone:
---
Assignee:
Ray Satiro
URL:
Depends on:
Blocks:
Reported:
Jul 31 2012 00:39:45 UTC
by:
Travis Owens
Modified:
Sep 9 2012 02:39:46 UTC
CC List:
Ray Satiro
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ray Satiro | Sep 6 2012 04:33:14 UTC | cc | Ray Satiro | |
| status | NEW | ASSIGNED | ||
| assigned_to | Raymond Penners | Ray Satiro | ||
| Ray Satiro | Sep 9 2012 02:39:46 UTC | status | ASSIGNED | RESOLVED |
| resolution | INVALID |
Description
Travis Owens Jul 31 2012 00:39:45 UTC
I notice then when scrolling with the arrow keys (scanning, reading, etc) that the application seems to stop counting down, in fact in Chrome this moment, my counter seems to ignore ALL keyboard input, it's only measuring mouse as input. So as I typed this bug, my counter reset. I'm using a Microsoft USB keyboard and their mouse.
Comment 1
Travis Owens Jul 31 2012 15:14:24 UTC
I'm suspecting that perhaps Workrave isn't pointing to my USB keyboard, even though it's the only one connected.
Comment 2
Travis Owens Jul 31 2012 17:23:36 UTC
I switched my keyboard around to my other USB ports (I might have had it in a different port back when I installed WorkRave) and it had to effect, WorkRave is outright ignoring all keyboard input in regards to usage tracking. I re-installed the same version of WorkRave over itself, and it's now tracking the keyboard. Just to double check, I swapped my keyboard to a different port and tested again and Workrave _IS_ still tracking my keyboard on a different USB port, so I have no insight or suggestions to how this bug surfaced.
Comment 3
Ray Satiro Sep 6 2012 04:33:14 UTC
Hi thanks for your report. Have you had this problem in the month since your report? What version of Windows? 32-bit or 64-bit? Are you using an antivirus client? Sometimes they can stop Workrave from hooking mouse and keyboard activity. As far as I know this hasn't been a problem as of late. avast's default behavior is a problem because it sandboxes workrave. There's not much we can do about AV sandboxing except get Workrave signed by a digital signature. Aside from that the burden is on the user to allow Workrave to run outside of an antivirus sandbox. You can try: Preferences > Timers > Monitoring > Use alternate monitor
Comment 4
Travis Owens Sep 8 2012 22:45:58 UTC
Windows 7 64bit I am using NOD32 by Eset.com, which I have been for years, never ran into this scenario. I do NOT run Avast. There's nothing I can try because as I already said, I removed Workrave and reinstalled it and the issue was fixed.
Comment 5
Ray Satiro Sep 9 2012 02:39:46 UTC
Alright then I'm closing this. If you have the same problem please reopen this issue.