After being away from my PC constantly faced with rest breaks. Got a new PC a downloaded / installed rev 1.9.3.
So more or less "forced"" with brakes that aren't interesting.


On my old PC from what I can remember Workrave stopped counting from moment on I left my PC.

Beside this also lost icon at right bottom side. So cannot look / change settings.
Have tried de-installing / installing, but don't want to de-install given something is running and installing fails as well given something is running.

(In reply to comment #0)

This may well be intentional. Can you please confirm that the break window is labeled "Natural Restbreak" ?

Natural restbreaks are activated whenever you lock your screen. (Or whenever the screensaver activates, I'm not sure).

In the old situation, when you leave your computer for longer than your restbreak duration, Workrave resets the timer. This is called a "natural restbreak". If you leave your computer for shorter than your restbreak duration, the timer is not reset. Thus, when you return after, say, your restbreak duration minus 10 seconds, it might be that after a very short time, you are forced to take a break. This is very annoying. If you had stayed away only 10 seconds longer, you would have been allowed to work much longer.

The "Natural Restbreak" window informs you how much time you still need to stay away, to complete the natural restbreak. As an added bonus, workrave will not accidentally consider you active and start the timers. As a downside: if you really want to start working, you have to click the "skip" or "postpone" button. They should always be available, regardless of your settings for "show skip/postpone buttons".

Hope this helps.

I can confirm this also affects Fedora and Ubuntu.

Regardless of the restbreak timer after the screen has been locked a restbreak is enacted. The restbreak should only be enacted if the timer has gone below 0 (orange).

(In reply to comment #2)
> I can confirm this also affects Fedora and Ubuntu.

Not to be ungrateful for your report, but if this is indeed the intended behavior I described in comment #1, then it will affect all platforms.

Could you please confirm that you are indeed seeing the behavior I describe in comment #1, and not something else? It would make the discussion a lot easier if we knew we were all talking about the same thing.

Thanks

(In reply to comment #3)
> 
> Not to be ungrateful for your report, but if this is indeed the intended
> behavior I described in comment #1, then it will affect all platforms.
> 
> Could you please confirm that you are indeed seeing the behavior I describe in
> comment #1, and not something else? It would make the discussion a lot easier
> if we knew we were all talking about the same thing.
> 
> Thanks

Yes, after screen lock a natural rest break occurs.

I also now see why I'm having problems with this functionality. I've got multiple computers on which I work, all linked via network.

When I'm working behind computer A and computer B goes into screensaver (/ lock) and I come back to computer B I get confronted with a 10 minute natural break on computer B. Computer A at that moment goes into a regular rest break.
This is wrong. I should not be confronted by any break.

Forcing a natural break after screen lock is wrong regardless. In a high security environment you're not allowed to leave your computer unlocked whenever you step away. Now you're forced a natural break whenever you come back, regardless of time spent.

(In reply to comment #4)
> Forcing a natural break after screen lock is wrong regardless. In a high
> security environment you're not allowed to leave your computer unlocked
> whenever you step away. Now you're forced a natural break whenever you come
> back, regardless of time spent.

You are not (should not be) in any way forced to take this break. If you don't want it, click "postpone" or "skip", which should always be available (as explained in comment #1)

(In reply to comment #1)
 
Hi, I confirm this behaviour, but find the downside of the new behaviour considerable. I lock the screen every time I walk away from my desk; thus I need to "postpone" at every unlock (in addition to unlocking). I don't force breaks when they are needed, and can skip them if I deem it necessary. Prompting for 5-min break after I'd just taken a 4-minute one happened much less often, so I found the old, automated, behaviour much less obtrusive.

Perhaps it's possible to include an option to regulate this behaviour? Like "prompt for natural rest breaks" yes/no? Sorry if this is the wrong place to request a feature change!

I also lock my screen very often and am confronted with this, in my opinion, broken behaviour.

(In reply to comment #5)
> You are not (should not be) in any way forced to take this break. If you don't
> want it, click "postpone" or "skip", which should always be available (as
> explained in comment #1)

Clicking "postpone" or "skip" has unwanted side effects:
 - Postpone, only postpones this natural break for 5 min. even if the next rest break timer indicates that the next rest break will be in 30 minutes.
 - Skip, will also reset the 'normal' rest break timer. Meaning that if a lock often and use skip, i'll never get a rest break.

I would expect the following behaviour:
 A - Have a configuration option to disable natural rest breaks upon running the screen saver. All other break related behaviour is configurable, why is this not?
 B - When clicking "skip" in a 'natural' rest break the 'normal' rest break timer should not be reset, or else don't make a difference between the two rest breaks.
 (C - remove the postpone button. This is less important, but why would you want to postpone a 'natural' rest break if you already have 'normal' rest breaks)