On May 4 2013 there was a new update for google-chrome-unstable-28.0.1496.0-197749: starting it in konsole I got the error:
- Code: Select all
[vatbier@this chrome]$ /opt/google/chrome/google-chrome
/opt/google/chrome/google-chrome: /lib/i686/libc.so.6: version `GLIBC_2.15' not found (required by /opt/google/chrome/google-chrome)
Mageia 2 has only glibc 2.14 and only in Mageia 3 will there be a higher glibc (glibc 2.17).
- Code: Select all
[vatbier@this chrome]$ ldd /opt/google/chrome/google-chrome
not a dynamic executable
[vatbier@this chrome]$ ldd /opt/google/chrome/chrome
/opt/google/chrome/chrome: /lib/i686/libc.so.6: version `GLIBC_2.15' not found (required by /opt/google/chrome/chrome)
linux-gate.so.1 => (0xffffe000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb2991000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb2988000)
As the previous google-chrome-unstable worked I searched in messages for the previous version:
- Code: Select all
[root@this log]# grep google-chrome /var/log/messages
May 4 19:26:09 this MageiaUpdate[4725]: [RPM] google-chrome-unstable-28.0.1496.0-197749.i386 installed
May 4 19:26:46 this MageiaUpdate[4725]: [RPM] google-chrome-unstable-28.0.1490.2-196983.i386 removed
Much to my dismay googling around I found that google does not keep their old unstable versions available so I couldn't revert to the older version google-chrome-unstable-28.0.1490.2-196983.i386.
It's dangerous to try to upgrade on Mageia 2 glibc and its dependent packages to a higher version of Mageia 3.
Luckily I found a solution:
I downloaded http://tmb2.mine.nu/Mageia/Cauldron/tes ... 2.i586.rpm
(on that site you can also find testing versions of glibc-2.16 and glibc-2.17 for mga3, or download the one of mga3 RC).
I extracted the rpm with Ark and copied the lib directory to a created lib directory in my google-chrome-unstable-28.0.1496.0-197749.i386 directory:
- Code: Select all
[root@this chrome]# pwd
/opt/google/chrome
[root@this chrome]# mkdir lib
[root@this lib]# pwd
/home/vatbier/test/glibc2.15/lib
[root@this glibc2.15]# cp * /opt/google/chrome/lib
[root@this lib]# cd i686/
[root@this i686]# cp * /opt/google/chrome/lib
I let the i686 libraries overwrite the other ones in lib. I didn't test if a created subdirectory i686 in /opt/google/chrome/lib would also work.
Then the latest version as of May 4 google-chrome-unstable-28.0.1496.0-197749.i386 could start!
So far it seems to work except for youtube video's: I noticed that their video and sound play too fast: the voices of people sound a little too high and fast (slightly squeaky voices). Maybe this fault isn't in the 2.16 or 2.17 versions but I didn't try them out yet. For now if I want to see youtube video's I can always fire up chromium-browser.
If your program can not search for a created subdirectory lib (or for Steam libs, see http://steamcommunity.com/app/221410/di ... 1448270483 ) in its installation directory, instead of copying downloaded glibc-2.15 lib directory to /opt/google/chrome/lib ,it also works with LD_LIBRARY_PATH:
- Code: Select all
[vatbier@this chrome]$ LD_LIBRARY_PATH=/home/vatbier/test/glibc2.15/lib /opt/google/chrome/google-chrome
with LD_PRELOAD I think you have to state all used libraries. So the following doesn't work:
- Code: Select all
[vatbier@this chrome]$ LD_PRELOAD=/home/vatbier/test/glibc2.15/lib/i686/libc-2.15.so /opt/google/chrome/google-chrome
Segmentation fault
If LD_LIBRARY_PATH did not work the absolute path to ld-linux.so.2 might be hard-coded into the executable at link time. Then you can try to binary edit the executable using rtldi, see http://stackoverflow.com/questions/8471 ... ingle-host and http://bitwagon.com/rtldi/rtldi.html (I did not try this).
Or in case you want to use the last version of google-chrome-unstable that worked, stop upgrading google-chrome-unstable in the graphical rpmdrake and upgrade it from now on only with the command "urpmi --noclean google-chrome-unstable":
- Code: Select all
urpmi --noclean --auto-select
will download and install all updates that are available on your currently active update resources, and keep a copy in /var/cache/urpmi/rpms; when the download is finished, you can fetch the package files from that directory. Evidently, this does not only work with --auto-select, but also with packages that are explicitely selected.
That way the older versions are kept in /var/cache/urpmi/rpms and if one of the newer versions fail to work like the google-chrome-unstable-28.0.1496.0-197749.i386 you can uninstall it and re-install the older version that still worked.
