what around , make the new config files ..

or try

Yeaaah, with this Plasma 5 Slackware 15.0 will be released in a couple more years.

xwmconfig doesn't work. There is no xinitrc file for kde.

No .new files were found.

The plasma-workspace package is supposed to include the xinitrc.kde file. Can you try reinstalling that one?

Thanks for the suggestion. I'll try it Friday morning.

Does exist? That is what is being called by .xinitrc to start Plasma 5.

Granted, I'm kind of under the weather due to vaccine, but did you just reinstall the old KDE? in your list, it looks like some things didn't get updated properly. I'd try removing KDE again, then doing an "install-new." It should pick up everything that was added when plasma was added to current. There's a few packages it needs that kde 4.12/4.13 didn't.

You forgot 'slackpkg clean-system'.

1 members found this post helpful.

That only removes the current kde packages, not the old ones you should get rid of.

This is probably irrelevant but from my own experience I find it worth pointing out:

Are you sure you have enough disk space?

I was once in a situation where I installed Slacware -current seemingly successfully, but I wasn't able to log in to KDE afterwards. I was puzzled, but about about half an hour later I figured out that my disk was completely full (it was a 15 GB partition, more than enough for Slackware 14.2 but -current requires 20GB+).

Thanks for your reply but as I mentioned earlier startplasma-x11 does not exist.

Thanks for your reply. I think I'll try this next.

Thanks for your reply. I have 789GB of free space. That should be enough.

I have spent considerable time screwing up slackpkg and slackpkgplus on multiple systems on multiple boxes. It's not hard to do, especially when along with numerous massive upgrades to the system, slackpkg and slackpkgplus get often upgraded as well and many .new files must be dealt with.

My suggestion is to first make certain slackpkg is in perfect order for what you want to accomplish. Ideally compare any leftover .new and .orig files in /etc/slackpkg and read each .conf file completely and carefully. Make certain your preferences match your chosen preference hierarchy, mirror and MIRRORPLUS if you're using slackpkgplus. It is especially important to make certain multilib is properly chosen if you want multilib.

Then, check /var/log/packages for any kde4 files as well as ConsoleKit which should be replaced by elogind. One of those will need to exist but not both. Ideally if you are comfortable with the risk and time for fixing back, you can simply rename any kde4 packages and ConsoleKit IF you also have Plasma 5 files, sddm, elogind, etc. OR if you are a serious gambler and handy with chroot, you can manually remove those packages or do "slackpkg clean-system" but it is wise to thoroughly review what will be "cleaned" and uncheck those you wish to keep.

After certainty exists with slackpkg and the major conflicts have been stalled or removed, update and upgrade-all should function properly.

BTW do you use "startx" or a variant like "startxfce4" or did you rely on "kdm" with the "chooser"?

Note that once Plasma5 is completely installed kdm will no longer exist being replaced by "sddm". Default sddm.conf is supposed to switch from minimumVT of 1 to minimumVT of 7 but it doesn't on some machines especially if you launch sddm as root. That requires a manual Alt-F7 if you get a black screen or appear to be dropped back to CLI. Apparently it prefers autologin to Desktop.

Slackpkg is a really decent tool but it is by no means trivial to set it up right, maintain it through upgrades, and does have a substantial learning curve given how powerfully it can affect one's system(s). Be thorough.