15-11-2012 11:16 - last edited on 16-05-2013 17:19 by Claudius
We have a large deployment of RHEL 6 Clients in place. Skype 4.0 worked fine (with the static version and some library tweaks). Since the 4.1 does not come as a static build anymore there seems to be no way to use Skype in an enterprise Linux environment.
Please provide a build for RHEL 6 (or Centos, or Scientific Linux). Do not let the enterprise linux customers (yes, we have a lot of paying accounts) standing in the rain please.
15-11-2012 20:38 - edited 15-11-2012 20:41
Definitely need something that runs on RHEL6 and variants.
The F16 RPM won't install because it requires:
alsa-lib >= 1.0.23 (only 1.0.22 is available)
The dynamic version crashes with the message "Illegal instruction (core dumped)" on the command line. dmesg shows:
skype trap invalid opcode ip:807c238 sp:ff8edcfc error:0 in skype[8048000+1b5c000]
Some googling seems to indicate that the skype binary was likely compiled with sse3 instructions or something that RHEL6 doesn't support.
17-11-2012 17:15 - edited 17-11-2012 17:33
The Ubuntu 10 skype binary should be compatible with EL6. Extract it from the deb file and and then put it in the "dynamic" version. That probably works.
Edit: No, doesn't work. All dependencies are fullfilled as expected. But it dies immeadiately with a segfault (Null pointer dereferenced.)
Normally, I would say that a programm that is binary-only but does not have a version for RHEL cannot be worth a thing.
17-11-2012 19:50 - edited 17-11-2012 21:31
Ok, here's the "solution":
1) Install the "dynamic" version.
2) Replace the skype binary with the one from the Ubuntu 10 package.
3) Get libQtWebKit.so.4 from some old qt package for el6 and make skype use it via LD_LIBRARY_PATH or whatever.
Correction: It was absent in el6 from the very beginning. I got my version somehow else. 4.6.2-15 from fc12 should do the trick, too.
ad 2) Ubuntu 10 is extremely close to EL6, that binary simply must and really does work.
ad 3) RH dropped QtWebKit in EL6 after originally having it. It's now supplied by epel, but derived from other sources, hence the segfault.
Optional and final step: Look for an alternative to skype if they don't offer a RHEL package in the near future, because after their support for Ubuntu 10 ends, there won't be any tricks anymore. (Did you know? Ubuntu and Skype are partners ...)
17-11-2012 23:09 - edited 18-11-2012 00:25
I wanted to put it all in the thread above, but editing time is now over.
The best source for libQtWebKit.so.4 is most probably Ubuntu 10. If someone has a link to the deb file, please post.
Perhaps we even can come up with a clear step-by-step description. Which in turn should be somewhere else (CentOS Forum or so).
[I'm still very much puzzeled about Skype: Are they really _that_ stupid or are they doing this on purpose? How can I offer a binary-only program without having a package for RHEL? Where do these people live?]
18-11-2012 00:35 - edited 18-11-2012 00:38
... choice "architecture" at bottom of page and download from near to you mirror.
18-11-2012 01:01 - edited 18-11-2012 01:39
That was yesterday. With 4.1, there's no binary that works ootb.
Please calm down. Read at least what has been said so far. "Quick replies" are not needed.
If you want to really help, please post a link to the latest deb (32 bit) in Ubuntu 10 LTS that includes the file "libQtWebKit.so.4". (I already have a version of this file and I know that it works. It's about an official source I can post.)
Final procedure for el6:
1) Start with the "dynamic" version, which for example goes to /usr/local/skype
2) Replace the skype binary in this folder with the one from the Ububtu 10 package.
3) Put a copy of Ubuntu's 'libQtWebKit.so.4" in this folder. You can get the package from here: http://packages.ubuntu.com/lucid-updates/i386/libq
4) move the skype binary to skype.bin and make an executable 'skype' script that contains:
#!/bin/sh export LD_LIBRARY_PATH=/usr/local/skype exec /usr/local/skype/skype.bin --resources=/usr/local/skype "$@"
Extracting files from a deb package goes like this:
$ ar x foo.deb
The files are then in either 'data.tar.gz' or 'data.tar.lzma'.
Thanks! That worked great!
For those who aren't familiar with extracting tar.lzma archives, you can use
# tar --lzma -xvf data.tar.lzma
to extract them. Do the extraction in a temp directory so it's easy to clean up later.
The whle think could probably be scripted...