Workrave 1.6.0 (todays nightbuild) thinks that I'm active all the time.
After some investigation i noticed that it recognize that button was 
pressed but does not that it was released. 
In file X11InputMonitor.cc in main loop I've added small printf and when I
press button event 4 (ButtonPressed) is generated. But when I release
button no event is generated. I changed mask in XGrabButton call from
ButtonPressMask to ButtonPressMask| ButtonReleaseMask but this has not
hellped. I have XFree86-4.4.0

And when i run 'xev' I see that both ButtonPressed and ButtonReleased events are
generated

Please check if the record extension is enabled in /etc/X11/XF86Config-4:

Section "Module"
        Load    "record"
EndSection

Workrave does not monitor the release event. Each keypress is an activity. As
longs as you keep pressing keys (or keep moving your mouse), workrave assume you
are active. activity does not end by releasing the mouse button.

Are you running some video player that artificially create keyboard button
events to "disable" the screensaver? I have seen such a player (forgot which one)

I was talking about BUTTON (mouse button) not key from keyboard. I had no "load
record" but i've added it and workrave still does no work correctly.

*** Bug 403 has been marked as a duplicate of this bug. ***

Hey there,

I posted a report to Debian BTS about this which got forwarded here (actually,
to the dupe mentioned above).  As a workaround I downgraded from the package in
sid (1.6.1-2) to the package in sarge (1.4.1-1).  This older package does not
suffer from the bug described here.

Not sure if this has to do with Gnome 2.6 (which only recently was put in sid)
or what, but I'd be glad to provide any information necessary to squash it.

-Andrew

I've never seen this bug myself, so I'm really puzzled.

A few questions.
- Do all breaks ignore activity?
- Is 'suspend when inactive' enabled for all breaks?
- Is networking enabled? (Does the debian package have networking support?)
- Does workrave show a break window after removing the warning window.
- What happens when a break window appears? Does the break count-down or does
the time remain the same all the time ?
- After starting workrave, do the timers start immediately, or do they start
when you first become active?
- Do the timers keep running indefinately

Could you mail me (or attach to bugzilla) the output of:

gconftool-2 --dump /apps/workrave

(You may want to remove your networking password from the output)

and the content of ~/.workrave

(I'm interested in 'state' and 'idlelog*' files. These files contain information
on your computer usage. You may not want to make them public by attachting them
to bugzilla)

This might help debugging a lot. Thanks.

I hope this bug is now fixed.... Pawel's analysis was very accurate.
Unfortunately, I didn't understand it at first....

I thought workrave didn't need the 'button released' event. Only button presses
are counted as activity. However, the fix for bug #335 requires button release
events....Xrecord should deliver these events [so here is an inconsistency with
Pawel's comment that enabling xrecord didn't help]. However, when xrecord is not
available or fails, workrave falls back to a dirty hack to monitor keyboard and
mouse. This hack uses the grabbutton (which only grab presses) which does not
detect mouse release events.....

It is very likely that this hack will be removed in a future version of workrave
(>= 1.7)

Everone, please download a nightly build of Jul 2nd or later
(http://workrave.org/download/snapshots/20040702/) and confirm that this bug has
been fixed.

*** Bug 421 has been marked as a duplicate of this bug. ***