Instantbird: XMPP fails connecting on self-compile

Error Log

Version 2138 (e3147073a9ba), built debug 32 bit on Win7x64 using pymake

There has not been a commit since 1.2, but 1.2 connects fine to this account.
I created a new profile for running my self-compile.

The following Error Log entries are logged in four bursts of three messages,
until the Accounts windows item displays as failed connection attempt, with error: “Invalid authzid”

No Proxy is used as per settings.

This issue occurs even on using the same Profile, where 1.2 can connect just fine after a first timeout.

---
---

Timestamp: 15.08.2012 12:31:31
Error: Error connecting to hermes6.jabber.org:5222 (Connection timed out.).

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 682
Source Code:
proxy: socket_ready_cb

---

Timestamp: 15.08.2012 12:31:31
Error: Connection attempt failed: Connection timed out.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 593
Source Code:
proxy: purple_proxy_connect_data_disconnect

---

Timestamp: 15.08.2012 12:31:31
Error: Unable to connect to server: Connection timed out..  Trying next SRV record or connecting directly.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/protocols/jabber/jabber.c
Line: 814
Source Code:
jabber: jabber_login_callback

---

Timestamp: 15.08.2012 12:31:52
Error: Error connecting to hermes.jabber.org:5222 (Connection timed out.).

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 682
Source Code:
proxy: socket_ready_cb

---

Timestamp: 15.08.2012 12:31:52
Error: Connection attempt failed: Connection timed out.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 593
Source Code:
proxy: purple_proxy_connect_data_disconnect

---

Timestamp: 15.08.2012 12:31:52
Error: Unable to connect to server: Connection timed out..  Trying next SRV record or connecting directly.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/protocols/jabber/jabber.c
Line: 814
Source Code:
jabber: jabber_login_callback

---

Timestamp: 15.08.2012 12:32:16
Error: Error connecting to hermes6.jabber.org:5222 (Connection timed out.).

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 682
Source Code:
proxy: socket_ready_cb

---

Timestamp: 15.08.2012 12:32:16
Error: Connection attempt failed: Connection timed out.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 593
Source Code:
proxy: purple_proxy_connect_data_disconnect

---

Timestamp: 15.08.2012 12:32:16
Error: Unable to connect to server: Connection timed out..  Trying next SRV record or connecting directly.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/protocols/jabber/jabber.c
Line: 814
Source Code:
jabber: jabber_login_callback

---

Timestamp: 15.08.2012 12:32:37
Error: Error connecting to hermes.jabber.org:5222 (Connection timed out.).

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 682
Source Code:
proxy: socket_ready_cb

---

Timestamp: 15.08.2012 12:32:37
Error: Connection attempt failed: Connection timed out.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/proxy.c
Line: 593
Source Code:
proxy: purple_proxy_connect_data_disconnect

---

Timestamp: 15.08.2012 12:32:37
Error: Unable to connect to server: Connection timed out..  Trying next SRV record or connecting directly.

Source File: http://hg.instantbird.org/instantbird/raw-file/e3147073a9ba/purple/libpurple/protocols/jabber/jabber.c
Line: 814
Source Code:
jabber: jabber_login_callback

Pinging the used Server

Account is @jabber.org, so should connect to jabber.org initially.


$ ping hermes6.jabber.org
Pinging hermes6.jabber.org [208.68.163.220] with 32 bytes of data:
Request timed out.

Sources pointed to (from Error Log entries)

---
# jabber.c

static void
jabber_login_callback(gpointer data, gint source, const gchar *error)
{
	PurpleConnection *gc = data;
	JabberStream *js = purple_connection_get_protocol_data(gc);

	if (source < 0) {
		if (js->srv_rec != NULL) {
			purple_debug_error("jabber", "Unable to connect to server: %s.  Trying next SRV record or connecting directly.\n", error);

---
# proxy.c

static void
purple_proxy_connect_data_disconnect(PurpleProxyConnectData *connect_data, const gchar *error_message)
{
	if (connect_data->child != NULL)
	{
		purple_proxy_connect_cancel(connect_data->child);
		connect_data->child = NULL;
	}

	if (connect_data->inpa > 0)
	{
		purple_input_remove(connect_data->inpa);
		connect_data->inpa = 0;
	}

	if (connect_data->fd >= 0)
	{
		close(connect_data->fd);
		connect_data->fd = -1;
	}

	g_free(connect_data->write_buffer);
	connect_data->write_buffer = NULL;

	g_free(connect_data->read_buffer);
	connect_data->read_buffer = NULL;

	if (error_message != NULL)
	{
		purple_debug_error("proxy", "Connection attempt failed: %s\n",
				error_message);

---
# proxy.c

socket_ready_cb(gpointer data, gint source, PurpleInputCondition cond)
{
	PurpleProxyConnectData *connect_data = data;
	int error = 0;
	int ret;

	/* If the socket-connected message had already been triggered when connect_data
	 * was destroyed via purple_proxy_connect_cancel(), we may get here with a freed connect_data.
	 */
	if (!PURPLE_PROXY_CONNECT_DATA_IS_VALID(connect_data))
		return;

	purple_debug_info("proxy", "Connecting to %s:%d.\n",
					connect_data->host, connect_data->port);

	/*
	 * purple_input_get_error after a non-blocking connect returns -1 if something is
	 * really messed up (bad descriptor, usually). Otherwise, it returns 0 and
	 * error holds what connect would have returned if it blocked until now.
	 * Thus, error == 0 is success, error == EINPROGRESS means "try again",
	 * and anything else is a real error.
	 *
	 * (error == EINPROGRESS can happen after a select because the kernel can
	 * be overly optimistic sometimes. select is just a hint that you might be
	 * able to do something.)
	 */
	ret = purple_input_get_error(connect_data->fd, &error);

	if (ret == 0 && error == EINPROGRESS) {
		/* No worries - we'll be called again later */
		/* TODO: Does this ever happen? */
		purple_debug_info("proxy", "(ret == 0 && error == EINPROGRESS)\n");
		return;
	}

	if (ret != 0 || error != 0) {
		if (ret != 0)
			error = errno;
		purple_debug_error("proxy", "Error connecting to %s:%d (%s).\n",
						connect_data->host, connect_data->port, g_strerror(error));

zDraugr.de

When connecting to the XMPP Host draugr.de a different issue occurs: “Error: Malicious challenge from server”.

Something unexpected as per protocol?