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.
Can this topic be marked effectively as solved then? Eric, I've had a look at your blog post regarding elogind but I can't see any leads on how to get it built for Slackware.
Either way, this is a real pain that Skype is doing this.
Can this topic be marked effectively as solved then? Eric, I've had a look at your blog post regarding elogind but I can't see any leads on how to get it built for Slackware.
Either way, this is a real pain that Skype is doing this.
My SlackBuild plus sources for elogind are here: https://slackware.nl/alien-kde/sourc.../deps/elogind/
Note that this dates back to February 2017, in the meantime a newer version is available and I do not know if the patches will still apply and whether new patches are required for Slackware.
Skype worked fine from long time under Linux. I talk about Fedora, RHEL, OpenSUSE, SLED, etc...
The real nuisance was the "PulseAudio sucks" crowd.
So embarrassing that Skype, Inc. does not payed double number of developers, just for some stray "anti-PulseAudio" guys.
no, in 2006 (?) it was nuisance with the shitty looking qt3 (was it 3?) interface that could not integrate with anything. Then the qt4 port came, but hey, no 64 bit. Then there was the pulseaudio thing. Then, hey, no 32 bit, but we have a clumsy web-based interface. Now this.
On Slackware64 14.2 it is working as we speak. The instructions you gave are hard for me to understand BUT I just tried this and tried that until Skype fired up for me. Thanks
EDIT - It works but upon reboot (laptops do that occasionally) I have to amend /usr/share/skypeforlinux again and then sign in to Skype again because it doesn't save my username and password.
Never, ever forget with these here black magic boxes (and Linux especially!); one letter wrong, or missing, and it don't want to know.....
(I've lost track of the number of times I, too, have made this mistake over the last few years...)
I still say the worst moment was when Skype was dragged from its Estonian roots.....and transplanted to American 'soil'. Nothing's been right with it since. And I'm sorry to say this, but yes; PulseAudio does 'suck'.
ALSA roolz! Yus.....
Mike.
Last edited by Mike_Walsh; 09-19-2018 at 06:23 AM.
Looks you ran into a tar bug that has plagued me a lot when developing liveslak: the path "usr/share/skypeforlinux/resources/app.asar.unpacked/node_modules/slimcore/bin/sharing-indicator.node" is exactly 100 characters and it seems that the tar in Slackware 14.2 truncates the last character, only in this particular situation of 100-character filenames.
The tar in -current does not have this bug, which is why I have to generate my Live ISO images on -current.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.