Google Talk plugin STILL not working

hpp3 · 08-22-2012, 12:13 PM

I know this problem has existed for quite some time, but there's nothing I can find on the internets to actually fix this, and Google has been rather mum about it as far as I can find, so I'm going to try here.

Kernel: 3.1.0-1-amd64, Debian "Wheezy".
Browsers tried: Google Chrome, Chromium, Midori, Firefox, Firefox 64-bit nightly.

So I download the 64-bit .deb from Google, install and open Gmail in a browser.
Hit the "call phone" button and a dial pad opens with a link at the top that says "Please download the voice plugin to make a call."
Funny, didn't I just do that?
Click the link and I get a webpage (http://www.google.com/intl/en/chat/voice/) with a big blue button that says "Try it now".
Click big blue button.
Another page opens with my Gmail and the dialpad that STILL says "Please download the voice plugin..."

Running the browser from a terminal, I get this message:

Code:

 
No bp log location saved, using default.
[000:000] Browser XEmbed support present: 1
[000:000] Browser toolkit is Gtk2.
[000:000] Using Gtk2 toolkit
[000:020] Starting client channel.
[000:020] Warning(clientchannel.cc:435): Unreadable or no port file.  Could not initiate GoogleTalkPlugin connection
[000:031] Warning(clientchannel.cc:410): Could not initiate GoogleTalkPlugin connection
[000:031] GoogleTalkPlugin not running. Starting new process...
[000:031] Warning(optionsfile.cc:47): Load: Could not open file, err=2
[000:031] Warning(pluginutils.cc:260): Failed to get GoogleTalkPlugin path. Trying default.
[000:035] Started GoogleTalkPlugin, path=/opt/google/talkplugin/GoogleTalkPlugin
[000:036] Waiting for GoogleTalkPlugin to start...
[001:110] Attempting to connect to GoogleTalkPlugin...
[001:110] Warning(clientchannel.cc:435): Unreadable or no port file.  Could not initiate GoogleTalkPlugin connection
[001:111] Warning(clientchannel.cc:410): Could not initiate GoogleTalkPlugin connection
[001:112] Waiting for GoogleTalkPlugin to start...
[002:113] Attempting to connect to GoogleTalkPlugin...
[002:114] Warning(clientchannel.cc:435): Unreadable or no port file.  Could not initiate GoogleTalkPlugin connection
[002:115] Warning(clientchannel.cc:410): Could not initiate GoogleTalkPlugin connection
[002:115] Waiting for GoogleTalkPlugin to start...
[003:116] Attempting to connect to GoogleTalkPlugin...
[003:116] Warning(clientchannel.cc:435): Unreadable or no port file.  Could not initiate GoogleTalkPlugin connection
... (repeat last 3 lines ad nauseum)

Any thoughts? Fixes? Links?

sag47 · 08-22-2012, 06:51 PM

Does the GoogleTalk plugin exist in the path /opt/google/talkplugin/GoogleTalkPlugin in which your browser appears to be looking? Try running strace with your browser to get more verbose output on what system calls are attempting to be made. Perhaps, the output in the terminal is misleading compared to what is actually being called in the system.

If you're using firefox an example of strace would be,

Code:

strace firefox

Try reproducing the same steps you provided to get the plugin error with strace. Once you have the output of strace post it in some code tags so I can analyze it.

hpp3 · 08-23-2012, 12:41 AM

I did confirm many times that the executable was indeed in the path where it is looking, and the names are the same.

As far as strace goes, DANG that produces a lot of output. Just opening with 'strace -o strace.txt google-chrome', logging in to gmail and opening the 'call phone' widget and closing creates a 10MB text file.
I searched it through and through, and there's no mention of the directory, or the plugin itself, except for around line 1802:

Code:

readlink("/proc/self/exe", "/opt/google/chrome/chrome", 4096) = 25
access("/opt/google/chrome/libpdf.so", F_OK) = 0
access("/opt/google/chrome/libppGoogleNaClPluginChrome.so", F_OK) = 0
access("/opt/google/chrome/pepper/libppo3dautoplugin.so", F_OK) = -1 ENOENT (No such file or directory)
access("/opt/google/chrome/pepper/libppgoogletalk.so", F_OK) = -1 ENOENT (No such file or directory)
pipe([22, 23])                          = 0
mmap(NULL, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f29b0585000
mprotect(0x7f29b0585000, 4096, PROT_NONE) = 0

The /opt/google/chrome/pepper/ directory doesn't exist, and neither does "libppgoogletalk.so". In fact, according to the output of strace, there are a LOT of files it's looking for, but missing. Although most are from searching for library in default locations before finding it in /usr/lib/ and stuff like that, so probably not of a whole lot of concern there. I could post the entire 10 MB file somewhere if you'd like to take a further look...

EDIT: just for giggles, I symlinked those two files it can't find in the snip above to the similarly-named '/opt/google/talkplugin/libnpgtpo3dautoplugin.so' and '/opt/google/talkplugin/libnpgoogletalk.so', but no dice.

hpp3 · 08-29-2012, 03:19 PM

Apparently, those two files are part of Google's ChromeOS for netbooks, so no love there.
Tried uninstalling, purging, and re-installing, still no dice.
Followed the advice here:
http://productforums.google.com/foru...okVU%5B1-25%5D
My ldd is not reporting any missing dependencies for the 32-bit libpulse library, so still nothing.

This is a bug that has been reported since the Linux release came out in 2010, why has nothing been done?
Does it work for anybody?

th0gz19 · 09-24-2013, 06:40 AM

I just enabled localhost and it's finally working for me.

#ifconfig lo up

raypsi · 11-23-2014, 11:51 AM

After hammering Google search engine for this trouble I found a quaint youtuber that had done it in windoz.

Unbelievable as is seems this youtuber put the plugin on the desktop.

So my challenge was finding the plugin to put it on the desktop.

Now I got Linux Mint 17 I was just hoping the browser works the same in Linux Mint.

Doing a search in file manager and then copied it to desktop.

Bah da bing bah da boom, it works. Totally unbelievable until I saw it wit my own eyes.

I was pushed to do this 'cause my amateur radio, friend, wd8wky, told me it was doable.

So far I've done this on 2 HD's with Linux Mint 17 on them. Three's going to be a charm.

Arcosanti · 11-23-2014, 07:49 PM

Now that is interesting. Never thought to put it on the desktop or the local host thing. For me the only way I've ever gotten it to work was by running the web browser as root. I know not a good thing. Also I have found that the Linux version doesn't seem as stable as the windows version.