Skypeforlinux Lacks Dependencies, Won’t Update

Home » CentOS » Skypeforlinux Lacks Dependencies, Won’t Update
CentOS 15 Comments

For about a week now yum has tried and failed to update skypeforlinux:

Packages skipped because of dependency problems:
    skypeforlinux-8.10.0.4-1.x86_64 from skype-stable

Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.20)(64bit) for package: skypeforlinux-8.10.0.4-1.x86_64

Is there any resolution to this issue?

15 thoughts on - Skypeforlinux Lacks Dependencies, Won’t Update

  • Thanks for pointing this out, it looks like they removed the newer GLIBCXX requirement that was added for 8.10, possibly due to popular demand?

    Peter

  • Hello,

    Maybe. Unpacking the rpm works, anyway, I never encountered a single binary issue since I use it like that (ordinary use, I probably don’t use that text encoding or whatever submodule which depends on a newer libstdc++).

    Regards,

  • Easy.
    rpm2cpio /path/to/whatever.rpm | cpio -idm

    Probably best to do that in a temporary directory and see what you get. See the cpio manpage for other options.

  • Hello,

    Exactly. One could also install using `rpm -Uvh –nodeps skypeforlinux-64-0.rpm`, that worked too even if NOT solving the dep for uninstalled lib for the specific skype module.

    Regards,

  • The issue here is that the reason it’s a dep is because at least some component of the skype package was built against a libstdc++ that in turn was built against a newer glibc than that provided by CentOS 7. You are playing with fire trying to bypass the dep and install it anyways. You are much better off getting the skype from the insider channel which was built without the newer library requirements. After installing it you can disable the insider repo and then you’ll get newer updates from the stable repo instead (which should hopefully work in the future).

    Peter

  • Hello Peter,

    I think that it’s clear that installing the package that way is potentially unsafe (well, when you know what module may crash, you don’t risk much), is tricky and just a workaround. At the time there was no insider package that fixes it, there was no alternative but this hack. I personally faced no issue at all w/ that workaround and am waiting for the next stable to jump in, I consider the insider one as less reliable.

    Regards,

  • Thanks, I didn’t know about flatpak… even tho it’s in the base repo! 
    I have to admit though, after reading through the flatpak website about it, I still don’t understand how it could overcome the dependency problem with the skypeforlinux update.  Grateful for enlightenment.

  • ken wrote:
    Unrelated comment: I was interested to see that there is a current skype for linux.

    Then I remembered that M$ is scanning skype connections, the same way google scans your gmail emails…..

    mark

  • Please excuse the sidetrack.

    I had to do a Skype-meeting yesterday evening. Some weirdness occurred.

    A background; Have two OEM:s, one at work, one at home. Same hardware, same OS – CentOS 7.4 x64, same repos and both fully updated, same software installed. I believe the chassis differ though(…).

    At work, the rpm from https://www.skype.com/en/get-skype/, refused to install with the same errors as above regarding the libs.

    The Skype Flatpak from https://flathub.org/repo/appstream/com.skype.Client.flatpakref installed just fine and the test call showed no problems, so that’s what I installed at home too.

    The Skype flatpak at home worked beautifully, that is to say for about ten minutes, then the sound (using a Koss SB/45 headset) it started crackling to the point of not being usable anymore. I hung up and reconnected, then sound was fine, for another ten minutes at which point the crackling returned. Checking the sound prefs, I saw that alsa on the app tab had two instances, one stable and one that blinked like crazy, like it was opening and closing a few times a second.

    On a hunch I downloaded the skype for linux rpm from the link above and installed it with yum. No lib errors!
    I started it and gave it a go, and – no crackling whatsoever. In fact it worked as good as it gets IMHO.

    Is there anything that could account for the problem I had?
    I read that the network bandwidth may be a problem, and that five Mbps at a minimum with video is the low mark. At work I sit on a 1 Gbps up/down network. At home I have 100 Mbps up/down. I
    have doubts that the network width was the problem.

    Are flatpaks known to cause odd problems at all?

LEAVE A COMMENT