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.
I do not believe that Microsoft, Inc. is the one who you should blame in this case...
From what I heard and understand, the today Skype is written in Javascript ran in a specialized web-browser called Electron and which is NODEJS and Chromium based: https://github.com/electron/electron
Specially, if you want to blame someone, enjoy reading those files:
An interesting excerpt from "atom/browser/lib/power_observer_linux.cc":
Code:
// Copyright (c) 2017 GitHub, Inc.
// Use of this source code is governed by the MIT license that can be
// found in the LICENSE file.
#include "atom/browser/lib/power_observer_linux.h"
#include <unistd.h>
#include <uv.h>
#include <iostream>
#include <utility>
#include "base/bind.h"
#include "device/bluetooth/dbus/dbus_thread_manager_linux.h"
namespace {
const char kLogindServiceName[] = "org.freedesktop.login1";
const char kLogindObjectPath[] = "/org/freedesktop/login1";
const char kLogindManagerInterface[] = "org.freedesktop.login1.Manager";
Please note the author company and the year of first implementation on those files.
And of course, how our ConsoleKit2 is a "perfect" implementation of the "login1 API", was just needed that that poor Skype to start using some Power Management features, to hilarity to ensue.
The bad news are that is safe to bet that there are many other Electron-based applications which maybe are "affected" in a way or other, not only this Skype, and does not matter that they are propietary or open source.
I for one, I believe that those forensics over proprietary applications could have been avoided IF the Slackware adopted Elogind from start, as any other "anti-systemd" distribution...
And as more I study this problem, more I am convinced that, unless the ConsoleKit2 is a Slackware project (and we must evangelize it over any existent software with interests on Power and User Management - no matter they are open source or propietary), then unless we must use that ConsoleKit2 at any price, is better for Slackware to switch to Elogind and to kiss goodbye that ConsoleKit2 which no one (excluding us) uses today.
PS. Thanks to @chris.willing for updates - and I attached also an update of my humble tentative of SlackBuild for Elogind (for building on for now -current).
Last edited by Darth Vader; 09-26-2018 at 10:10 AM.
FWIW I prefer our ConsoleKit2 to Elogind; and I hope to not see Elogind any time.
Please, the ConsoleKit2 is not better than (e)logind in any way.
There's no way someone will prefer a partial clone or whatever is, instead of the original.
Unless we introduce there the politics and religious beliefs like "systemd sucks!", when I will raise the following points:
- Has no importance that Elogind is a chunk of systemd (compared with the pure origins ConsoleKit2), because already we use happily another chunk of it: eudev - and both comes from Gentoo hands, at the end of day.
- We need something which is able to support for real that "login1 API", because it is used by the software.
Read: something plug and play, without us to beg of Microsoft or whatever Big Houses to patch their software to support something which no one uses, excluding us.
I am not against or pro ConsoleKit2 - I will not prefer it or unprefer it, really I will do not care about it and completely ignore it, IF it is capable to behave just like (e)logind over DBUS, and that to be at 100%
Last edited by Darth Vader; 09-26-2018 at 11:05 AM.
Please, the ConsoleKit2 is not better than (e)logind in any way.
There's no way someone will prefer a partial clone or whatever is, instead of the original.
Unless we introduce there the politics and religious beliefs like "systemd sucks!", when I will raise the following points:
- Has no importance that Elogind is a chunk of systemd (compared with the pure origins ConsoleKit2), because already we use happily another chunk of it: eudev - and both comes from Gentoo hands, at the end of day.
- We need something which is able to support for real that "login1 API", because it is used by the software.
Read: something plug and play, without us to beg of Microsoft or whatever Big Houses to patch their software to support something which no one uses, excluding us.
I am not against or pro ConsoleKit2 - I will not prefer it or unprefer it, really I will do not care about it and completely ignore it, IF it is capable to behave just like (e)logind over DBUS, and that to be at 100%
I just gave my opinion, which is of course of limited value. Whatever Pat decides I will abide by (within reason and he has never been unreasonable before, in my opinion). I do hope ConsoleKit2 stays, however.
That is not an opinion, its a statement. An opinion would have some relevant reasoning as to why you prefer consolekit2 to elogind. Personally I have neither installed and haven't noticed the difference.
I just gave my opinion, which is of course of limited value. Whatever Pat decides I will abide by (within reason and he has never been unreasonable before, in my opinion). I do hope ConsoleKit2 stays, however.
Even after random proprietary and open source applications will start stopping randomly to work, just like happened with Skype?
Last edited by Darth Vader; 09-26-2018 at 11:21 AM.
That is not an opinion, its a statement. An opinion would have some relevant reasoning as to why you prefer consolekit2 to elogind. Personally I have neither installed and haven't noticed the difference.
heh an opinion and a statement are not mutually exclusive.
Perhaps install Skype on your smartphone? (I am assuming you have a smart phone... not too far fetched an assumption these days )
note: I did not read the entire thread so if this suggestion was made just ignore.
I am afraid that the desktop sharing on smartphones is something reserved exclusively for the sons of Eagle Eyes, then this suggestion is only partial useful.
I am afraid that the desktop sharing on smartphones is something reserved exclusively for the sons of Eagle Eyes, then this suggestion is only partial useful.
Are those people in any way related to the people with bat ears?
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.
Last edited by Darth Vader; 09-26-2018 at 12:04 PM.
You still haven't elaborated on anything, as it is I will be forced to conclude that you don't actually have any points to bring up...
For an opinion to be an opinion one is not required to elaborate -- what you feel forced to conclude is your own business. I thank you for taking the time to share what you think about my opinion.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.