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

qunying · 09-26-2018, 04:06 PM

As the standalone one does not work properly. There is skype for web https://web.skype.com. It is still beta, but at least it works for my limited use. It is said that using Edge or Chrome will support Video/Audio calls, I did not try that, but at least at Chrome under Slackware, the Audio call button is clickable, on firefox it is dimmed.

jakedp · 09-26-2018, 05:58 PM

Quote:

Originally Posted by RadicalDreamer

He did sort of:

This is a campaign against GLIBC 2.28+.

With him it is always a campaign. He should be working for a an organization that gathers it' s food by playing the moral high ground.

Alien Bob · 09-26-2018, 06:04 PM

Quote:

Originally Posted by Darth Vader

Even after random proprietary and open source applications will start stopping randomly to work, just like happened with Skype?

Closed-source applications that stop - go creating bug reports and hope for the best.
Open source applications? We will write a patch that amounts to "s/login1/ConsoleKit/g" and also ask the developer to add support for more than just the systemd implementation of the logind API.
Stop whining and start filing those bugs.

chris.willing · 09-26-2018, 06:08 PM

A second patch (to correct location of dbus/system_bus_socket for Slackware) has been accepted i.e. the next elogind release is now "Slackware-ready" and won't need any patching at all.

Until then, the attached diff of that commit applies OK to elogind-238.1 too.

chris

jakedp · 09-26-2018, 06:14 PM

Quote:

Originally Posted by Darth Vader

I managed to put together the patches published by @chris.willing for elogind-238.1 (many thanks!) and shameless borrowing the w41l's build for elogind from there https://github.com/w41l/kde-elogind/elogind adapted by me to the current meson build.

The resulted SlackBuild is attached to this post, and generates a elogind-238.1 package, which apparently works correctly and is able to bring up the support needed by skypeforlinux_8.31.76.88, which is able to work on GLIBC 2.28, as shown in the attached screenshot.

BUT, like I said in a previous post, installing Elogind along with ConsoleKit2 you obtain two distinct systems which try to handle the user login sessions, and very possibly to step on each other shoes.

Not fully tested, but looks like the Eric's Plasma5 5.13.5 still manage to execute the power and logout actions even with both of those systems installed.

However, I strongly believe that this story clearly demonstrate that the ConsoleKit2 should be gone and it replaced by at least Elogind.

Why I say that ConsoleKit should be gone?

Because it is clear for me that it is obsolete. Software evolved, and needs features which aren't offered by ConsoleKit. And I guess there are many other applications which suffer by that lack, not only Skype.

However, in this weekend, which I spent experimenting around Skype and DBUS services for users login sessions I observed that the other few distributions proud to be "systemd-free" in fact they use at least three barbarian chopped chunks of systemd: eudev, elogind and systemd-timedated1 (which probably replaces ntp and/or ntpdate).

Yep, the "systemd-free" thing looks like have the sense for them as not using it as init system.

That make to ask myself: IF we must use huge chunks of systemd to satisfy the requirements of the today software, why we should stay ourselves as minions of Gentoo and at their caprices, when we can just use our own machete at build time to chop off the init system part from that systemd, which apparently is what its hatters hate?

That's why I said "at least Elogind"

Anyways, I believe that in a way or other we should kiss goodbye to ConsoleKit2, if we want Slackware to be compatible with the today Linux software.

PS. To have a imagine about what is adapting Plasma5 to elogind you can take a look there: https://github.com/w41l/kde-elogind

However, it is very possible that this implementation to be not actual, because it is about Plasma5 5.10.4, and the today Plasma5 5.13.5 may have a much better support for elogind.

I have a better option. Chop the offending software. There is very little free software that does not have good citizen alternatives.

There is very good reasons to keep away from systemd and none of them are ideological. I will list them:

1) generates more heat
2) uses more RAM
3) uses more CPU cycles
4) corporate embrace and extend tendencies
5) you can change the timeout but we have seen the watchdog process fail to reboot or shutdown the machine because a process is still running that systemd decides should be still running although you the user said to reboot or shutdown the damn machine
6) ties to 5, there is many little barely noticeable instances where systemd decides against what the user said or intends, it is an egotist in control of your machine and thinks it knows better than you
6) slower boot and shutdown in many intances
7) has that nasty windows habit of slowing down the more the OS is used (time scale), the longer systemd is installed the more it seems the machine slows down, this is my subjective opinion
8) Pottering is an asshole, like me, but I do not like him - this is totally irrelevant
9) back to point 8, systemd makes stable and time tested software irrelevant for no reason, it is an asshole
10) the biggest is that it limits choice, we all migrated or use Linux for choice and many other reasons but choice to me is more important than any technical consideration, the limiting of software choice leads to lower quality of technical quality in software

jakedp · 09-26-2018, 06:22 PM

Quote:

Originally Posted by Darth Vader

Well, in the Romanian folklore, Mr. Eagle Eyes is an (imaginary?) Native American, with an exceptionally good sighting. A character probably "imported" from some Western movie, as Romanians was always huge lovers of this genre.

"You are the son of Eagle Eyes!" has the sense of "You have an exceptional good sighting!"

In a similar way,

"You have bat ears!" has the sense of "You have an exceptional good hearing!" (like a bat)

Both of those expressions has no negative connotations. They are purposely and purely appreciative. And there is no relation between them from what I known.

Not imported by movies, it is an old term/mythology across Europe back too Classical Greek times. That is at least 2, 500 years old...

If a person only heard of it from movies then the movie just kept a piece of old wisdom from literature alive. :-)

Darth Vader · 09-27-2018, 01:54 AM

Quote: