Bug 25149 - TpAccount doesn't fire "status-changed" if the account is removed
Summary: TpAccount doesn't fire "status-changed" if the account is removed
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Simon McVittie
QA Contact: Telepathy bugs list
URL: http://git.collabora.co.uk/?p=user/sm...
Whiteboard:
Keywords: patch
Depends on:
Blocks: 24209
  Show dependency tree / graph
 
Reported: 2009-11-17 10:58 UTC by Rob Bradford
Modified: 2010-01-21 04:04 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Rob Bradford 2009-11-17 10:58:56 UTC 
If the account is removed from the AccountManager the CM gets disconnected but the signal about the disconnection is never propagated through to the Account.

The workaround is to listen for the status change on the Connection from the Account. But since anybody using Account will have to do this it would be nice if the signal can come through Account without the need to listen on another signal.h
Comment 1 Simon McVittie 2009-12-01 09:55:38 UTC 
A better workaround would be to consider the status to have become DISCONNECTED if the TpAccount emits 'invalidated', I think?
Comment 2 Simon McVittie 2009-12-18 11:18:09 UTC 
+patch. Is this what you're after?
Comment 3 Sjoerd Simons 2010-01-21 03:33:26 UTC 
Code looks fine, test would give you some bonus points ;)
Comment 4 Simon McVittie 2010-01-21 04:04:24 UTC 
Merged already, apparently... fixed in 0.9.3 or 0.10.0, whichever comes first.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.