Loading Profile...
How to fix logging disable from ScreenSaver?
My RescueTime is disables logging when my computer goes to screensaver and locks. It does not automatically start logging again.
I’m frustrated
6
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?We are aware of the issue and I'm working on putting together an update to fix it. I should have that out there shortly.
Thanks! -
Inappropriate?I believe the same problem occurs when you go to Start | Log-Off | Switch Users and then return. You must manually re-enable logging :(
I’m frustrated
-
Inappropriate?I have pushed out an update that should resolve this (1.0.5.20). Perform a "Check for updates" or restart RescueTime and it should get the patch.
Let me know if this update doesn't resolve the issue.
Thank you
1 person says
this solves the problem
-
Inappropriate?I did an update, exited, restarted, then switched users and came back. It works! I admit it's a very short test, but so far so good. TYVM. Amazingly fast turnaround! :) Good work.
-
Inappropriate?My initial testing confirms that this seems to be fixed. I've only tested it quickly, but I'll let you know if this reoccurs. Thanks so much for the quick patch!
I’m happy
-
Inappropriate?This issue did seem to be resolved initially, but in continuing to use the latest version, I've seen RescueTime still experience issues starting to log again. If I lock my computer and unlock it, RescueTime seems to resume logging within a few seconds (it still takes longer than it used to!). However, if my computer goes to screensaver and then I unlock it, that's when I've noticed long delays/failure to resume logging.1 Comment Add a comment
This solves the problem
-
Robert, if you are still seeing this issue, could you email me at team@rescuetime.com ? I have been unable to reproduce this issue with screen savers, however we've had another user report the same thing. I'm hoping to get a bit more information about your setup in an attempt to reproduce it on out testing systems.
Thanks! -
Inappropriate?Thanks for the letting me know Robert, I'll do some more testing with that scenario. The reason it takes a couple of seconds longer when unlocking, is that they check now occurs during the scan interval, so we can handling the Logging Between functionality that was added with version 1.0.5. So, depending on what you have your scan interval set to, that's how long it will take for RescueTime to realize that it has been woken up.
I'll let you know what I find out with the screen saver scenario.
Thanks! -
Inappropriate?It has solved the problem for me. I haven't experienced the problem since I downloaded the update. Thanks!
I’m thankful
-
Inappropriate?I'm running 1.0.7.1 and still have this problem from time to time. In case it matters, the "Logging HotKey" and "Only Log Between" options are both disabled. -
Inappropriate?I've actually seen this problem come back in a recent update, as well. I'm running 1.0.7.01
-
Inappropriate?I will re-open this bug and take a look at what I screwed up with the 1.0.7.01 update ;)
Thanks -
Inappropriate?Same here, it's back in 1.0.7.01
-
-
Inappropriate?I'm testing another fix for this now. It's a really weird issue and it is hard to reproduce on our test systems. Once I think I've got a workable solution, I will post information on a test build to see if I can get you guys to verify that the fix works.
Thanks!
EMPLOYEE
