Bug 41118 - bad error message with dns failure
Summary: bad error message with dns failure
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-22 06:35 UTC by Guillaume Desmottes
Modified: 2011-09-29 10:07 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume Desmottes 2011-09-22 06:35:29 UTC
Original bug report: https://bugzilla.gnome.org/show_bug.cgi?id=659819

"""
1. Attempt to log into google talk
2. Error message: "gabble/connection-DEBUG: 22/09/11 14:55:26.505064:
connector_error_disconnect (connection.c:1673): connection failed:
g-resolver-error-quark (#1): connection failed: Error resolving
'talk.google.com': Temporary failure in name resolution" 
3. See the error message  "Disconnected - No reason specified" as shown in the
screenshot.

This is with gabble 0.12.0 on meego (we're going to try upgrading to the latest
and retest) and the meego branch of empathy 2.30.
"""

Looking at MC logs we have:

mcd-DEBUG: 22/09/11 15:24:28.707423: mcd_connection_invalidated_cb: Proxy destroyed (g-resolver-error-quark (#1): connection failed: Error resolving 'talk.google.com': Temporary failure in name resolution)!
mcd-DEBUG: 22/09/11 15:24:28.707442: _mcd_connection_release_tp_connection: 0x9aac178
mcd-DEBUG: 22/09/11 15:24:28.707489: _mcd_account_set_connection_status: gabble/jabber/nick_2erichards_40gmail_2ecom0: 2 because 0
mcd-DEBUG: 22/09/11 15:24:28.707504: mcd_account_freeze_properties: gabble/jabber/nick_2erichards_40gmail_2ecom0
mcd-DEBUG: 22/09/11 15:24:28.707520: _mcd_account_set_connection_status: changing error details
mcd-DEBUG: 22/09/11 15:24:28.707547: _mcd_account_set_connection_status: changing connection status from 1 to 2
mcd-DEBUG: 22/09/11 15:24:28.707564: _mcd_account_set_connection_status: changing connection status reason from 1 to 0

So Gabble uses None_Specified.
Comment 1 Will Thompson 2011-09-22 06:56:45 UTC
Yup, a quick local test (by setting 'server': 'lololol') confirms that this is the case:

signal sender=:1.64 -> dest=(null destination) serial=8133 path=/org/freedesktop/Telepathy/Connection/gabble/jabber/resiak_40topsecrettestserver_2eorg_2fQueeg; interface=org.freedesktop.Telepathy.Connection; member=ConnectionError
   string "org.freedesktop.Telepathy.Error.NotAvailable"
   array [
      dict entry(
         string "debug-message"
         variant             string "g-resolver-error-quark (#0): connection failed: Error resolving 'lolololol': Name or service not known"
      )
   ]
signal sender=:1.64 -> dest=(null destination) serial=8134 path=/org/freedesktop/Telepathy/Connection/gabble/jabber/resiak_40topsecrettestserver_2eorg_2fQueeg; interface=org.freedesktop.Telepathy.Connection; member=StatusChanged
   uint32 2
   uint32 0


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.