Pidgin using google talk authorization

2015-06-04 Thread Bill Jobs
Hi, I'm having an issue using pidgin. I am trying to connect/authenticate
my pidgin client to my custom server. After failing to correctly
authenticate, I browsed through the debug output provided below:Pidgin
Debug Log : Thu 04 Jun 2015 04:14:02 PM CDT
(16:13:18) util: Writing file prefs.xml to directory /home/me/.purple
(16:13:18) util: Writing file /home/me/.purple/prefs.xml
(16:13:18) util: Writing file accounts.xml to directory /home/me/.purple
(16:13:18) util: Writing file /home/me/.purple/accounts.xml
(16:13:23) g_log: purple_account_get_bool: assertion 'account != NULL'
failed
(16:13:42) buddyicon: Could not get file info of
(16:13:42) account: Connecting to account my_uname@my_domain/.
(16:13:42) connection: Connecting. gc = 0xb9678da8
(16:13:42) dnssrv: querying SRV record for my_domain:
_xmpp-client._tcp.my_domain
(16:13:42) dnssrv: res_query returned an error
(16:13:42) dnsquery: Performing DNS lookup for my_domain
(16:13:42) dnsquery: IP resolved for my_domain
(16:13:42) proxy: Attempting connection to my_domain
(16:13:42) proxy: Connecting to my_domain:5222 with no proxy
(16:13:42) proxy: Connection in progress
(16:13:42) proxy: Connecting to my_domain:5222.
(16:13:42) proxy: Connected to my_domain:5222.
(16:13:42) jabber: Sending (my_uname@my_domain): ?xml version='1.0' ?
(16:13:42) jabber: Sending (my_uname@my_domain): stream:stream
to='my_domain' xmlns='jabber:client' xmlns:stream='
http://etherx.jabber.org/streams' version='1.0'
(16:13:42) jabber: Recv (428): ?xml version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
from='my_domain' id='70087262-114a-4f64-9e89-969529b866d4' xml:lang='en'
xmlns='jabber:client'stream:featuresauth xmlns='
http://jabber.org/features/iq-auth'/starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanismPLAIN/mechanism/mechanisms/stream:features
(16:13:42) jabber: Sending (my_uname@my_domain): starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/
(16:13:42) jabber: Recv (50): proceed
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/
(16:13:42) nss:
subject=E=root@localhost.localdomain,CN=localhost.localdomain,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
issuer=E=root@localhost.localdomain
,CN=localhost.localdomain,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
(16:13:42) certificate/x509/tls_cached: Starting verify for my_domain
(16:13:42) certificate/x509/tls_cached: Checking for cached cert...
(16:13:42) certificate/x509/tls_cached: ...Found cached cert
(16:13:42) nss/x509: Loading certificate from
/home/me/.purple/certificates/x509/tls_peers/my_domain
(16:13:42) certificate/x509/tls_cached: Peer cert matched cached
(16:13:42) nss/x509: Exporting certificate to
/home/me/.purple/certificates/x509/tls_peers/my_domain
(16:13:42) util: Writing file
/home/me/.purple/certificates/x509/tls_peers/my_domain
(16:13:42) nss: Trusting E=root@localhost.localdomain
,CN=localhost.localdomain,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
(16:13:42) certificate: Successfully verified certificate for my_domain
(16:13:42) jabber: Sending (ssl) (my_uname@my_domain: stream:stream
to='2my_domain' xmlns='jabber:client' xmlns:stream='
http://etherx.jabber.org/streams' version='1.0'
(16:13:42) jabber: Recv (ssl)(377): ?xml version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
from='my_domain' id='7e7c8c82-df9a-4c29-8480-9e5c3648c6e2' xml:lang='en'
xmlns='jabber:client'stream:featuresauth xmlns='
http://jabber.org/features/iq-auth'/mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanismPLAIN/mechanism/mechanisms/stream:features
(16:13:42) sasl: Mechs found: PLAIN
(16:13:42) jabber: Sending (ssl) (my_uname@my_domain): auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga='
http://www.google.com/talk/protocol/auth'
ga:client-uses-full-bind-result='true'password removed/auth
(16:13:42) jabber: Recv (ssl)(167): failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'not-authorized/textUnable to
authorize you with the authentication credentials youapos;ve
sent./text/failure
(16:13:42) connection: Connection error on 0xb9678da8 (reason: 2
description: Not Authorized)
(16:13:42) account: Disconnecting account my_uname@my_domain/ (0xb963c2e0)
(16:13:42) connection: Disconnecting connection 0xb9678da8
(16:13:42) jabber: Sending (ssl) (my_uname@my_domain): /stream:stream
(16:13:42) connection: Destroying connection 0xb9678da8
(16:13:47) util: Writing file accounts.xml to directory /home/me/.purple
(16:13:47) util: Writing file /home/me/.purple/accounts.xml
(16:13:48) util: Writing file blist.xml to directory /home/me/.purple
(16:13:48) util: Writing file /home/me/.purple/blist.xml
(16:13:50) Gtk: Attempting to read the recently used resources file at
`/home/me/.local/share/recently-used.xbel', but the parser failed: Failed
to open file '/home/me/.local/share/recently-used.xbel': Permission 

Re: Pidgin status incorrect

2015-06-04 Thread Mark Riesenberger
Dear Kevin,

I'll check with the Stanford XMPP server managers and let you know.

Sincerely, 


Mark Riesenberger 
Manager, Desktop Computing 
Department of Radiology 
Stanford University 






- Original Message -
From: Kevin Stange ke...@simguy.net
To: Mark Riesenberger sli...@stanford.edu, Support@pidgin.im
Sent: Wednesday, June 3, 2015 10:16:08 PM
Subject: Re: Pidgin status incorrect

On 06/02/2015 03:13 PM, Mark Riesenberger wrote:
 Dear Michael,
 
 All the clients experiencing this issue deny having any other instance of 
 Pidgin running---only one device using Pidgin. What other options? Is there a 
 cache file that I can delete? It's a Windows 7 Ultimate laptop.

Do you know if the XMPP server being used is Openfire?  There is a known
issue which causes exactly the behavior you have described:

https://igniterealtime.org/issues/browse/OF-829

This issue exists in 3.9.2 and 3.9.3, and downgrading the server to
3.9.1 or upgrading it to 3.10.0 is supposed to resolve it.  However,
there is another major problem with 3.10.0 and I wouldn't recommend
upgrading until 3.10.1 is released.

Kevin




___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support