Installing Skype on Fedora 17

Well, Skype, although it provides and RPM for Fedora 13+, it doesn’t really handle the dependencies very well.

I found I had to install these items seperatly:

yum install -y libXScrnSaver.i686 qt.i686 qt-x11.i686

you might find others though. To find it, do the following:

in terminal as your account, type skype and press enter. If it doesn’t load it will tell you something is missing.

In this example what’s missing is libXss.so.1

To find what has that you run this command:

yum whatprovides */libXss.so.1
It will tell you all the packages which include that file, however as Skype is 32bit, its looking for that library.

So, you tack on .i686 at the end, as above and it should deal with that minor issue.

11 comments

Hilary May 11, 2012 10:43 am

Hi Lee,
I tried your suggestions but ran into errors when using yum, protected multilib versions. Something new in Fedora 17 I think.
Currently Skype is not installable on my system.
Any ideas?

Hilary

lee May 11, 2012 11:56 am

If you could post your full error I’ll certainly take a look for you.

What’s the error when you try to run Skype from a terminal? Also, are you 32bit or 64bit?

Hilary May 11, 2012 5:07 pm

So I tried a post, sorry if this is a duplicate

Thanks Lee.

I’m on 64 bit Fedora 17 beefy beta

I get the same errors when using autoten to install skype or manually with yum,

these are the errors,

Error: Protected multilib versions: libstdc++-4.7.0-4.fc17.i686 != libstdc++-4.7.0-5.fc17.x86_64
Error: Protected multilib versions: libpciaccess-0.13-2.fc17.i686 != libpciaccess-0.13.1-1.fc17.x86_64
Error: Protected multilib versions: mesa-libGL-8.0.2-2.fc17.i686 != mesa-libGL-8.0.2-6.fc17.x86_64
Error: Protected multilib versions: libgcc-4.7.0-4.fc17.i686 != libgcc-4.7.0-5.fc17.x86_64
Error: Protected multilib versions: libxcb-1.8-2.fc17.i686 != libxcb-1.8.1-1.fc17.x86_64
Error: Protected multilib versions: libdrm-2.4.33-1.fc17.i686 != libdrm-2.4.33-2.fc17.x86_64
Error: Protected multilib versions: mesa-libglapi-8.0.2-2.fc17.i686 != mesa-libglapi-8.0.2-6.fc17.x86_64
Error: Protected multilib versions: krb5-libs-1.10-5.fc17.i686 != krb5-libs-1.10-6.fc17.x86_64

Thanks for your help

Hilary

lee May 11, 2012 6:04 pm

Thanks, and what command did you run which produced those errors?

Hilary May 11, 2012 6:38 pm

These errors come from the autoten installation of Skype.

But if I use your yum command above I get similar errors.

Here’s the output from that.

Error: Protected multilib versions: libstdc++-4.7.0-4.fc17.i686 != libstdc++-4.7.0-5.fc17.x86_64
Error: Protected multilib versions: libpciaccess-0.13-2.fc17.i686 != libpciaccess-0.13.1-1.fc17.x86_64
Error: Protected multilib versions: libgcc-4.7.0-4.fc17.i686 != libgcc-4.7.0-5.fc17.x86_64
Error: Protected multilib versions: libxcb-1.8-2.fc17.i686 != libxcb-1.8.1-1.fc17.x86_64
Error: Protected multilib versions: libdrm-2.4.33-1.fc17.i686 != libdrm-2.4.33-2.fc17.x86_64
Error: Protected multilib versions: mesa-libGL-8.0.2-2.fc17.i686 != mesa-libGL-8.0.2-6.fc17.x86_64
Error: Protected multilib versions: mesa-libglapi-8.0.2-2.fc17.i686 != mesa-libglapi-8.0.2-6.fc17.x86_64
Error: Protected multilib versions: krb5-libs-1.10-5.fc17.i686 != krb5-libs-1.10-6.fc17.x86_64

Thanks for your help.

Hilary May 11, 2012 6:51 pm

Well, I solved it by enabling Fedora 17 test updates in the software sources.

Thanks for your help.

lee May 11, 2012 7:05 pm

Glad you got it working.

Cogito Ergosum June 11, 2012 4:28 am

For me with F17/32b on Lenevo X220 I had no issues after the first step [- Download the latest beta from the Skype Website from here (http://www.skype.com/go/getskype-linux-beta-fc10)]\\as per http://www.riccardoriva.com/blog/?p=1275#comment-235

Sully September 12, 2012 9:19 pm

I haven’t had any problems installing skype on fedora 16 or 17. Just went to the website downloaded and installed the latest rpm. The installer handled all the dependencies, no problem.

Lee September 12, 2012 9:32 pm

Unless they have changed the RPM or you’ve installed everything possible, this won’t be the case.

Setup a VM and install using the default options a new Fedora install, then try again.