I have to conclude that there is a 99.999999999999999999999999999999999999999999999999% chance that Pat will just absorb Alien's packages for Plasma5; it would make sense since he (Alien) did all the legwork in figuring out the build/dependencies and whatnot. The bigger question, is when will this happen? I theorized that since PAM was yet to be absorbed at the time, maybe that was the main issue, but now that PAM is official in Slackware, I honestly do not know what the hold up is - and unfortunately the radio silence from Pat is causing this uncertainty.

My request is not for the Slackware development team, but for Slackware users. It seems like everyone is putting a lot of pressure on Slackware devs to provide something RIGHT NOW. If it is not ready, there will be silence, until it is fully cooked up. It will be provided for free to Slackware users and community. It is a possibility that there are paying customers who require certain features in 15.0, and that could be part of the delay. It's all speculation at this point, and only further detracting from this thread. Please use this thread for what it is meant for and make a new thread if you want to speculate. :twocents: :hattip:

Fair, but again the issue at hand is also the long silence with regards to Plasma5, and clearly KDE4 is EOL however that hasn't been any further development with regards to what is happening other than Alien's packages. I do not think anyone here is doubting Pat's abilities , and I have no problem waiting for 15.0 when it is ready - this issue right now is that there hasn't been any update with regards to the Plasma5 situation - this is not to be confused imo to wanting something RIGHT NOW, but just maybe a blurb or sign that things are still a go and not stalled.

In README_CRYPT.TXT it says:
But I only see /dev/mapper/lukssdx2 as shown in the attached image. Am I doing something wrong?

*EDIT*: yes, it was me. Sorry for the noise.

Starting from June, ktown replaced ConsoleKit2 with elogind and shipped a modified polkit package. I think this is one of the roadblocks, even more than PAM.
Anyway, we can be patient. I am running ktown and it's running OK (still), so we can afford to wait. I'm grateful to Pat and Eric for their efforts, and I hope the best for both of them. To both of them: take your time!

Permit me to disagree...

I have two boxes which runs the standard -current, with its KDE4 and XFCE, BUT with ConsoleKit replaced (in the past) by my own builds of elogind and polkit, then from KTown (and its polkit companion) and now by my own builds again. And that happens since several months, BEFORE the elogind even to be adopted by KTown.

The reason? To run Skype, which requires a functional systemd-login1 server.

Believe or not, both KDE4 and XFCE (as shipped right now by Mr. Volkerding) works fine with elogind. Who knows, probably they believes that they found systemd, BUT I do not noticed an issue on power management or whatever.

So, I believe that IF the Slackware team wants to replace ConsoleKit2 with elogind, they can do this tomorrow with no issues.

However, there's another software which is dependency of Plasma5, specially in the latest version of Plasma 5.20 about which you guys talk with serenity: Pipewire.

What is Pipewire? I belive that the proper way to describe it is as Pulse Audio/Video.

Did you know what happens when the PulseAudio server crashes? Probably you know that - your computer will become silent.
Did you know what happens when the Pipewire server crashes? Your graphical desktop suddenly disappear and you are sent into text console. It drags everything with it.

That's WHY is astonishing to see that you guys talks with serenity about the fancies of Plasma5 and how it MUST be included in Slackware right now, BUT nobody talks about Pipewire...

Did I said that that Pipewire server is one kind of server which needs to be started after master user logins (as Plasma5 starts) then to be shutdown before the master user logout (as Plasma5 stops) ? How you do this with the BSD/SYSV init system which we have?

Honestly, I would love to see a generic method to handle those "user target" servers in Slackware, without systemd...

PS. This Pipewire is also used now by Chromium for the WebRTC screencasting, then will be no wonder if it will become also a Firefox dependency in the near future.

Hi,

I am using Slackware64-current along with Xfce-4.14 packages provided by rworkman (Thanks Robby!).

With the recent Slackware updates, polkit is at version 0.118 along with mozjs78. These do not work correctly with rworkman's packages - suspend, hibernate does not work, network manager also has issues, etc.

To fix, I downloaded rworkman's polkit Slackbuild (currently at 0.117), used source 0.118 from Slackware current, and rebuilt the package. After that things started working again.

Here is my package (x86_64) for convenience. Thanks for reading.

Using slackware64_current and Fluxbox and trying to use "powerkit" to manage hibernate and suspend/resume, I get the error

(upower:2428):

libupower-glib-WARNING **: 07:44:46.170: Couldn't enumerate devices: Message recipient disconnected from message bus without replying

Powerkit package at /system/powerkit (git-hub slackbuilds by Ponce) used to work.

hi kevmccor, I don't have modified the powerkit SlackBuild at all in my repositoy, it's the same as on SBo...

you can try rebuilding and reinstalling it in your slackware64-current: in case it doesn't help I think your best option is contacting the maintainer on SBo, he's also the author of this tool

https://github.com/rodlie/powerkit

Maybe you did not get the substance of my post. Yes, you may disagree. Yes, whatever setup you might have might work wonderfully. In my system, elogind and PAM works wonders and that might be the case for many people. OK I get that I case you did not understand it.

But still yours and mine are not all Slackware use cases by any means. Thus it is highly probable there are still roadblocks. That was my point.

Command line tool for Wireless - wpa passphrase
 

Will be nice that Slackware comes with a tool for setup wireless connection over command line.
I have attached a suggestion for it that uses a dialog interface.

If you use Network Manager, it comes with nmcli and nmtui, both being CLI interfaces for it.

I used to like wicd and had to switch to nmtui for simple gui to connect to wifi. What is shown could bfit my needs if it was a bit more polished...

last firmware package: kernel-firmware-20200923_afbfb5f-noarch-1.txz, is missing symbol links.

upstream remove them, could be created by copy-firmware.sh.

I remember other user says some similar , recommendation is use the make ...provided.