Gaim should refresh status for all accounts when returning from hibernate

Bug #64809 reported by Kristoffer Lundén
4
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Invalid
Undecided
Scott Zawalski

Bug Description

When hibernating with Gaim active, and then resuming later, Gaim looks and behaves as if it has active connections and is connected to the network - however, it may just display how it looked when hibernate was invoked.

Eventually, it will come around and update its status by itself, but I've seen this take up to about 20 minutes for an account before it notices that it isn't still connected and refreshes. During this time, there is no indication that the user is not in fact connected and available, unless a message is attempted. Very undiscoverable.

The only workaround (apart from closing and starting Gaim) is to manually set status to Offline, then back to Available/Away etc.

Solution: The system should notify Gaim that it should refresh its status, in some appropriate way. Perhaps upstart could simply tell Gaim to refresh all accounts via dbus or something like that, or maybe a small, active-by-default plugin could be added.

Posting bug here in the first place, because best solution for Ubuntu may be upstart-specific.

Revision history for this message
Jeff Greene (jeffgreene) wrote :

I triaged it and it appears fixed. I am instantly connected when restored from hibernation. Read more about it here: http://gaim.sourceforge.net/sean/blog/tray-icon

Changed in gaim:
status: Unconfirmed → Fix Released
Revision history for this message
Kristoffer Lundén (kristoffer-lunden) wrote :

That would only be if/when network manager is the default in Ubuntu, right? Also, my version of Gaim is not that version yet. Until then, it will only work after manual intervention, by installing NM and upgrading Gaim from CVS.

If it worked for you anyways, what protocol(s) were you testing? It seems that some are quicker than others to react. Also, did it actually go Not Available/Available as it should, or did you just have your connection back this one time? And if it actually worked, how is this possible? :)

Revision history for this message
Kristoffer Lundén (kristoffer-lunden) wrote :

No fix is released, though there might be possible workarounds with next/latest Gaim.

Changed in gaim:
status: Fix Released → Unconfirmed
Revision history for this message
Luke Schierer (lschiere) wrote :

Right, Sean's post is talking about gaim working with network manager, and that functionality depends on it. That code is in beta4.

Revision history for this message
Scott Zawalski (cowbud) wrote :

What version of gaim are you currently using? Was this in feisty? If so this should now be working currectly.

Changed in gaim:
assignee: nobody → cowbud
status: Unconfirmed → Needs Info
Revision history for this message
Kristoffer Lundén (kristoffer-lunden) wrote :

Sorry, no chance to try Feisty at the moment, I suggest you close this then, I'll simply file a new bug or reopen this if it doesn't work when I move to Feisty (but probably I won't have to, then).

Thanks a lot!

Revision history for this message
Scott Zawalski (cowbud) wrote :

No problem, I am currently using feisty and I can tell you that this issue has been resolved here so the wait isn't long for you :)

Changed in gaim:
status: Needs Info → Rejected
Revision history for this message
Xamusk (ronanpaixao) wrote :

I'm running Feisty and the problem may be resolved for Hibernate, but it's still there for suspend.
I'm using Network Manager, and it appears to work right, because it does notify Evolution of the network status.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.