Anybody got google-talk going?

[jur]

I downloaded the .deb package for google-talk and converted to .tcz using the script by Jason... the files get installed in /opt when loading the tcz.

That aside, has anybody had success getting google-talk to work? It is a plugin like flash10... but I have no idea where to place the files so chromium can find them. /opt seems not to work. The plugins page in chromium is of no help. googling did not turn up any help either.

Help please?

[Jason W]

I copied the plugins to /usr/local/lib/mozilla/plugins and the .so libs to /usr/local/lib, and the executable to /usr/local/bin, but I got an error with unable to get openssl version when I tried to use it.

I am not sure if the source is available, I didn't spend much time on it, but it if was then there is a better chance that it would build and run.

[tinypoodle]

Looks like I got it to load in opera10:

Code: [Select]

Google Talk Plugin

application/googletalk googletalk

/usr/lib/mozilla/plugins/libnpgoogletalk.so
/usr/lib/mozilla/plugins/ needs to be in plugin path

Not that I would have any idea how to use it, and therefore can't test 

[aus9]

hi

I have not tested this either but as I have no programming skills I cheat and use package binutils ...command strings

Code: [Select]

strings GoogleTalkPlugin | grep dev
gnu_dev_major
gnu_dev_minor
Failed to load device options.
input device index, output device index,
and video capture device index,
Failed to get input device index.
Failed to get output device index.
Failed to get video capture device index.
__default_device
getdevicestate
setdevicestate
revertdevicestate
__default_device
Gpu: device-name='
, device-id=
Device manager can't find selected device
session/phone/devicemanager.cc
Can't enumerate devices
Failed to read V4L2 device meta
Enumerating V4L2 devices
V4L2 device metadata found at
Device name not found, defaulting to device path
Plan B. Scanning all video devices in /dev directory
Total V4L2 devices found :
/proc/video/dev/
Found V4L2 capture device
Can't open selected device
No capture device selected; using default
No capture device selected and can't get default
No playback device selected; using default
No playback device selected and can't get default
Unable to retrieve default capture device
Bad capture device number
Unable to retrieve default playback device
Bad playback device number
/dev/urandom
Default device
pa_stream_get_device_index
snd_device_name_hint():
snd_device_name_free_hint():
snd_device_name_free_hint
snd_device_name_get_hint
snd_device_name_hint
  failed to initialize the sound device
  no support for getting number of devices (playout=%d, recording=%d) => _lastError = %d
  cannot get device name => _lastError = %d
  Cannot set devices when soundcard is grabbed (%d, %d) => _lastError = %d
  Cannot set devices => _lastError = %d
  No support for resetting sound device => _lastError = %d
  No support for controlling sound device => _lastError = %d
  output sound device might not be able to play out the input signal correctly
Open of video device %s failed: %d (%s)
/dev/

Inference.....pay attention to your video4linux setup

and pa_stream_get_device_index made me think that maybe pulseaudio is needed?

Code: [Select]

strings GoogleTalkPlugin | grep pulseaudio
sound/pulseaudiosoundsystem.cc
good luck

[tinypoodle]

Its showing up as a process actually:

Code: [Select]

11807 tc       /usr/local/lib/opera/10.10//operapluginwrapper 24 29 /usr/lib/mozilla/plugins/libnpgoogletalk.so


[tinypoodle]

As a test: https://talkgadget.google.com/talkgadget/popout is loading when /usr/lib/mozilla/plugins/ is in plugin path in opera10, but not loading when path is disabled.

[tinypoodle]

Fiddling further with this, after doing ldd on all the executables and libs, I found that despite the plugin was loaded into browser and running as a PID there were missing deps.
In my case libGL.so.1 and libdrm.so.2. Of course that may depend on which packages a user would have installed already anyway.

After installing the deps, when before I was prompted to install the plugin which was already running, I get:

We couldn't detect a proper audio setup. Please ensure your speakers are working and try again.

I suspect that might be due to running OSS instead of alsa.

[hiro]

Have you tried OSS_alsa?

[tinypoodle]

Yes, plus an .asoundrec as suggested in OSS wiki.

[roberts]

Yes. Will be demoing Google Talk it at Scale9x running TinyCore on a Dell mini 9 (portable free phone calls). 

[tinypoodle]

Nice, very interesting subject for a presentation.

roberts, have you tried that with OSS in particular? And if so, to what result?

[jur]

* drool *

What a pity I'm an introverted engineer who doesn't talk, much. 

[roberts]

Two guys at the Tiny Core booth had Tiny Core running on Dell Mini 9. I personally no longer own one.
I did a quick and dirty hack to get Google Talk working on Dell Mini 9 using the following:

1. Xorg-7.5.tcz onboot
2, alsa.tcz onboot
3. alsamixergui.tcz ondemand
4. glew.tcz onboot
5. namoroka.tcz onboot


sudo -s
ar -p google-talkplugin_current_i386.deb data.tar.gz | tar -C / -zx
echo /opt/google/talkplugin/lib >> /etc/ld.so.conf
/sbin/ldconfig
namaroka &

We were able to make free calls while roaming the booth.

If anyone wants to finish this into an extension please do, as I have plenty of tasks awaiting me.

[jls]

google-talk is on the repo