So, no more working Skype for Slackware 15? The older versions crash because the new GLIBC, the newer ones needs systemd-logind
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So we don't want our family and friends to be protected from phishing and identity theft or interrupted streams with lousy compression and huge overhead? Sorry I think it important to educate family and friends about what MS is really doing with the Skype data and they gladly switched to WIRE.
Cheers.
I don't want to seem rude, but, I must say, spoken like someone who has limited contacts with run-of-the-mill typical Windows and Mac users. They are not going to leave what they are used to--especially not Mac users trapped in the walled orchard.
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'll use my girl friend for an example. She is a sane and savvy Windows user. She doesn't have problems with viruses and Trojans because she doesn't visit dodgy websites, she runs an AV and a firewall, and she delights in identifying and deleting spammy emails; she has antennae that quiver at the sight of a phish. But after almost a decade, I haven't been able to convert her to Linux because she needs her MSOffice because it's what she knows.
lol lol - you just described my wife (apart from the antennas!!) - she once got hit by clicking on a link that said 'chaze.com' (rather than 'chase.com') - duhhh! I have since (tried to) teach her to mouse-over on a link to see what it actually points to. Probably won't help much ...
I stopped using Skype about the time that Microsoft bought it and not for ideological reasons. Over time it functioned less well on Slackware.
I'm looking forward to Slackware 15.0.
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.
He did sort of:
Quote:
Originally Posted by Darth Vader
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.
And I for one, I consider this being a terrible huge issue, because the Skype is the software which I use to communicate with my family, with my friends, and with my colleagues at work.
Everyone uses Skype, so I should, if I want to communicate with them.
Oh, and that ELOGIND does not compile in Slackware-current in any version released. Apparently the Slackware is so long way away of Gentoo, that's not worth considering that ELOGIND.
I am very disappointed.
elogind-238.1 compiles for me. What errors do you get? (Admittedly I am using PAM but elogind is supposed to compile without it.)
However it won't help you because even the latest (logind) versions of skype crash on start-up with the most recent glibc in slackware-current (glibc-2.28). Given that glibc is not supposed to break ABI on its minor version bumps, that is odd - it isn't supposed to do that.
However it won't help you because even the latest (logind) versions of skype crash on start-up with the most recent glibc in slackware-current (glibc-2.28). Given that glibc is not supposed to break ABI on its minor version bumps, that is odd - it isn't supposed to do that.
Maybe that will quieten down the "why do you want to use Skype" crowd. It seems other apps are affected by the new glibc-2.28 too so better hope your favourite apps aren't included. You could possibly even thank Skype for exhibiting the problem, hence DV for starting discussion here on how to possibly fix it (perhaps along with your favourite app).
elogind-238.1 compiles for me. What errors do you get? (Admittedly I am using PAM but elogind is supposed to compile without it.)
However it won't help you because even the latest (logind) versions of skype crash on start-up with the most recent glibc in slackware-current (glibc-2.28). Given that glibc is not supposed to break ABI on its minor version bumps, that is odd - it isn't supposed to do that.
Ah, the good news is that the latest recompilation of skype (version 8.31.76.88) fixes the problem with glibc-2.28. So you need to get elogind working. What compilation error are you getting?
The only problem I have experienced with elogind is that running it can stop xfce's shutdown/reboot options working correctly, possibly because it interferes with ConsoleKit, so it is best to start it in the skypeforlinux script and stop it when skype is closed.
Ah, the good news is that the latest recompilation of skype (version 8.31.76.88) fixes the problem with glibc-2.28. So you need to get elogind working. What compilation error are you getting?
ninja -C build
ninja: Entering directory `build'
[1/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o
ccache cc -Isrc/libelogind/src@libelogind@@elogind@sta -Isrc/libelogind -I../src/libelogind -Isrc/basic -I../src/basic -Isrc/shared -I../src/shared -Isrc/systemd -I../src/systemd -Isrc/login -I../src/login -Isrc/core -I../src/core -I../src/libelogind/sd-bus -I../src/libelogind/sd-id128 -Isrc/sleep -I../src/sleep -Isrc/update-utmp -I../src/update-utmp -I. -I../ -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -fPIC -pthread -fvisibility=default -MD -MQ 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -MF 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o.d' -o 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -c ../src/libelogind/sd-bus/bus-error.c
In file included from ../src/basic/util.h:47,
from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1387:8: error: redefinition of ‘struct statx_timestamp’
struct statx_timestamp {
^~~~~~~~~~~~~~~
In file included from /usr/include/sys/stat.h:446,
from ../src/basic/util.h:38,
from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:25:8: note: originally defined here
struct statx_timestamp
^~~~~~~~~~~~~~~
In file included from ../src/basic/util.h:47,
from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1392:8: error: redefinition of ‘struct statx’
struct statx {
^~~~~
In file included from /usr/include/sys/stat.h:446,
from ../src/basic/util.h:38,
from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:36:8: note: originally defined here
struct statx
^~~~~
[2/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o
Quote:
Originally Posted by chrisVV
The only problem I have experienced with elogind is that running it can stop xfce's shutdown/reboot options working correctly, possibly because it interferes with ConsoleKit, so it is best to start it in the skypeforlinux script and stop it when skype is closed.
I believe that the issue of ELOGIND is bigger than this and our Dutch Overlord stopped his experiments with elogind for Plasma5 for a very reason:
The systemd-logind (hence the elogind) is a evolution of ConsoleKit which we use today even in -current, and offer a similar functionality as basis.
Then you cannot use them simultaneous, because they will step on each other shoes.
The real issue with Slackware looks like is that we are stuck from whatever reasons on this "old" ConsoleKit which apparently is about of being abandoned.
Reverting to GLIBC 2.27 will be only a temporary solution.
I am intelligent enough to see that is not worth a campaign "pro-2.27", because sooner or later that last "non-logind" Skype will stop working becoming obsolete.
Last edited by Darth Vader; 09-23-2018 at 11:09 PM.
Reverting to GLIBC 2.27 will be only a temporary solution.
I am intelligent enough to see that is not worth a campaign "pro-2.27", because sooner or later that last "non-logind" Skype will stop working becoming obsolete.
What is your solution? Replace Consolekit with Elogind or install the software which shall not be named?
Latest skype running in a -current VM with elogind (patched as per previous post) running in background.
For elogind to run, I had to make a symlink in /run to /var/run/dbus because elogind looks for /run/dbus/system_bus_socket at startup. Maybe that's a location that can be set at build time but the symlink works well enough for now.
Yep, 'find src/ -type f |xargs grep run\/dbus' gives:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
