View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016054||administration||operations||public||2019-05-04 12:34||2019-06-04 05:15|
|Platform||Toshiba Satellite||OS||centos-release-7-6.1810.2.el7.ce||OS Version||7-6.1810.2|
|Target Version||Fixed in Version|
|Summary||0016054: after update of skypeforlinux.x86_64 0:220.127.116.11-1 skype doesn't start|
|Description||after yum update of skypeforlinux.x86_64 0:18.104.22.168-1 skype doesn't start|
KSysGuard shows that skype has 3 processes but nothing happend.
|Steps To Reproduce||just yum update skypeforlinux|
and start it
|Additional Information||downgrade works fine|
|Tags||No tags attached.|
I experienced same issue .
Downgrade works .
yum downgrade skypeforlinux-22.214.171.124-1.x86_64
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.6.1810 (Core)
I have the same issue. Any (stable / unstable) release after skypeforlinux-126.96.36.199-1.x86_64 fails to run as expected.
If I remember well, I've noticed something like a library issue (that some process related to skypeforlinux failed to start or so...) at one of the first pre-releases after 188.8.131.52-1 (probably managed to find something in some log or so... don't remember details though). With the most recent releases, no indication of what went wrong.
The problem is that even if launched through terminal, initial process is terminated instantly (and, command prompt is back), without any error being reported. Don't have an idea about how to make skype processes to be more verbose or to log issues somewhere. Anyone has an idea about that?
Apparently the new version has been compiled with a newer version of GLIBC (GLIBC_2.18) and CentOS 7 is at GLIBC_2.17.
Source of this info:
I can confirm that versions after skypeforlinux-184.108.40.206-1.x86_64 does not work any more.
Since new version appeared, I had to apply "yum downgrade skypeforlinux" twice to reach skypeforlinux-220.127.116.11-1.x86_64.
Even Skype System Requirements do not show CentOS/RHEL as supported anymore: https://support.skype.com/en/faq/fa10328/what-are-the-system-requirements-for-skype
As @gorano wrote, problem seams to be with newer GLIBC version and Microsoft does not care to support RHEL any more. There is possibility it is connected with Microsofts new ties with Ubuntu or recent stop of support for both Skype Desktop and Skype for Web on Windows XP platform that happened last month.
In any case, I propose for this bug to be marked unfixable,
and to propose that everyone using skype-stable repo apply "yum-config-manager --disable skype-stable" to dissable further hassle.
Maybe Nux can move one copy of skypeforlinux rpm to his repository in case skypeforlinux-18.104.22.168-1.x86_64 is removed from official repo.
|skypeforlinux.x86_64 0:22.214.171.124-1 does not solve the problem we have to downgrade twice to skypeforlinux.x86_64 0:126.96.36.199-1|
|Version 188.8.131.52 fixes this.|
" Version 184.108.40.206 fixes this. "
I can confirm this, Skype 220.127.116.11 loads and works.
It is quite unexpected but nice development.
solved by skypeforlinux-18.104.22.168-1.x86_64
|2019-05-04 12:34||rbr146||New Issue|
|2019-05-05 09:27||pakistan||Note Added: 0034426|
|2019-05-14 16:27||LUTi||Note Added: 0034463|
|2019-05-20 05:40||gorano||Note Added: 0034482|
|2019-05-22 08:00||DrLove73||Note Added: 0034491|
|2019-05-23 05:06||rbr146||Note Added: 0034503|
|2019-06-03 05:19||gorano||Note Added: 0034580|
|2019-06-03 07:50||DrLove73||Note Added: 0034583|
|2019-06-04 05:15||rbr146||Note Added: 0034590|