Bug 28379 - TpAccount::status-changed signal should provide dbus_error_name and error_details
Summary: TpAccount::status-changed signal should provide dbus_error_name and error_det...
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on: 21200
Blocks:
  Show dependency tree / graph
 
Reported: 2010-06-04 03:18 UTC by Guillaume Desmottes
Modified: 2010-06-14 09:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Guillaume Desmottes 2010-06-04 03:18:50 UTC 
From the doc of this signal:
dbus_error_name : currently unused, but for exposing the dbus error name on a connection error in the future

details : currently unused, but for exposing the error details on a connection error in the future

This would be useful to allow Empathy displaying more info on connection errors (https://bugzilla.gnome.org/show_bug.cgi?id=523895 )
Comment 1 Simon McVittie 2010-06-04 03:25:01 UTC 
This is easy to do after the necessary info is added to Account in telepathy-spec, which is itself blocked by having a trial implementation of that feature in MC (an MC branch that put the necessary information on the McdAccount, but didn't expose it to D-Bus, would be sufficient).
Comment 2 Simon McVittie 2010-06-07 11:18:18 UTC 
(In reply to comment #1)
> This is easy to do after the necessary info is added to Account in
> telepathy-spec, which is itself blocked by having a trial implementation of
> that feature in MC (an MC branch that put the necessary information on the
> McdAccount, but didn't expose it to D-Bus, would be sufficient).

The spec is Bug #21200, and I've now done a trial implementation in Bug #28428 if you're interested.
Comment 3 Simon McVittie 2010-06-14 09:10:29 UTC 
Fixed in git for 0.11.7

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.