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?
Maybe try flatpak version? there should be no problems with dependencies there... :)
On Sat, Nov 18, 2017 at 7:02 PM, ken gebser@mousecar.com wrote:
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?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 11/19/2017 12:53 PM, vychytraly . wrote:
Maybe try flatpak version? there should be no problems with dependencies there... :)
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.
On Sat, Nov 18, 2017 at 7:02 PM, ken gebser@mousecar.com wrote:
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?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
ken wrote:
On 11/19/2017 12:53 PM, vychytraly . wrote:
Maybe try flatpak version? there should be no problems with dependencies there... :)
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.
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
-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of ken Sent: den 22 november 2017 20:14 To: centos@centos.org Subject: Re: [CentOS] skypeforlinux lacks dependencies, won't update
On 11/19/2017 12:53 PM, vychytraly . wrote:
Maybe try flatpak version? there should be no problems with
dependencies
there... :)
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.
On Sat, Nov 18, 2017 at 7:02 PM, ken gebser@mousecar.com wrote:
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?
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?
-- //Sorin
Sorry, to be honest I dont have personal experience with skype flatpak so I dont know how does it behave. But I would recommend to report your problems to issues page on skype flatpak github: https://github.com/alexlarsson/skype-app
On Thu, Nov 23, 2017 at 7:49 AM, Sorin Srbu Sorin.Srbu@orgfarm.uu.se wrote:
-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of ken Sent: den 22 november 2017 20:14 To: centos@centos.org Subject: Re: [CentOS] skypeforlinux lacks dependencies, won't update
On 11/19/2017 12:53 PM, vychytraly . wrote:
Maybe try flatpak version? there should be no problems with
dependencies
there... :)
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.
On Sat, Nov 18, 2017 at 7:02 PM, ken gebser@mousecar.com wrote:
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?
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?
-- //Sorin _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 23/11/17 19:49, Sorin Srbu wrote:
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.
I think this was a known issue with Skype 8.10 for linux itself as I noticed it when I was looking for answers to the GLIBCXX dependency issue. It looks like the skype-stable repo just got updated to 8.11.0 which fixes both the dependency issue and the crackling one.
Peter
-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Peter Sent: den 23 november 2017 23:44 To: centos@centos.org Subject: Re: [CentOS] [ot] Skype crackling (was: skypeforlinux lacks dependencies, won't update)
On 23/11/17 19:49, Sorin Srbu wrote:
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.
I think this was a known issue with Skype 8.10 for linux itself as I noticed it when I was looking for answers to the GLIBCXX dependency issue. It looks like the skype-stable repo just got updated to 8.11.0 which fixes both the dependency issue and the crackling one.
Cool, thanks for the heads-up!
Will check this out.
-- //Sorin
Quoting ken gebser@mousecar.com:
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?
There's the unstable version that installs and works: https://www.skype.com/en/insider/
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 20/11/17 11:30, milos.blazevic wrote:
There's the unstable version that installs and works: https://www.skype.com/en/insider/
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,
On Mon, 20 Nov 2017 12:58:21 +1300 Peter peter@pajamian.dhs.org wrote:
On 20/11/17 11:30, milos.blazevic wrote:
There's the unstable version that installs and works: https://www.skype.com/en/insider/
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?
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,
On 11/20/17 03:44, wwp wrote:
Hello,
On Mon, 20 Nov 2017 12:58:21 +1300 Peter peter@pajamian.dhs.org wrote:
On 20/11/17 11:30, milos.blazevic wrote:
There's the unstable version that installs and works: https://www.skype.com/en/insider/
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?
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++).
Please explain "Unpacking the RPM". How is one to do that when there are broken dependencies?
On 11/20/2017 07:13 PM, Mark LaPierre wrote:
On 11/20/17 03:44, wwp wrote:
Hello,
On Mon, 20 Nov 2017 12:58:21 +1300 Peter peter@pajamian.dhs.org wrote:
On 20/11/17 11:30, milos.blazevic wrote:
There's the unstable version that installs and works: https://www.skype.com/en/insider/
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?
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++).
Please explain "Unpacking the RPM". How is one to do that when there are broken dependencies?
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,
On Mon, 20 Nov 2017 19:22:19 -0600 Robert Nichols rnicholsNOSPAM@comcast.net wrote:
On 11/20/2017 07:13 PM, Mark LaPierre wrote:
On 11/20/17 03:44, wwp wrote:
Hello,
On Mon, 20 Nov 2017 12:58:21 +1300 Peter peter@pajamian.dhs.org wrote:
On 20/11/17 11:30, milos.blazevic wrote:
There's the unstable version that installs and works: https://www.skype.com/en/insider/
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?
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++).
Please explain "Unpacking the RPM". How is one to do that when there
are broken dependencies?
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.
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,
On 21/11/17 19:55, wwp wrote:
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++).
Please explain "Unpacking the RPM". How is one to do that when there
are broken dependencies?
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.
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.
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,
On Tue, 21 Nov 2017 20:39:41 +1300 Peter peter@pajamian.dhs.org wrote:
On 21/11/17 19:55, wwp wrote:
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++).
Please explain "Unpacking the RPM". How is one to do that when there
are broken dependencies?
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.
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.
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).
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,
Quoting Peter peter@pajamian.dhs.org:
On 20/11/17 11:30, milos.blazevic wrote:
There's the unstable version that installs and works: https://www.skype.com/en/insider/
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?
Judging by the comments in the original announcement: https://answers.microsoft.com/en-us/skype/forum/skype_linux-skype_startms-sk... I'd say yes.
Sadly, no one from M$/Skype team bothered to point us in the right direction.
Peter _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 21/11/17 02:21, milos.blazevic wrote:
Judging by the comments in the original announcement: https://answers.microsoft.com/en-us/skype/forum/skype_linux-skype_startms-sk... I'd say yes.
Sadly, no one from M$/Skype team bothered to point us in the right direction.
I'm impressed that they listened at all.
Peter
-
ken -
m.roth＠5-cent.us -
Mark LaPierre -
milos.blazevic -
Peter -
Robert Nichols -
Sorin Srbu -
vychytraly . -
wwp