So, no more working Skype for Slackware 15? The older versions crash because the new GLIBC, the newer ones needs systemd-logind

abga · 09-22-2018, 11:06 PM

Quote:

Originally Posted by frankbell

Face it, we persons here at LQ are geeks who love taking computers and operating systems apart and putting them back together.

We are not typical.

I was just suggesting Darth to switch from that corporate backed thingy to something more secure/simple/reliable, without being able to help him with his actual concerns. Sorry, I'm using Skype only when I'm forced to (corporate).

I'm just wondering how small the minority of those typical users is, that are still messaging on desktops computers these days...
https://signal.org/
"Fast, simple, secure.
Privacy that fits in your pocket.

Android
iPhone
Desktop
"

Gordie · 09-22-2018, 11:52 PM

Quote:

Originally Posted by garpu

https://www.linuxquestions.org/quest...ng-4175638207/ Were any of these solutions of help?

There was only really one solution in that 5 page thread and it works after a fashion on both 14.2 and current.
I have it working but it is sorta crippled

john2x · 09-23-2018, 12:04 AM

So far I've been able to get away with using Skype on my Android device exclusively. Fortunately I don't need it for work, otherwise I'd be out of luck if I needed to do screen sharing on my laptop.

Melke · 09-23-2018, 02:39 AM

I'm still using Skype on Slackware... admittedly I am using flatpak for Skype.. but it works

https://slackbuilds.org/repository/1...search=flatpak

with this repo
https://flathub.org/apps/details/com.skype.Client

Kr
Melke

chris.willing · 09-23-2018, 06:35 AM

Quote:

Originally Posted by Melke

I'm still using Skype on Slackware... admittedly I am using flatpak for Skype.. but it works

https://slackbuilds.org/repository/1...search=flatpak

with this repo
https://flathub.org/apps/details/com.skype.Client

Kr
Melke

At the moment, the Skype version in the linked flatpak is 8.29.0.50 - same as in SBo at the moment and which works fine here too. However the problem as described in skypeforlinux-latest-update-not-working-417563820 is actually with version 8.30.0.50. It'll be interesting to see if the flatpak still works when it's upgraded to 8.30.0.50 and beyond.

chris

Darth Vader · 09-23-2018, 06:56 AM

BTW, the Skype 8.29.0.50 crashes (with segfault) after the update for GLIBC in -current. And any available previous version behaves the same.

Code:

[10720.907849] skypeforlinux[22734]: segfault at ab6fd0 ip 0000000000ab6fd0 sp 00007ffc8a1f1138 error 15 in skypeforlinux[200000+160b000]
[10720.907866] Code: f7 01 2f 26 86 30 1f 06 03 55 1d 23 04 18 30 16 80 14 4e 0b ef 1a a4 40 5b a5 17 69 87 30 ca 34 68 43 d0 41 ae f2 30 66 06 08 <2b> 06 01 05 05 07 01 01 04 5a 30 58 30 27 06 08 2b 06 01 05 05 07

That's on dmesg.

So, right now on -current does not work natively any Skype release.

bodqhrohro · 09-23-2018, 07:42 AM

Doesn't https://web.skype.com satisfy you?

bodqhrohro · 09-23-2018, 07:46 AM

Quote:

Originally Posted by Darth Vader

BTW, the Skype 8.29.0.50 crashes (with segfault) after the update for GLIBC in -current. And any available previous version behaves the same.

Code:

[10720.907849] skypeforlinux[22734]: segfault at ab6fd0 ip 0000000000ab6fd0 sp 00007ffc8a1f1138 error 15 in skypeforlinux[200000+160b000]
[10720.907866] Code: f7 01 2f 26 86 30 1f 06 03 55 1d 23 04 18 30 16 80 14 4e 0b ef 1a a4 40 5b a5 17 69 87 30 ca 34 68 43 d0 41 ae f2 30 66 06 08 <2b> 06 01 05 05 07 01 01 04 5a 30 58 30 27 06 08 2b 06 01 05 05 07

That's on dmesg.

So, right now on -current does not work natively any Skype release.

What CPU do you have? The 8.x client is known to be built with some newer instructions support, like sse and ssse and probably some others. So it won't start on old CPUs that lack such instructions, regardless of OS/distro.

Gordie · 09-23-2018, 07:56 AM

Debian - Well you are happy at least. Skype works on Debian and Red Hat. This is a Slackware Forum and the thread concerns Skype not working on Slackware

Darth Vader · 09-23-2018, 07:59 AM

Quote:

Originally Posted by bodqhrohro

What CPU do you have? The 8.x client is known to be built with some newer instructions support, like sse and ssse and probably some others. So it won't start on old CPUs that lack such instructions, regardless of OS/distro.

Excuse me? Now an AMD Phenom x4 9650 at 2.3GHz is obsolete?

AND, the same Skype release worked fine before upgrading the GLIBC to 2.28 on Slackware-current.

interndan · 09-23-2018, 08:40 AM

Try reverting to an earlier GLIBC for a while. You are talking about -current. Sometimes things break on -current. That is why it isn't recommended for production machines.

Darth Vader · 09-23-2018, 08:46 AM

Quote:

Originally Posted by interndan

Try reverting to an earlier GLIBC for a while. You are talking about -current. Sometimes things break on -current. That is why it isn't recommended for production machines.

Thank you, I considered that already.

AND, no dot worry, I do not use -current in production machine.

Unless we consider a production machine my test-machine with solely purpose is me to play with Plasma5...

Like I say in thread's title, I am worried about what will happen on the next-to-be Slackware 15.

garpu · 09-23-2018, 08:49 AM

Quote:

Originally Posted by Darth Vader

Like I say in thread's title, I am worried about what will happen on the next-to-be Slackware 15.

Something will likely be figured out. There are many clever people here.

Darth Vader · 09-23-2018, 09:03 AM

Quote:

Originally Posted by garpu

Something will likely be figured out. There are many clever people here.

Everyone knows already what should be done to avoid those kinds of problems.

BUT that thing will not be done, because of a bunch of guys loves to play fundamentalists.

khronosschoty · 09-23-2018, 09:35 AM

Quote:

Originally Posted by Darth Vader

Everyone knows already what should be done to avoid those kinds of problems.

BUT that thing will not be done, because of a bunch of guys loves to play fundamentalists.

What should be done (?), please spell it out! I'm sitting here imagining that you are saying that, "everyone knows we should adopt systemd", and other things like that.