413035 - Auto away is lost when power management turns screen off

Status: RESOLVED INVALID

(Other Applications :: ChatZilla, defect)

Description

[Stéphane Grégoire (yamo)]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8.1.8) Gecko/20071008 Iceape/1.1.5 (Ubuntu-1.1.5-1ubuntu0.7.10)
Build Identifier: ChatZilla 0.9.80-rdmsoft [XULRunner 1.9a8/2007100620]

I'm using the new auto-away fonctionnality thanks for your job.

When I should be away Chatzilla set me away (I first tried 10 then 15 minutes).

DUring this time ScreenSaver appear after 10 minutes and 40 minutes after my screen is going in veille (black screen) and then Chatzilla remove my away!

Then 15 after this Chatzilla set me away and don't again remove the away!

If after that I use My PC Chatzilla remove the away ( This is works fine).

Reproducible: Always

Steps to Reproduce:
1. doing nothing then being away (Normal)
2. screensaver stopping (black screen) then chatzilla remove my away! (Not normal)


Expected Results:  
When Chatzilla set me away and I'm doing nothing on my PC I should still be away until I use my PC.

When using the old away like : /away pas là 
There's no bug.

I'm on Ubuntu Gutsy (7.10) on Gnome, and Xulrunner is coming from the packages of my distribution.

I use Chatzilla on ircnet and irc.epiknet.org

Comment 1

[James Ross]

So, the problem is that it removed the 'away' status when your screen turned off. That *sounds* like a bug either in the nsIIdleService (which ChatZilla uses to tell when you are idle) or, more likely, in the underlying API used by nsIIdleService.

Comment 2

[Stéphane Grégoire (yamo)]

Yes James.
The problem is : " that it removed the 'away' status when your screen turned
off".

Sorry for my bad english.

Comment 3

[:Gijs (he/him)]

Stephane: does Pidgin react the same for your IM away state? Because I'm very suspicious this is a platform bug, not a ChatZilla one, like James suggested in comment #1.

Comment 4

[Stéphane Grégoire (yamo)]

I've tried to use Pidgin on irc and It has the same bug so it might be an Ubuntu gutsy bug.


Should this bug be marked as "INVALID"?

Comment 5

[:Gijs (he/him)]

Yeah. Here we are. :-)