You believe wrong

Agreed. Can we please get this thread back on topic? As a long-time Slacker I'm happy that KDE5 has made it into the -current branch. Let us talk about KDE-plasma.

1 members found this post helpful.

Maybe you can ask me to explain then. Are you asking?

What I use is totally irrelevant. I've used and have an installation of Slackel, does that count? But I could be using winXP, does this change the fact that the latest upstream stable version of KDE/plasma works without systemd and elogind?

One of Slackware's fanboys is making a false statement and I am correcting the record. This is LinuxQuestions it is not Slackware's private club! And poor slackware is nowhere blamed here for anything, it is one fool believing in things that are not right. That's all. He, or anyone else can just admit on the error of the statement and it will all be over.

INSTEAD, to defend the LIAR you are trying to say I am attacking Slackware for its choices and its justifications. I am not, you are simply using Slackware as a shield to cover up on a lie!

Now, do you understand? Or is this too complicated for you and I need to break it down in simpler statements?

For what it's worth, anyone that was running ktown already knows that Plasma (X11) runs on ConsoleKit2, because it only switched to elogind quite recently, so there's nothing much to discuss there.

@FungalNet, relax

OK, I got it.

SO, this is your personal Crusade against the infidel LuckyCyborg, who dared to claim that "he believes" that Plasma5 does not well without (e)logind. If this is his personal opinion expressed as Slackware user, what's your problem? He's just a Slackware user.

But, I understand that Plasma5 will not work with Wayland without (e)logind, at least in Slackware, as bigger names like Mr. Hameleers says.

Out of semantics, if Plasma5 works only with Xorg and will not work with Wayland, while having ConsoleKit2 instead of elogind or systemd, isn't a "not working well" ?

After all, the Plasma5 used to work well in the past with ConsoleKit2, even in Wayland. Until a certain time, when it does not worked anymore.

Actually this is a subforum of Linux Questions devoted to Slackware
HTH
John

4 members found this post helpful.

All we need now is someone to come here and make the atrocious remark that the latest wayland works without systemd's logind !

Imagine that!

At some point this fork may escalate into a subject of remote graphical access to the desktop.

What does that even mean in your perception, that behind closed doors we "slackare users" can lie about other software and nobody can dare challenge our lies?

The Slackware users talks about their experiences with Slackware, not with Oberan. And I do not exclude that the software behavior to be different on different distributions, depending in how the distro developers patch the things.

Good for them if they patched Plasma5 to work fully with ConsoleKit2, but in Slackware it will work only in the Xorg sessions without elogind.

1 members found this post helpful.

About what fork you talk? About Slackware?

Yeah, I heard that Slackware is a fork of SLS Linux, but this thing happened 20 years ago. Or 22?

1 members found this post helpful.

No, I was referring to a fork of the discussion, plasma5 --> elogind, plasma5+wayland --> elogind, wayland --> elogind

But it is worth something this "fork of the discussion" ?

After all, elogind was created as a fork of logind from systemd, exactly to avoid the inclusion of systemd, just like is the eudev.

Anyway, other than yelling, arguing and insulting people here, you do not presented yet any arguments that the latest and unpatched KDE Plasma5 release can still work fully with ConsoleKit2 under Slackware.

And by "fully working" I understand to work both on X11 and Wayland sessions.

3 members found this post helpful.

Just a basic correction of your assumptions about this forum This is a forum devoted to Slackware
HTH
John

2 members found this post helpful.

If I remember right, this happened around 2 years ago, when they started also to hard-coded prefer the logind against ConsoleKit2.

The most visible was that that login1 shim service shipped by Skype package started to lock the power management on Plasma5 - this on X11 sessions.

1 members found this post helpful.

My favorite desktop is Plasma5 under Wayland. Both in Slackware and Ubuntu - in fact Kubuntu.

Yes, I do not care about systemd, instead I care exclusively about the operating systems which I like and I have no issues to use also distros who ships systemd. Honestly, I have also boxes with openSUSE Tumbleweed, which works so well, that I never needed to make a single post in their forums.

As someone who built hundred times the Plasma5 on Slackware, trying different software combinations and spending uncounted nights to make Wayland/Plasma5 to work in Slackware, this is my sincere belief: the Plasma5 does not work well without elogind, because the Wayland/Plasma5 does not even start with ConsoleKit2 and I say this from my very own experience. And I do not want to limit myself at x11 sessions only for love of ideology.

And excuse me, but I cannot care less about your war on systemd if it conflicts with my needs.

I am neither pro-systemd or anti-systemd - I do not care about it and I am rather pro myself and pro my own needs.

And you known what? I am very happy that Slackware adopted elogind, because this way works also Skype, a software which I use daily.

3 members found this post helpful.