After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 306374 - When set to Busy, Gossip changes presence to Available during idling
When set to Busy, Gossip changes presence to Available during idling
Status: RESOLVED NOTABUG
Product: gossip
Classification: Deprecated
Component: General
0.8.90
Other All
: Normal normal
: ---
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-03 13:44 UTC by Paul van Tilburg
Modified: 2005-06-04 13:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paul van Tilburg 2005-06-03 13:44:58 UTC
Please describe the problem:
When I set myself to Busy with a given message and I wait for 5 minutes, Gossip
sets me to Availble instead of Away and sets it back to Busy again when I become
active.

Steps to reproduce:
1. Set presence to Busy with a given message.
2. Wait 5 minutes while idling.



Actual results:
I am set to Aavailable with the default message.

Expected results:
That I am set to Away.

Does this happen every time?
Yes.

Other information:
Martyn, I think this might be a result of our patch :)
Small log:

[...]
Idle for:296
Idle for:298
Idle for:300
Idle for:302
Going to away...
Idle for:304
[...]
Idle for:316
Idle for:318
OK, away now.
Idle for:320
Going to away...
Idle for:323
Idle for:325
[...etc...]
Comment 1 Paul van Tilburg 2005-06-04 09:28:20 UTC
It even seems that this Available presence when idle is renewed, which seems
logical to me considering the repeated "Going to away..." debug message.
Comment 2 Martyn Russell 2005-06-04 09:31:33 UTC
This was in the patch I gave you to test.

My commit to CVS does NOT have this problem because I set the debug back to:

    #define d(x)

from 

    #define d(x) x

:)
Comment 3 Martyn Russell 2005-06-04 13:35:59 UTC
My apologies on this, I thought you meant the debug output left in the patch was
a bug.

I have fixed this bug also found if you send a message while in the first 15
seconds after being automatically away, it doesn't clear your away state.

I see what you mean now when you asked if there was a state model for the code,
it is a little complex.