Kuser on current
 

I get the following error

kuser: error while loading shared libraries: libkldap.so.4: cannot open shared object file: No such file or directory

Every thing is up to date.

Thanks

there's no kuser neither a libkldap.so.4 in current (it ships a libKF5Ldap.so.5): that is probably a leftover of a kde 4 installation and cannot work with kde 5.

I see is there an equivalent for kde 5?

You have on System Settings a page named User Manager, where you can edit (or add/remove) unprivileged users.

Just type "user" on the search box of application, and you will find it easily.

There is something called user, but it only appears to add users. It does not even show the users that are already on the system so broken or useless or both, or my installation is borked.

Strange, it does here. You can also delete them. Root password (once per session) is required for deletion and addition of users. The users shown in mine were all added from the CLI, my normally method for user management.

Well if that is the case there is something borked with my installation. Does the obsolete KUser show up for you? It should not be there as it should have been removed when we went from KDE4 to KDE5.

I Will probably nuke the install when 15 is release and go with a clean install. As my Steam OS drive does a kernel panic for some reason now I may format that drive and try a clean install there. SteamOS is dead in the water anyway no updates since 2019. So no reason to keep it around anyway.:rolleyes:

I use the command line to do these things but since I don't need to add or modify users often I have to look it up :redface:

I'm on a up-to-date slackware64-current install, no KUser on my system, that was removed ages ago, before KDE Plasma5 landed in Slackware, when I was using Alien Bob's ktown.

My guess is the fact that it still shows up for me (KUser) has something to do with User not working. :study:

Kuser should not be on your system, it was removed over a year ago when Plasma landed in the main tree.

Read/follow docs.slackware.com current instructions; after an update you have to: slackpkg clean-system.

That sometimes causes problems for me.

Download the ChangeLog.txt in a directory, then execute this command in the same directory.

It will try to remove every package which was previously removed from -current, without touching of course your custom packages.

OR, you can remove them manually, those are the packages removed from -current:

The list of removed packages in UPGRADE.TXT was recently brought up to date as well, so you could use the removal script from that:

Trying to just grep the ChangeLog for removals requires a bit of finesse, otherwise you can end up getting hits on packages that were removed in testing/ or /extra and end up removing (for example) all of the glibc packages. There are also cases where packages were removed in this development cycle but then reintroduced later, so even using a list that's filtered to avoid testing/ and extra/, you'd need to follow it up with an upgradepkg --terse --install-new <all packages> to add back the things that shouldn't have been removed.

This is my script to get a raw list of removals from the main package directory, in case anyone finds it useful:

Thanks that is useful information.

Still can't get users to see anything although it will seemingly let me add a new user. Also on my main test install there is no user manager, there is on my other test box but it also does not see the users that were added from the command line. Strange must have done something wrong at some point.