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.
/tmp/nss-3.53
cp: -r not specified *; omission of the 'lib/pkgconfig' directory
cp: impossible to evaluate 'lib/libcrmf.a': No file or folder of this type
/tmp/nss-3.53
/tmp/nss-3.53
cat: 'nspr/Linux*/config/nspr-config': No such file or folder
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.
Mr. Hameleers, with all respect, but why we should wait eventually for Plasma5 adoption to have also this eventual replacement of ConsoleKit2 with elogind?
I ask this because from my own experience, a (probably minimalist) migration to elogind of slackware-current (with its native KDE4) is just a matter of replacing the ConsoleKit2 with elogind, rebuilding polkit for elogind support and also rebuilding the kde-workspace.
I know, most likelly the KDE4 believes that it runs under a systemd based system, but it does as usual its tasks, as I tested as KDM autologin to an unprivileged user, as KDM login as root, reboot/shutdown from KDM and as both unprivileged user and root, everything looks working fine.
Right now I post from a box which runs the -current's native KDE4 and elogind, like you can see from the attached screenshot.
Last edited by LuckyCyborg; 06-01-2020 at 02:03 PM.
I found a small error in the bash-4.3.046 package of -current (which was already there in older versions too):
the package provides a "rbash.1.gz" man page, which is faulty (it refers to bash.1 with a
.so bash.1
line, which cannot be found) but the package doesn't create the link for rbash, like
( cd bin ; ln -sf /bin/bash rbash )
Mr. Hameleers, with all respect, but why we should wait eventually for Plasma5 adoption to have also this eventual replacement of ConsoleKit2 with elogind?
He has no control over what is added to -current. If he did, Plasma5 would've been added many years ago. The answer to this question is you *have* to wait until Pat puts it in or continue to use your own builds or someone else's builds.
The ultimate decision on what goes into -current is up to Pat. Pat may be evaluating the potential benefits and repercussions of adding elogind to -current. Maybe this will happen when Plasma5 is introduced, or maybe it won't. If it isn't introduced, then hopefully something can be found for those wanting to use skypeforlinux and Plasma5 together and keep everything working. Maybe that is patching ConsoleKit2 or Plasma5 or maybe something else.
Mr. Hameleers, with all respect, but why we should wait eventually for Plasma5 adoption to have also this eventual replacement of ConsoleKit2 with elogind?
I ask this because from my own experience, a (probably minimalist) migration to elogind of slackware-current (with its native KDE4) is just a matter of replacing the ConsoleKit2 with elogind, rebuilding polkit for elogind support and also rebuilding the kde-workspace.
I know, most likelly the KDE4 believes that it runs under a systemd based system, but it does as usual its tasks, as I tested as KDM autologin to an unprivileged user, as KDM login as root, reboot/shutdown from KDM and as both unprivileged user and root, everything looks working fine.
Right now I post from a box which runs the -current's native KDE4 and elogind, like you can see from the attached screenshot.
Have you tested from runlevel 3, i.e. login on console and "startx" ? How's everything that way?
Do you have any hints on how to fix the SlackBuild-script?
I had no time to try to build it to see whats going wrong, but I suppose is that line not picking up the correct file, as the
nspr-config.in in the sources has the lines needed. I think somebody else already stated that it needs a correct path.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.