LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-29-2020, 09:07 PM   #5131
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 654

Rep: Reputation: 129Reputation: 129

librsvg-2.48.5
https://download.gnome.org/sources/l...-2.48.5.tar.xz

vte-0.60.3
https://download.gnome.org/sources/v...-0.60.3.tar.xz
 
Old 05-30-2020, 11:07 AM   #5132
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 247
Blog Entries: 2

Rep: Reputation: 77
Quote:
Originally Posted by allend View Post
The way I read the last few posts, LuckyCyborg is suggesting the replacement of ConsoleKit2 with elogind.
My problem is I find the arguments spurious, being based on edge cases.

Good for you, but is Wayland really ready for the prime time?

Actually, companies and Microsoft are pushing for the adoption of Microsoft Teams as it is more capable with multiplatform support. (I recently built the Linux client from SlackBuilds.org) There is no Linux support for the Skype for Business app that companies use.

Personal computers have generally lacked the hardware to support multiseat.
I think the idea to switch to elogind is a sound one. Most of the nonsystemd distributions have switched to elogind, and Consolekit2 is mostly unmaintained AFAIK. With time the login1 API requirement will likely increase, and software developers prefer to support maintained technologies, hence elogind.

Just my 2 cents. :-)
 
4 members found this post helpful.
Old 05-30-2020, 03:17 PM   #5133
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,253

Rep: Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948Reputation: 4948
Quote:
Originally Posted by aaditya View Post
I think the idea to switch to elogind is a sound one. Most of the nonsystemd distributions have switched to elogind, and Consolekit2 is mostly unmaintained AFAIK. With time the login1 API requirement will likely increase, and software developers prefer to support maintained technologies, hence elogind.

Just my 2 cents. :-)
It does look like the maintainer of ConsoleKit2 has gone mostly MIA. He hasn't had any updates to ConsoleKit2 since Nov 2017 (there's 7 open PRs and 17 open issues) and his github account has mostly quiet since then with 5 commits to xfce related things in 2.5 years. It is unlikely ConsoleKit2 is going to get more features without forking it, but I'm not really sure how feature complete it is with what is needed/desired in Slackware.

Guess we'll have to see how Pat feels about ConsoleKit2 vs elogind. I imagine if he switches to elogind, it'd probably happen when Plasma5 is added.

Last edited by bassmadrigal; 05-30-2020 at 03:19 PM.
 
1 members found this post helpful.
Old 05-30-2020, 05:30 PM   #5134
slalik
Member
 
Registered: Nov 2014
Location: Moscow, Russia
Distribution: Slackware
Posts: 196

Rep: Reputation: 138Reputation: 138
ProFTPD 1.3.6d is released.
 
1 members found this post helpful.
Old 05-31-2020, 04:25 AM   #5135
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 685

Rep: Reputation: 466Reputation: 466Reputation: 466Reputation: 466Reputation: 466
Quote:
Originally Posted by aaditya View Post
I think the idea to switch to elogind is a sound one. Most of the nonsystemd distributions have switched to elogind, and Consolekit2 is mostly unmaintained AFAIK. With time the login1 API requirement will likely increase, and software developers prefer to support maintained technologies, hence elogind.

Just my 2 cents. :-)
In fact, today even the Linux From Scratch offers either elogind or systemd builds for its BLFS ...

http://www.linuxfromscratch.org/blfs/read.html

Last edited by LuckyCyborg; 05-31-2020 at 04:26 AM.
 
1 members found this post helpful.
Old 05-31-2020, 01:42 PM   #5136
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 685

Rep: Reputation: 466Reputation: 466Reputation: 466Reputation: 466Reputation: 466
Quote:
Originally Posted by allend View Post
Good for you, but is Wayland really ready for the prime time?
Looks like that I am able now to really respond to your question, after (more or less) finishing the migration from the ConsoleKit2 to elogind...

So, like you can see in the attached screenshot, the final build of Plasma5 made by Mr. Hameleers with its inconfundible and broken kinfocenter, works quite decently.

Honestly, there are some (small) differences, compared with the the same but "classic" Plasma5 under X11, like there are no thumbnails in the taskbar's popup, Spectacle (the app for taking screenshots) absolutely needs a click for doing its job and probably many others.

BUT, at least for me, the Plasma5 desktop under Wayland is quite usable and I can live with it.

However, to arrive there, I needed to replace the ConsoleKit2 with a custom build of elogind, shameless inspired from kde-elogind (because I wanted also a fully functional Plasma5 under X11) then I needed to customize two other packages, to add the elogind support: polkit and sddm. Mainly, to make the power controls to work again - and they work quite fine.

Probably there would be a need to rebuild some other packages to fully migrate to elogind, but for now I am satisfied by the end result.

Also, please note that little green lemon from system tray - yeah, it is right what you guess: the skypeforlinux, and it works absolutely fine under Wayland.

And this without "silently" adding a broken login1 implementation which blows up what looks being a quite important system from Slackware: the system wide login sessions...
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20200531_204527.jpg
Views:	74
Size:	234.0 KB
ID:	33307  

Last edited by LuckyCyborg; 05-31-2020 at 04:13 PM.
 
4 members found this post helpful.
Old 05-31-2020, 02:28 PM   #5137
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 685

Rep: Reputation: 466Reputation: 466Reputation: 466Reputation: 466Reputation: 466
And there I have a proposal for slackware-current:

Even the elogind is not adopted right now, at least would be very nice if the /etc/rc.d/rc.M would be modified from:
Code:
# Start console-kit-daemon:
if [ -x /etc/rc.d/rc.consolekit ]; then
  /etc/rc.d/rc.consolekit start
fi
to:
Code:
# Start either the console-kit-daemon or elogind-daemon:
if [ -x /etc/rc.d/rc.consolekit ]; then
  /etc/rc.d/rc.consolekit start
elif [ -x /etc/rc.d/rc.elogind ]; then
  /etc/rc.d/rc.elogind start
fi
This way, the ones who likes to switch to elogind for whatever reasons (like playing with, or even using the Wayland) will have a proper init setup, while, as it is obvious, the "orthodox" ConsoleKit2 way will take priority.

Last edited by LuckyCyborg; 05-31-2020 at 03:21 PM.
 
2 members found this post helpful.
Old 05-31-2020, 05:02 PM   #5138
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 654

Rep: Reputation: 129Reputation: 129
Hi, for some reason on my machine the /usr/bin/nspr-config is an empty file. The
sister script /usr/bin/nss-config works normally.

I have mozilla-nss-3.53-x86_64-1 package installed.
 
1 members found this post helpful.
Old 05-31-2020, 05:13 PM   #5139
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 654

Rep: Reputation: 129Reputation: 129
Seem that this line is not picking it up:

Code:
# Install nspr-config:
cat nspr/$(uname -s)*/config/nspr-config | sed -e "s,prefix=/usr/local,prefix=/usr,g" | sed -e "s,libdir=\${exec_prefix}/lib,libdir=\${exec_prefix}/lib${LIBDIRSUFFIX},g" > $PKG/usr/bin/nspr-config
chmod 755 $PKG/usr/bin/nspr-config
 
1 members found this post helpful.
Old 06-01-2020, 05:37 AM   #5140
camerabambai
Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 145

Rep: Reputation: 19
Intel firmware probably is not the latest, the program spectre-meltdown-checker.sh
said
Code:
  * CPU microcode is the latest known available version:  NO  (latest version is 0x26 dated 2019/11/12 according to builtin firmwares DB v147.20200529+i20200427)
 
1 members found this post helpful.
Old 06-01-2020, 05:52 AM   #5141
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,529

Rep: Reputation: Disabled
Quote:
Originally Posted by camerabambai View Post
Intel firmware probably is not the latest, the program spectre-meltdown-checker.sh
said
Code:
  * CPU microcode is the latest known available version:  NO  (latest version is 0x26 dated 2019/11/12 according to builtin firmwares DB v147.20200529+i20200427)
you need intel-microcode from SBo for that (you can also version-bump it to the latest, if you like).
 
1 members found this post helpful.
Old 06-01-2020, 06:23 AM   #5142
ZhaoLin1457
Member
 
Registered: Jan 2018
Posts: 443

Rep: Reputation: 467Reputation: 467Reputation: 467Reputation: 467Reputation: 467
Quote:
Originally Posted by LuckyCyborg View Post
And there I have a proposal for slackware-current:

Even the elogind is not adopted right now, at least would be very nice if the /etc/rc.d/rc.M would be modified from:
Code:
# Start console-kit-daemon:
if [ -x /etc/rc.d/rc.consolekit ]; then
  /etc/rc.d/rc.consolekit start
fi
to:
Code:
# Start either the console-kit-daemon or elogind-daemon:
if [ -x /etc/rc.d/rc.consolekit ]; then
  /etc/rc.d/rc.consolekit start
elif [ -x /etc/rc.d/rc.elogind ]; then
  /etc/rc.d/rc.elogind start
fi
This way, the ones who likes to switch to elogind for whatever reasons (like playing with, or even using the Wayland) will have a proper init setup, while, as it is obvious, the "orthodox" ConsoleKit2 way will take priority.
Well, as from my own experiences, if there is present a login1 service, it will be preferred certainly by Plasma5 and maybe by other things, then I think that the preference should go to elogind.

My rationale is that if the user installed the elogind for playing with Wayland or whatever, and yet the ConsoleKit2 is not uninstalled, even we will start the ConsoleKit2 service, also the elogind service will be started in demand when the applications calls via DBUS for it.

Then, sooner or later we will end with both services up and running. That's why I suggest a logic like this:

Code:
# Start either the elogind or console-kit-daemon:
if [ -x /etc/rc.d/rc.elogind ]; then
  /etc/rc.d/rc.elogind start
elif [ -x /etc/rc.d/rc.consolekit ]; then
  /etc/rc.d/rc.consolekit start
fi
BTW, I think that your Wayland/Plasma5 experiments are worth to have their own thread, where to explain in detail what you did and others to share their further experiences.

For what is worth, like probably many others, I was genuinely surprised to learn that we are basically just at a step away from a decent Wayland desktop, thanks to the amazing efforts made by Mr. Volkerding and Mr. Hameleers regarding the Wayland integration.
 
5 members found this post helpful.
Old 06-01-2020, 07:04 AM   #5143
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,089

Rep: Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900Reputation: 6900
Quote:
Originally Posted by ZhaoLin1457 View Post
For what is worth, like probably many others, I was genuinely surprised to learn that we are basically just at a step away from a decent Wayland desktop, thanks to the amazing efforts made by Mr. Volkerding and Mr. Hameleers regarding the Wayland integration.
Replacing ConsoleKit2 with elogind has been under discussion ever since we discovered that development of ConsoleKit2 had stalled, needed functionality to act as a login1 drop-in replacement has not been added, and my Wayland sessions which worked two/three years ago are now non-functional with all the latest versions of KDE Plasma5 software.
So, between now and adding Plasma5 to Slackware, there's room for all sorts of fun.
 
7 members found this post helpful.
Old 06-01-2020, 07:50 AM   #5144
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware
Posts: 768

Rep: Reputation: 503Reputation: 503Reputation: 503Reputation: 503Reputation: 503Reputation: 503
Quote:
Originally Posted by saxa View Post
Hi, for some reason on my machine the /usr/bin/nspr-config is an empty file. The
sister script /usr/bin/nss-config works normally.

I have mozilla-nss-3.53-x86_64-1 package installed.
Confirmed. Rebuilding the package shows empty /usr/bin/nss-config.
 
Old 06-01-2020, 07:51 AM   #5145
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware
Posts: 768

Rep: Reputation: 503Reputation: 503Reputation: 503Reputation: 503Reputation: 503Reputation: 503
Quote:
Originally Posted by saxa View Post
Seem that this line is not picking it up:

Code:
# Install nspr-config:
cat nspr/$(uname -s)*/config/nspr-config | sed -e "s,prefix=/usr/local,prefix=/usr,g" | sed -e "s,libdir=\${exec_prefix}/lib,libdir=\${exec_prefix}/lib${LIBDIRSUFFIX},g" > $PKG/usr/bin/nspr-config
chmod 755 $PKG/usr/bin/nspr-config
Do you have any hints on how to fix the SlackBuild-script?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:05 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration