Okay thanks a lot for the quick + informative reply, Eion!
It would be great to post the solution or the workaround in this list
once it becomes known, so everybody can avail it promptly.
For my part, as mentionned in my post, I did a clean install of
Pidgin+plugins, whereby I flushed
Hi Cedric,
The Google servers made a change as of a day or two ago and no one's yet
worked out what url we should be using for auth now.
Unfortunately the bitbucket tracker for the plugin is offline due to spam
problems, but if you keep an eye on
https://github.com/tdryer/hangups/issues/260
Hello,
I have spent almost 6 hours trying to learn more on my issue with Hangouts.
It seems that quite a few users on the Google "Support" Forums, have the
same access token authorization problem with Google, when trying to
enable the Hangouts account from the Pidgin client.
Curiously, there
On 31-08-2016 05:10, Eion Robb wrote:
It is added to the Pidgin code, but Pidgin 3 is not yet released.
On 31 August 2016 at 14:49, >
wrote:
I was under the impression that the patch was already added to Pidgin.
Is there any compelling
Context: Pidgin 2.10.9 installed in 64 bit Ubuntu 14.04.4 (kernel
3.16.0-50-generic #67 - Unity desktop) with following plugins:
- purple-hangouts
- pidgin-twitter
- telegram-purple
- purple-skypeweb
After a complete re-install and reconfiguration of Pidgin with Skype and
Telegram,
//Hello Eion,
At boot time today, Pidgin launches and crashes immediately afterwards.
Again
It seemed to have stabilized yesterday after disabling the encryption
plugin by removing /usr/lib/pidgin/encrypt.so.
It gets messier by the day, so I am now purging all so I may start again
with a
It is added to the Pidgin code, but Pidgin 3 is not yet released.
On 31 August 2016 at 14:49, wrote:
>
> I was under the impression that the patch was already added to Pidgin.
> Is there any compelling reason not to add it?
>
> Can you please provide a patched versions for