[Bug 942390] [NEW] won't connect if password is provided from the start

[John de Largentaye]

Public bug reported:

In Empathy, I created a new Jabber account for my corporate server,
filling in the JID and password fields and checking "Remember password.
In "Advanced" I checked "Ignore SSL certificate errors" and "Override
server settings" -> "Server" specified the name of the server. The
account already existed on the server.

Connection failed with "Network error". In a terminal, starting the telepathy-gabble service as:
 WOCKY_DEBUG=xmpp GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy/telepathy-gabble 2>&1 | tee jabber.log

(telepathy-gabble:5553): tp-glib/params-DEBUG: tp_base_protocol_sanitize_parameters: using specified value for account: "user at server"
(telepathy-gabble:5553): tp-glib/params-DEBUG: tp_base_protocol_sanitize_parameters: missing mandatory account parameter password

("user at server" is the redacted JID )

The "missing mandatory account parameter password" was odd since the
password field was odd, since the field was filled in the Empathy UI. I
tried deleting the field and unchecking "Remember password", then
putting an invalid password, but neither changed anything.

I killed and restartd mission-control-5 with "MC_DEBUG=2", and the relevant output was:
(process:5764): mcd-DEBUG: mcd_manager_create_connection: Created a connection 0x1abe3f0 for account: gabble/jabber/user_40server_2ecom0
(process:5764): mcd-DEBUG: _mcd_connection_connect: called for 0x1abe3f0, account gabble/jabber/user_40server_2ecom0
(process:5764): mcd-DEBUG: _mcd_connection_connect_with_params: Trying connect account: gabble/jabber/user_40server_2ecom0
(process:5764): mcd-DEBUG: _mcd_account_set_connection_status: gabble/jabber/user_40server_2ecom0: 1 because 1
(process:5764): mcd-DEBUG: mcd_account_freeze_properties: gabble/jabber/user_40server_2ecom0
(process:5764): mcd-DEBUG: _mcd_account_set_connection_status: changing connection status from 2 to 1
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: Connection
(process:5764): mcd-DEBUG: mcd_account_changed_property: First changed property
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionStatus
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionStatusReason
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionError
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionErrorDetails
(process:5764): mcd-DEBUG: mcd_account_thaw_properties: gabble/jabber/user_40server_2ecom0
(process:5764): mcd-DEBUG: emit_property_changed: called

(process:5764): mcd-WARNING **: request_connection_cb: RequestConnection failed: missing mandatory account parameter password
(process:5764): mcd-DEBUG: _mcd_account_set_connection_status: gabble/jabber/user_40server_2ecom0: 2 because 2
(process:5764): mcd-DEBUG: mcd_account_freeze_properties: gabble/jabber/user_40server_2ecom0
(process:5764): mcd-DEBUG: _mcd_account_set_connection_status: changing connection status from 1 to 2
(process:5764): mcd-DEBUG: _mcd_account_set_connection_status: changing connection status reason from 1 to 2
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: Connection
(process:5764): mcd-DEBUG: mcd_account_changed_property: First changed property
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionStatus
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionStatusReason
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionError
(process:5764): mcd-DEBUG: mcd_account_changed_property: called: ConnectionErrorDetails
(process:5764): mcd-DEBUG: mcd_account_thaw_properties: gabble/jabber/user_40server_2ecom0
(process:5764): mcd-DEBUG: emit_property_changed: called

(again, JID is redacted)

I don't see any evidence that MC is providing the password to Gabble.

I then deleted and recreated the account, omitting the password field
but checking "Ignore SSL errors" and providing the server info. The
connection failed with "Auth failed" (whereas in the same situation the
Gmail connector asked for the password). I then filled in the password
field and then it finally worked.

** Affects: telepathy-gabble (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of
Telepathy, which is subscribed to telepathy-gabble in Ubuntu.
https://bugs.launchpad.net/bugs/942390

Title:
  won't connect if password is provided from the start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/942390/+subscriptions