Issue 435099 in chromium: google-talkplugin libc6 dependency problem on Debian 7 (Wheezy)

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Cr-Internals-Installer Pri-2 Via-Wizard Type-Bug OS-Linux

New issue 435099 by yu210...@gmail.com: google-talkplugin libc6 dependency
problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/39.0.2171.65 Safari/537.36

Steps to reproduce the problem:
1. Download the .deb 64 bit google-talkplugin package from
https://www.google.com/tools/dlpage/hangoutplugin/download.html to a Debian
7 (Wheezy) machine.
2. run dpkg -i /path/to/file/google-talkplugin_current_amd64.deb
3. Look for the output that shows the dependency conflict. "dpkg:
dependency problems prevent configuration of google-talkplugin:
google-talkplugin depends on libc6 (>= 2.14); however:
Version of libc6:amd64 on system is 2.13-38+deb7u6."

What is the expected behavior?
The Hangouts / Talk plugin installs.

What went wrong?
The talk plug in package was configured to require libc6 (>= 2.14) however
the current libc6 version in the current stable release of Debian is based
on 2.13.

Did this work before? Yes About a month ago I'd estimate.

Chrome version: 39.0.2171.65 Channel: stable
OS Version: Debian 7 (Wheezy)
Flash Version: Shockwave Flash 15.0 r0

This is similar to Issue 410805 (http://goo.gl/igPabc) in which a similar
dependency was introduced to the pepper flash plugin.

There are some people talking about this issue here: http://goo.gl/71mqaV

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #2 on issue 435099 by jorge.ar...@gmail.com: google-talkplugin

libc6 dependency problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

Google developers do not respect Debian users. They never did.

[chro...@googlecode.com]

Updates:
Labels: TE-NeedsFurtherTriage

Comment #4 on issue 435099 by hmupp...@chromium.org: google-talkplugin

libc6 dependency problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #5 on issue 435099 by fredd...@gmail.com: google-talkplugin libc6

dependency problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

I have this issue as well. Is there any place to get the old
google-talkplugin? Are there alternatives that will allow me to stay on
Debian stable and use the google-talkplugin?

[chro...@googlecode.com]

Comment #6 on issue 435099 by aepstein...@gmail.com: google-talkplugin

libc6 dependency problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

Does google-talkplugin really need such a recent version of libc? If it
could be built against an early version that is actually in wheezy, and
have the dependency lowered, that would also fix this.

[chro...@googlecode.com]

Comment #7 on issue 435099 by Jim.Lin...@gmail.com: google-talkplugin libc6

dependency problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

This is idiotic. Google is excluding the Talk plugin from the majority of
Linux users. Just another example of how "Don't be evil" was an ironic evil
joke.

[chro...@googlecode.com]

Comment #8 on issue 435099 by da...@sailthru.com: google-talkplugin libc6

dependency problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

Any updates from the team on this one?

[chro...@googlecode.com]

Comment #9 on issue 435099 by louisw...@fastmail.fm: google-talkplugin

libc6 dependency problem on Debian 7 (Wheezy)
https://code.google.com/p/chromium/issues/detail?id=435099

To work around this problem, I installed the 32-bit .deb archives instead
for both Google Chrome and the Google Talk Plugin. For whatever reason, the
32-bit version of the Google Talk Plugin depends on glibc6>=2.7, unlike the
64-bit version which depends on glibc6>=2.14, which is of course
unavailable in Wheezy.

I'm not sure if it is strictly necessary to use 32-bit versions of both the
browser and the plugin -- i.e., it might be possible to run a 32-bit
version of the plugin in a 64-bit version of Chrome.

If you do what I did and install 32-bit versions of both, know that Chrome
depends on a 32-bit version of xdg-utils and, if you already have a 64-bit
version installed (which is very likely), it will be impossible to install
the 32-bit binaries alongside. To get around this, I edited the archive
itself (as root):

# touch /etc/default/google-chrome
# dpkg -x google-chrome-stable_current_i386.deb ./extract-dir/
# dpkg -e google-chrome-stable_current_i386.deb ./extract-dir/DEBIAN/
# sed -i 's/xdg-utils (>= 1\.0\.2), //' ./extract-dir/DEBIAN/control
# dpkg -b ./extract-dir/ google-chrome-stable_modified_i386.deb
# dpkg --install google-chrome-stable_modified_i386.deb

Note that because of the first "touch" command, the package repository will
not be installed automatically. You will need to track Google Chrome
updates and install them manually, using this procedure for each update.
That is, until Jessie is released.