Skype is a popular platform that is used by millions of people for Text, Audio or Video-based communications. It allows you to call your friends and family at affordable prices. Skype offers desktop versions for almost all platforms including Linux.
However, Skype issues aren’t new and the latest Skype for Linux patch is the latest to cause more problems. People who are running Skype on CentOS systems are now reporting that the latest update broke the messaging app.
Some Skype users confirmed that the issue started affecting their systems soon after the installation of the latest version, resulting in the inability to use the application. The OP wrote on Microsoft support forum:
“The latest version skypeforlinux.x86_64 0:188.8.131.52-1 completely broke it and it doesn’t work any more. Any hint on how to continue using it is very much welcome. We have several working stations where this is required.”
The Problem Continues On Ubuntu
Notably, Skype only supports the 64-bit versions of some Linux distributions including Ubuntu 14.04+, Debian 8.0+, OpenSUSE 13.3+, and Fedora Linux 24+. The Microsoft support team advised the users to switch to any of the supported versions:
“Skype may have worked with your CentOS 7 before, however, please be advised that it is not supported. With this being said, we won’t be able to guarantee that it will work with Skype all the time. We suggest for you to use another supported device or use a Linux with a Version / Distribution that would meet Skype’s requirements.”
Until now, the problem was only reported by CentOS users from all over the world. But now users are experiencing the same problem with the latest Skype build on Ubuntu as well. Someone who installed Ubuntu 14.04 confirmed that even though the package was installed right away, it still broke the Instant Messaging app.
For some users, the issue was temporarily resolved by downgrading the package to a previous version. Most likely, the issue is specifically related to a buggy build rather than the platform.
The Redmond giant is yet to respond to the issue. We will update this article as soon as Microsoft provides details on this matter.