comparison libpurple/protocols/jabber/jabber.c @ 30597:adce8f13a749

jabber: Set a connection display name even when using legacy auth Previously, the only place we were setting one was in the bind-result code path, so it was always NULL when doing legacy auth, but that causes issues with jabber_presence_fake_to_self, so let's just have a default init in jabber_stream_new(). Should Fixes #12499

30595:11cfc72c0330

		return NULL;
	}

	js->buddies = g_hash_table_new_full(g_str_hash, g_str_equal,
			g_free, (GDestroyNotify)jabber_buddy_free);

	js->user_jb = jabber_buddy_find(js, user, TRUE);
	g_free(user);
	if (!js->user_jb) {
		/* This basically *can't* fail, but for good measure... */

30597:adce8f13a749

		return NULL;
	}

	js->buddies = g_hash_table_new_full(g_str_hash, g_str_equal,
			g_free, (GDestroyNotify)jabber_buddy_free);

	/* This is overridden during binding, but we need it here
	 * in case the server only does legacy non-sasl auth!.
	 */
	purple_connection_set_display_name(gc, user);

	js->user_jb = jabber_buddy_find(js, user, TRUE);
	g_free(user);
	if (!js->user_jb) {
		/* This basically *can't* fail, but for good measure... */