After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 523895 - Use ConnectionError for better error reporting
Use ConnectionError for better error reporting
Status: RESOLVED FIXED
Product: empathy
Classification: Core
Component: Accounts
0.22.x
Other Linux
: Normal enhancement
: ---
Assigned To: empathy-maint
: 600016 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-03-22 19:47 UTC by Diego González
Modified: 2010-09-13 13:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
http://git.Collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/connection-error-523895 (6.76 KB, patch)
2010-08-05 11:58 UTC, Guillaume Desmottes
none Details | Review

Description Diego González 2008-03-22 19:47:52 UTC
i just compiled empathy and all (the needed modules), after playing a bit and looking at some web pages i got to correctly configure my gtalk account so that i could use it.

During this process, i had to try a lot of different things, during this process empathy didn't show any error saying why it was not connecting.

There should be some errors about this fact, what is wrong in the configuration provided and why it cannot connect to the servers.

Also there is something very akward in the gtalk configuration options:
  Encryption required (which has to be off)
  Use old SSL (which has to be on)

It cannot understand it and it is misleading.
Comment 1 Guillaume Desmottes 2008-04-09 10:36:34 UTC
I agree, error messages could be improved.
Comment 2 Xavier Claessens 2008-04-09 11:43:16 UTC
Empathy reports connection errors the CM gives. It can't tell more with the current tp spec.
Comment 3 Guillaume Desmottes 2008-04-09 12:09:31 UTC
We could display the error message, it's not localized but that's better than nothing. Maybe hide it as advanced/more explanation as Nautilus does for some error dialogs?
Comment 4 Xavier Claessens 2008-04-09 12:26:02 UTC
The only thing the CM gives to empathy is a reason code, here are possibilities:

typedef enum {
    TP_CONNECTION_STATUS_REASON_NONE_SPECIFIED = 0,
    TP_CONNECTION_STATUS_REASON_REQUESTED = 1,
    TP_CONNECTION_STATUS_REASON_NETWORK_ERROR = 2,
    TP_CONNECTION_STATUS_REASON_AUTHENTICATION_FAILED = 3,
    TP_CONNECTION_STATUS_REASON_ENCRYPTION_ERROR = 4,
    TP_CONNECTION_STATUS_REASON_NAME_IN_USE = 5,
    TP_CONNECTION_STATUS_REASON_CERT_NOT_PROVIDED = 6,
    TP_CONNECTION_STATUS_REASON_CERT_UNTRUSTED = 7,
    TP_CONNECTION_STATUS_REASON_CERT_EXPIRED = 8,
    TP_CONNECTION_STATUS_REASON_CERT_NOT_ACTIVATED = 9,
    TP_CONNECTION_STATUS_REASON_CERT_HOSTNAME_MISMATCH = 10,
    TP_CONNECTION_STATUS_REASON_CERT_FINGERPRINT_MISMATCH = 11,
    TP_CONNECTION_STATUS_REASON_CERT_SELF_SIGNED = 12,
    TP_CONNECTION_STATUS_REASON_CERT_OTHER_ERROR = 13,
} TpConnectionStatusReason;

For each case empathy has a little translated text... But it can't do more.
Comment 5 Guillaume Desmottes 2009-08-25 14:21:29 UTC
Empathy could use the ConnectionError signal for better error reporting.

http://telepathy.freedesktop.org/spec/org.freedesktop.Telepathy.Connection.html#org.freedesktop.Telepathy.Connection.ConnectionError
Comment 6 Guillaume Desmottes 2010-06-04 10:19:09 UTC
This is blocked by: https://bugs.freedesktop.org/show_bug.cgi?id=28379
Comment 7 Guillaume Desmottes 2010-08-05 11:58:24 UTC
Created attachment 167182 [details] [review]
http://git.Collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/connection-error-523895

 libempathy/empathy-utils.c    |   86 ++++++++++++++++++++++++++++++++++++++++-
 libempathy/empathy-utils.h    |    4 +-
 src/empathy-accounts-dialog.c |    4 +-
 src/empathy-main-window.c     |   10 +---
 4 files changed, 93 insertions(+), 11 deletions(-)
Comment 8 Guillaume Desmottes 2010-08-05 12:20:01 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 9 Guillaume Desmottes 2010-09-13 13:28:24 UTC
*** Bug 600016 has been marked as a duplicate of this bug. ***