Bug 167216 - kopete does not detect user activity
Summary: kopete does not detect user activity
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-22 15:16 UTC by Marcus Better
Modified: 2009-01-22 00:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Better 2008-07-22 15:16:25 UTC 
Version:           0.50.80 (using 4.1.00 (KDE 4.0.99 (4.1 RC1+)), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.25-melech

The activity detection feature seems to be broken in the KDE4 version. When I am inactive for a while, the Jabber status is set to Away, but it stays there even after I start using the system.

I have enabled the "become available when activity detected" checkbox in the settings.
Comment 1 Ramon Antonio Parada (brainsqueezer) 2008-07-23 17:31:38 UTC 
In 0.50.80 (Debian experimental)

1. Configured "Use autoaway" with 1 minute and "become available when activity detected" selected

2. After configured time got "You are now marked as Idle." in a chat window

3. After moving the mouse "You are now marked as Idle."

Shouln't state being changed to away instead of idle?
Comment 2 Ramon Antonio Parada (brainsqueezer) 2008-07-23 17:34:49 UTC 
#2 was when kopete was on focus.

With another app having focus got idle after time but moving mouse didn't took effect until I click chat window
Comment 3 Marcus Better 2008-10-27 09:36:01 UTC 
Confirmed on 0.60.2 (Debian KDE 4.1.2).
Comment 4 Tomas Trnka 2009-01-22 00:09:16 UTC 
Works for me on 0.70.50 (SVN r910502), regardless of Kopete having focus or not. It sets the correct "Away" status and resets to Online upon touching mouse.
Comment 5 Matt Rogers 2009-01-22 00:25:39 UTC 
Reported as fixed for KDE 4.2