Prev: Wireless Slackware 13 64 bits
Next: KDE/Gtk and Perhaps X Errors
From: Chick Tower on 25 Feb 2010 22:30
Has anyone else had a problem with the latest upgrade to Pidgin,
v.2.6.5? When I use it on Slackware 12.0, it keeps telling me that my
AIM account has been disabled due to an unexpected response from the
servers. When I downgrade to v.2.6.3, it resumes working just fine. I
haven't tried it on any other versions of Slackware yet, although I plan
to begin using 13.0 in the near future. I also have yet to research
this on the web, but I intend to do so today.
--
Chick Tower

For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
From: Dan C on 25 Feb 2010 23:30
On Fri, 26 Feb 2010 03:30:23 +0000, Chick Tower wrote:

> Has anyone else had a problem with the latest upgrade to Pidgin,
> v.2.6.5? When I use it on Slackware 12.0, it keeps telling me that my
> AIM account has been disabled due to an unexpected response from the
> servers. When I downgrade to v.2.6.3, it resumes working just fine. I
> haven't tried it on any other versions of Slackware yet, although I plan
> to begin using 13.0 in the near future. I also have yet to research
> this on the web, but I intend to do so today.

Yes, I have had exactly the same problem. I have found that if you go
into the account settings and disable the SSL, it will work fine. Not a
great idea if you're worried about anybody snooping on you, but I'm
hoping the next revision will have this resolved.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as Piglet refused to give him some Pooh-tang.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg
From: Dan C on 26 Feb 2010 00:27
On Fri, 26 Feb 2010 04:30:20 +0000, Dan C wrote:

> On Fri, 26 Feb 2010 03:30:23 +0000, Chick Tower wrote:
>
>> Has anyone else had a problem with the latest upgrade to Pidgin,
>> v.2.6.5? When I use it on Slackware 12.0, it keeps telling me that my
>> AIM account has been disabled due to an unexpected response from the
>> servers. When I downgrade to v.2.6.3, it resumes working just fine. I
>> haven't tried it on any other versions of Slackware yet, although I
>> plan to begin using 13.0 in the near future. I also have yet to
>> research this on the web, but I intend to do so today.
>
> Yes, I have had exactly the same problem. I have found that if you go
> into the account settings and disable the SSL, it will work fine. Not a
> great idea if you're worried about anybody snooping on you, but I'm
> hoping the next revision will have this resolved.

It does seem to be a known issue:

http://www.pidgin.im/

Their site says to disable "Use clientLogin", which also works for me, so
I turned SSL back on. I see plenty of bug reports have been made so it
should get fixed.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as Kanga sneezed in his honey pot.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg
From: Chick Tower on 26 Feb 2010 22:47
On 2010-02-26, Dan C <youmustbejoking(a)lan.invalid> wrote:
> It does seem to be a known issue:
>
> http://www.pidgin.im/
>
> Their site says to disable "Use clientLogin", which also works for me, so
> I turned SSL back on. I see plenty of bug reports have been made so it
> should get fixed.

Thanks for the informative replies, Dan. I saw that note on their
website, but, unless 2.6.5 enables it, I already had "Use clientLogin"
disabled. It's easy enough to reinstall it and see.
--
Chick Tower

For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
From: Chick Tower on 1 Mar 2010 22:18
On 2010-02-26, Dan C <youmustbejoking(a)lan.invalid> wrote:
> On Fri, 26 Feb 2010 04:30:20 +0000, Dan C wrote:
> It does seem to be a known issue:
>
> http://www.pidgin.im/
>
> Their site says to disable "Use clientLogin", which also works for me, so
> I turned SSL back on.

When I reinstalled v.2.6.5, it did enable clientLogin and SSL.
Disabling clientLogin did the trick.
--
Chick Tower

For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
 | 
Pages: 1
Prev: Wireless Slackware 13 64 bits
Next: KDE/Gtk and Perhaps X Errors