There is indeed a key present for that account. (I wasn't previously aware of this keyring interface, though I had looked for it).
I deleted the key from that store, the proceeded to delete the account from empathy and kill telepathy subsystems. Recreated the jabber account, *not* providing password nor server nor ssl ignore -> Network error. Set server and ssl ignore in Empathy accounts -> Network error. Set password, expecting it to work as previously described, but got Network error again! Checked that password was present and correct in "Keys & Password", it is. So now I am no longer able to connect, it's complaining about missing password despite it being present in the Empathy UI *and* the Keys & Passwords store. Clearing the password from Empathy deletes it from the password store (note: restart "Keys & Password" to see the change, there is no "refresh"). However, deleting the account in Empathy does *not* delete the password from the store. I then quit Empathy and killed Telepathy daemons, restarted Empathy, recreated the account *omitting* the password, and it worked. Attached mc-log. ** Attachment added: "mc-log-3.txt" https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/942390/+attachment/2791491/+files/mc-log-3.txt -- You received this bug notification because you are a member of Desktop Packages, 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 Status in “telepathy-gabble” package in Ubuntu: Incomplete Bug description: 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@server" (telepathy-gabble:5553): tp-glib/params-DEBUG: tp_base_protocol_sanitize_parameters: missing mandatory account parameter password ("user@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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/942390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
