GNOME Bugzilla – Bug 642408
Presence goes to Away when idle, although Busy was set
Last modified: 2012-02-08 16:55:27 UTC
i set my presence to Busy before leaving the computer for some minutes.. I went into the kitchen to do some painting, then i returned to my computer. I noticed that it was now set to Away, obviously an Auto-Away aka Idle. As soon as i moved the mouse, Away jumped back to Busy. This shouldn't happen. Busy a.k.a. Do Not Disturb is a mode explicitly set by the User. This means the User doesn't want it to be changed, unless explicitly instructed. Away should never kick in automatically while DnD aka Busy is set. origin: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/706877
I can also confirm this with "Hidden" status in 3.2.0 I would think switching to idle should only happen with "Available" status only. It's very annoying with the hidden status because you appear as if you signed on with idling then off when switching back to hidden.
Indeed we shouldn't change the status if it's Hidden. Re-assigning to gnome-shell as that's the one doing that now.
Created attachment 199435 [details] [review] user-menu: Don't change HIDDEN to EXTENDED_AWAY When the session status changes to IDLE, we automatically adjust the IM presence; however, we should treat HIDDEN the same as OFFLINE and not change the presence. (In reply to comment #2) > Indeed we shouldn't change the status if it's Hidden. Re-assigning to > gnome-shell as that's the one doing that now. Yeah, it doesn't make sense to change the status from hidden ...
Well I do believe the protocol standard is to put on the EXTENDED_AWAY/IDLE only if the user is set to available. To my knowledge, the purpose of the status is to change to an away-like status if you walk away from your computer while available to talk. This will let your contacts know you are no longer available because you've left your computer temporarily or are temporarily occupied/busy. I would think away and busy would point at a non-temporary status, while idle denotes that you are not available to talk temporarily, thus why I thought busy and away should override idle.
*** Bug 664349 has been marked as a duplicate of this bug. ***
In 3.2: 1- set the shell's status to Busy (disable notifications) 2- go away from the computer and come back, unlock the screen Result: status is set to Away instead of Busy. Expected result: I guess "away" makes sense since I was definitely away from the computer, but now that I'm back it should be set back to Busy.
(In reply to comment #7) > Expected result: I guess "away" makes sense since I was definitely away from > the computer, but now that I'm back it should be set back to Busy. Yes, that's how it is supposed to work. It is unrelated to this issue though, see bug 658955.
In reply to comment 8, nevermind... Either we say "become away then set the status back to busy when coming back" which would make bug 658955 valid (but it would need rewording), or we go by what has been suggested here (ie: never automatically change the status from Busy) and bug 658955 should be closed as invalid. Actually, the more I look at it, the more I think that bug 658955 should be considered a duplicate of this bug report. It's not like it's doing anything but setting the status type (ie: it doesn't change the status "message").
(In reply to comment #9) > In reply to comment 8, nevermind... Either we say "become away then set the > status back to busy when coming back" which would make bug 658955 valid (but it > would need rewording), or we go by what has been suggested here (ie: never > automatically change the status from Busy) and bug 658955 should be closed as > invalid. To be honest, I don't quite understand that. If you look at the screenshot Jon attached to bug 658955, you'll notice that Notifications are enabled, so it is not related to Busy in any way; it is about us failing to revert an automatically set "Away" status to the correct presence after the session comes back from idle. This bug is about not setting Away automatically unless the presence is available (which I disagree with), or at least to not automatically change from Hidden to Away (which makes sense to me). > Actually, the more I look at it, the more I think that bug 658955 should be > considered a duplicate of this bug report. It's not like it's doing anything > but setting the status type (ie: it doesn't change the status "message"). So no, I think the bugs are different: This bug is about changing the intended behavior, bug 658955 is a bug where the shell does not behave as intended (session goes idle => status is set to Away, session comes back => status should be reset from Away, but isn't).
Review of attachment 199435 [details] [review]: Seems fine as far as I can tell
Comment on attachment 199435 [details] [review] user-menu: Don't change HIDDEN to EXTENDED_AWAY Attachment 199435 [details] pushed as b3936ec - user-menu: Don't change HIDDEN to EXTENDED_AWAY
I talked with the designers on IRC, and they agreed that changing presence from Busy to Away when idle is the correct behavior. So there's nothing left to do here ...