Skype dies with segfault

[Anonymous]

I noticed there is a skype repo in the repositories list and installed skypeforlinux, but when I run it, I get a segmentationfault. It crashed before the Skype window even appears.

33.955994] skypeforlinux[3608]: segfault at 8 ip 00007f4d5c666500 sp 00007fffa1c52d78 error 4 in libdbus-1.so.3.14.15[7f4d5c64d000+4d000]
[ 2341.066600] skypeforlinux[15943]: segfault at 8 ip 00007f1fe451b500 sp 00007ffe59257288 error 4 in libdbus-1.so.3.14.15[7f1fe4502000+4d000]
[ 2385.299769] skypeforlinux[16218]: segfault at 8 ip 00007faf2369c500 sp 00007ffda6bbdde8 error 4 in libdbus-1.so.3.14.15[7faf23683000+4d000]
[ 2401.449501] skypeforlinux[16369]: segfault at 8 ip 00007f2b7c40a500 sp 00007ffc65bb2558 error 4 in libdbus-1.so.3.14.15[7f2b7c3f1000+4d000]
[ 2617.349256] skypeforlinux[17895]: segfault at 8 ip 00007f8e004b8500 sp 00007ffc5890b3f8 error 4 in libdbus-1.so.3.14.15[7f8e0049f000+4d000]
[ 3109.336591] skypeforlinux[21049]: segfault at 8 ip 00007fb76f8a0500 sp 00007ffc6cfda018 error 4 in libdbus-1.so.3.14.15[7fb76f887000+4d000]
[ 3214.880588] skypeforlinux[21604]: segfault at 8 ip 00007f91a683a500 sp 00007ffdd39fae88 error 4 in libdbus-1.so.3.14.15[7f91a6821000+4d000]
[ 3869.005743] skypeforlinux[25812]: segfault at 8 ip 00007f27c373d500 sp 00007ffc642834a8 error 4 in libdbus-1.so.3.14.15[7f27c3724000+4d000]
[ 4527.576716] skypeforlinux[30380]: segfault at 8 ip 00007f482b310500 sp 00007ffe0460dab8 error 4 in libdbus-1.so.3.14.15[7f482b2f7000+4d000]

Has anyone else had similar issues? I did a little bit of research on this and it appears quite a complicated issue. It seems MS may have introduced some systemd elements, which would be a problem for AntiX. It looks like this is a dbus issue, which I have no idea how to tackle. If anyone has any suggestions, I’d be happy to hear them.

[Anonymous]

Helpful

Up

0

::

I’m not a skype user. I have read that skype (recent versions) is used successfully in MX Linux but same skype version fails under antiX.
You might need to install
libappindicator-gtk3
(if absent from the skype declared list of dependent packages, it wouldn’t have been automatically installed.)

there is a skype repo in the repositories list

???
On my system, nothing found when I checked
grep ‘skype’ /etc/apt/sources.list.d/*

Do you mean you found+installed skype by using the packageinstaller utility?
gksu packageinstaller
( aka “antiX ControlCenter }} System tab }} Package Installer” )

MS may have introduced some systemd elements, which would be a problem for AntiX.

The ldd utility might be enlightening here. If the program name is, literally, skypeforlinux:
ldd skypeforlinux | grep ‘systemd’

[Anonymous]

Helpful

Up

0

::

skidoo

Anonymous wrote:

I’m not a skype user. I have read that skype (recent versions) is used successfully in MX Linux but same skype version fails under antiX.

That pretty much sums it up.

I had https://repo.skype.com/deb in my repositories list. I must have added it at some point but forgot. At any rate, I installed Skype using Synaptic and also tried downloading the deb package from https://www.skype.com/en/get-skype/ and installing with dpkg but both get the same segfault in the end.

ldd skypeforlinux | grep ‘systemd’ returns ldd: ./skypeforlinux: No such file or directory
Not sure why that is, as skypeforlinux is definitely the name of the actual program.

Perhaps I can find an older version that worked and install that.

[Anonymous]

Helpful

Up

0

::

Not sure why that is

The command “ldd skypeforlinux” presumes the executable resides in a known $PATH directory
vs
The command “ldd ./skypeforlinux” presumes the executable resides in the cwd (current working directory)

[Anonymous]

Helpful

Up

0

::

Okay. I ran the same command in /usr/bin/ and there was no output at all.

[Anonymous]

Helpful

Up

0

::

The no output result implies the program isn’t using (linking) any systemd libraries.
If so, you would just need to figure out the “missing ingredient”, the package(s) installed in MX but absent from antiX. In case you’re motivated to do so, here’s a rough howto:

v—– note: the forum software sometimes MANGLES the text. The following looks correct in proofreading (should be “minus minus get minus selections”) but might copy/paste as loongdash blahblah

dpkg --get-selections >> /tmp/list_of_installed_packages.txt
run that on each system. Copy and rename the text files (e.g. mx.txt and antix.txt) then
comm -1 -3 mx.txt antix.txt >> pkgs_only_in_antix.txt
comm -2 -3 mx.txt antix.txt >> pkgs_only_in_mx.txt

If you send the content of those 2 “only_in” files to pastebin.com
and provide the pastebin links, I and others could help you whittle down list to identify the likely “missing ingredient” package.

[Anonymous]

Helpful

Up

0

::

That’s mighty kind of you, skidoo. I’d like to take you up on that offer if that’s okay. Here are the pastebin links:

Only in AntiX: https://pastebin.com/q8gwj0fh
Only in MX: https://pastebin.com/i3q36j9V

If you need any further info, just let me know! Thanks a million.

[Anonymous]

Helpful

Up

0

::

Skidoo: I thought I had good news to report . . . I followed the instructions on this site and lo and behold it installed and opened . . . I tried logging in a few times, but every time I got “unable to connect”. Turns out it’s version 4.3, which is no longer supported . . . hence the inability to connect. Back to the drawing board.

[Author]

Posts