Empathy Not working in other gmail accounts

Bug #1440407 reported by prasad.ram
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi i am using ubuntu 12.04 LTS.
Output of lsb_release -rd

Description: Ubuntu 12.04.4 LTS
Release: 12.04

Output for policy

empathy:
  Installed: 3.4.2.3-0ubuntu1.1
  Candidate: 3.4.2.3-0ubuntu1.1
  Version table:
 *** 3.4.2.3-0ubuntu1.1 0
        500 http://in.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        100 /var/lib/dpkg/status
     3.4.1-0ubuntu1 0
        500 http://in.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
     2.30.0.1-0ubuntu3 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main i386 Packages

 i configured one gmail account let's suppose account1 in empathy. Now i want to add one more gmail account to empathy which is account2. while i was trying to connect to account2 it's giving "Authentication Failed" error , i tried so many times to check my password i gave the same password in gmail also there it's working. But if login with my account1 it's working. So atlast i found that apart from account1 it was not accepting any other gmail accounts. So please help me to solve this problem. The below are logs of type Empathy.Auth

empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.294514: handle_channels: Handle TLS or SASL carrier channels.
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.294583: tls_handler_init_async: Received hostname: gmail.com
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.294624: tls_handler_init_async: Received reference identities: gmail.com, talk.google.com, talk.google.com
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.294665: tls_handler_init_async: Creating an EmpathyTLSCertificate for path /org/freedesktop/Telepathy/Connection/gabble/jabber/prasad_2edeveloper126_40gmail_2ecom_2fd5b24ae6/ServerTLSChannel1/TLSCertificateObject, bus name :1.191
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.295877: tls_certificate_got_all_cb: Got a certificate chain long 3, of type x509
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.295979: auth_factory_new_tls_handler_cb: New TLS server handler received from the factory
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.296041: empathy_tls_verifier_verify_async: Starting verification
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.296294: empathy_server_tls_handler_finalize: 0x9a25af0
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.315774: perform_verification: Performing verification
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.315851: debug_certificate_chain: Certificate chain: length 4 status anchored
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.316283: debug_certificate: Certificate: C=US, ST=California, L=Mountain View, O=Google Inc, CN=gmail.com
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.316540: debug_certificate: Certificate: C=US, O=Google Inc, CN=Google Internet Authority G2
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.316792: debug_certificate: Certificate: C=US, O=GeoTrust Inc., CN=GeoTrust Global CA
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.317260: debug_certificate: Certificate: C=US, O=Equifax, OU=Equifax Secure Certificate Authority
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.324692: perform_verification: Certificate verification gave result 1 with reason 0
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.324975: perform_verification: Hostname matched
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.325108: complete_verification: Verification successful, completing...
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.325525: empathy_tls_certificate_accept_async: Accepting TLS certificate
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.327199: empathy_tls_verifier_finalize: 0x9a25b90
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.327491: cert_proxy_accept_cb: Callback for accept(), error (nil)
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.327876: empathy_tls_certificate_finalize: 0x9a14068
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.523294: observe_channels: New auth channel to observe
empathy/Other-DEBUG: Saturday 04 April 2015 13:15:29.523351: empathy_keyring_get_account_password_async: Trying to get password for: gabble/jabber/prasad_2edeveloper126_40gmail_2ecom0
empathy/Other-DEBUG: Saturday 04 April 2015 13:15:29.527056: find_items_cb: Got 1 secrets; use the first one
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.527215: get_password_cb: We have a password for account /org/freedesktop/Telepathy/Account/gabble/jabber/prasad_2edeveloper126_40gmail_2ecom0, calling Claim
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.528861: password_claim_cb: Claim called successfully
empathy/Other-DEBUG: Saturday 04 April 2015 13:15:29.529205: empathy_keyring_get_account_password_async: Trying to get password for: gabble/jabber/prasad_2edeveloper126_40gmail_2ecom0
empathy/Other-DEBUG: Saturday 04 April 2015 13:15:29.530690: find_items_cb: Got 1 secrets; use the first one
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.530843: auth_factory_new_sasl_handler_cb: New SASL server handler received from the factory
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.530992: empathy_server_sasl_handler_provide_password: Calling StartMechanismWithData with our password
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.532058: empathy_server_sasl_handler_provide_password: not remembering the password
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.532110: empathy_server_sasl_handler_provide_password: MaySaveResponse unknown, assuming TRUE
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.532239: sasl_status_changed_cb: SASL status changed to 'in progress'
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.532299: start_mechanism_with_data_cb: Started mechanism successfully
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.798513: sasl_status_changed_cb: SASL status changed to 'server failed'
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.798572: auth_factory_auth_passsword_failed: Authentification on gabble/jabber/prasad_2edeveloper126_40gmail_2ecom0 failed, popup password dialog
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.891716: base_password_dialog_grab_keyboard: Could not get the event device!
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.893841: base_password_dialog_grab_keyboard: Could not get the event device!
empathy/Tls-DEBUG: Saturday 04 April 2015 13:15:29.894184: sasl_handler_invalidated_cb: SASL handler for channel /org/freedesktop/Telepathy/Connection/gabble/jabber/prasad_2edeveloper126_40gmail_2ecom_2fd5b24ae6/ServerSASLChannel is invalidated, unref it
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.894336: empathy_server_sasl_handler_dispose: 0x9a1b078
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.894471: empathy_server_sasl_handler_finalize: 0x9a1b078
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.916078: base_password_dialog_grab_keyboard: Could not get the event device!
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:29.918900: base_password_dialog_grab_keyboard: Could not get the event device!
empathy/Sasl-DEBUG: Saturday 04 April 2015 13:15:36.656407: base_password_dialog_grab_keyboard: Could not get the event device!

Tags: precise
Ken Sharp (kennybobs)
tags: added: precise
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.