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.
Sorry I fell short. I guess I was used to the Slackware source tree where that tree is used to build the packages and any unused packages don't have their source components available.
I'll try to stay more informed, but it isn't always easy to stay up on everything.
Sorry I fell short. I guess I was used to the Slackware source tree where that tree is used to build the packages and any unused packages don't have their source components available.
I'll try to stay more informed, but it isn't always easy to stay up on everything.
The reaction to your posting was over the top. You have apologised once for somethign that barely required an apology. There is no need to do it again.
Good catch! I didn't look close enough to realize the second wget was hardcoded to the "latest" url. I don't have the ability to generate a diff right now (work computer running Windows and I couldn't find any websites that would generate one for you), but if you change the following line (line number 145):
cd "$REPACKDIR/src"
wget https://repo.skype.com/rpm/stable/skypeforlinux_$VERSION-1.x86_64.rpm
it should work with any versions they have in their repo.
Thanks, didn't know the link for the "stable" rpm archive.
So with a small modification to Ruario's script I was able to download and create packages for versions 8.29.0.50 and 8.30.0.50. There are only a few recent rpms in that archive, so who knows how long the 8.29.0.50 version will be available.
Thanks for making me realize that I should probably do something about skypeforlinux NOW-rather-than-later, regis_n_bits.
I hadn't considered that maybe version 8.29.0.50 might disappear from repo.skype.com ...
In addition to bassmadrigal's patch, I had to set a wget -O flag to replace a '_' with a '-' in the original filename to comply with Slackware-Standard Naming Conventions.
Patch is below my signature.
I upgraded skypeforlinux version 8.18.0.6 with 8.29.0.50 on my Slackware64 14.2 + Multilib system and it works just fine.
Thanks to all !
-- kjh
# diff -Naur latest-skype.sh-orig latest-skype.sh
Code:
--- latest-skype.sh-orig 2018-04-09 07:19:56.000000000 -0500
+++ latest-skype.sh 2018-09-14 14:39:22.230605371 -0500
@@ -127,7 +127,8 @@
install -m 644 "${0}" "$REPACKDIR/src/$SCRIPT"
# Fetch Skype
-wget https://repo.skype.com/latest/skypeforlinux-64.rpm -O "$REPACKDIR/src/skypeforlinux-$VERSION-1.x86_64.rpm"
+cd "$REPACKDIR/src"
+wget https://repo.skype.com/rpm/stable/skypeforlinux_$VERSION-1.x86_64.rpm -O "skypeforlinux-$VERSION-1.x86_64.rpm"
# Now we have all the sources in place, switch to the package directory
# and start setting things up.
No more new Skype releases running on Slackware, because of "systemd sucks" ?
I think the conclusion is either to use old versions of skype for as long as they work, or to try starting the elogind daemon before running a new version of skype and see if that helps. (Since you will probably have an X session running under ConsokeKit at that point, I don't know what the outcome of that will be.)
At first I thought this might be an issue with libappindicator (I have libindicator but not libappindicator and I'm using my own Plasma 5 build). Then I read this thread and decided to test the theory about elogind. I've installed skypeforlinux 8.30.76.41 with elogind 236.1 and 238.1. In both cases Skype works and I have an icon in the Plasma 5 task tray. If I remove elogind, there is a skypeforlinux process running but nothing appears in the task tray. So no systemd drama, just install elogind if you can.
Since compiling elogind requires meson, which requires python 3, it is possible to install this on 14.2 using the SlackBuilds from -current for python3, python-setuptools, python-six etc., re2c from SBo, and then ninja and meson from the -current SlackBuilds. Don't mess around with your python2 packages (esp. if you have 3rd party packages installed), just the new python3 stuff that's been added to -current.
Things might be more interesting if you're using glibc-2.28. I have this installed on my build PC (which is a custom rolling installation somewhere between 14.2 and -current). I get the "redefinition of ‘struct statx’" error if I try to build elogind on this PC but on another with glibc-2.27 both 236.1 and 238.1 build fine.
I think the conclusion is either to use old versions of skype for as long as they work, or to try starting the elogind daemon before running a new version of skype and see if that helps. (Since you will probably have an X session running under ConsokeKit at that point, I don't know what the outcome of that will be.)
So, long story short, we just entered in a hell hole because of the usage of ConsoleKit hack instead of using as everyone, you know what?
Nice!
Last edited by Darth Vader; 09-15-2018 at 05:23 AM.
At first I thought this might be an issue with libappindicator (I have libindicator but not libappindicator and I'm using my own Plasma 5 build). Then I read this thread and decided to test the theory about elogind. I've installed skypeforlinux 8.30.76.41 with elogind 236.1 and 238.1. In both cases Skype works and I have an icon in the Plasma 5 task tray. If I remove elogind, there is a skypeforlinux process running but nothing appears in the task tray. So no systemd drama, just install elogind if you can.
Since compiling elogind requires meson, which requires python 3, it is possible to install this on 14.2 using the SlackBuilds from -current for python3, python-setuptools, python-six etc., re2c from SBo, and then ninja and meson from the -current SlackBuilds. Don't mess around with your python2 packages (esp. if you have 3rd party packages installed), just the new python3 stuff that's been added to -current.
Things might be more interesting if you're using glibc-2.28. I have this installed on my build PC (which is a custom rolling installation somewhere between 14.2 and -current). I get the "redefinition of ‘struct statx’" error if I try to build elogind on this PC but on another with glibc-2.27 both 236.1 and 238.1 build fine.
Then, even the ConsoleKit shipped by slackware-current does not emulate the systemd-logind too?
Last edited by Darth Vader; 09-15-2018 at 05:30 AM.
Then, the ConsoleKit shipped by slackware-current does not emulate the systemd-logind too?
ConsoleKit2 mostly seems to do the job, but you might still need loginctl from elogind if the Plasma 5 lock screen kicks in and you can't unlock it in the GUI and you have to drop to the console to unlock it (say, for example, because you've upgraded Plasma while you're still in the GUI). There is another way out using dbus but it's hacky:
If I remove elogind, there is a skypeforlinux process running but nothing appears in the task tray.
There must be something different about your set-up. If I start skypeforlinux-8.30.76.22 under XFCE with a vanilla slackware64-current SysVinit boot-up, skype aborts after failing to find the org.freedesktop.login1 service, and no process is left running.
Anyway it is good to hear that installing elogind deals with the issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.