I have tested this on four separate installs of Slackware64 full install after the December 12th updated.

I can log into a Plasma ( not Wayland ) session, all operates as expected. When I click on Log Out, after a few seconds, I see the loading screen appear as if Plasma is re-loading, and I am not logged out.

I am a long time XFCE user, however, I wanted to give KDE another try.

If I hit Ctrl + Alt + backspace, killing the xserver, I can thn log into XFCE, and all is normal there. I can log out of XFCE without any problem.

My questions, how to diagnose? I did switch to TTY2, loged in as user, and ran 'ps aux | grep kde' after the failure, and saw KDEinit process running, after the log out.

For the record, I ran: slackpkg update, slackpkg install-new, slackpkg upgrade-all, and slackpkg clean-system.

I rsync the slackware-tree to one system and upgrade from there.

The other irregularity I remember, was after the initial upgrade, I could not log into XFCE, I had to run xwmconfig to get access. Not sure if that is related of not.

Any one else see behaviour like this?

Are you logging in via console and then running "startx". That's what I do here and "loggin out" of KDE drops me to a console prompt as usual, and the KDE5 shutdown and reboot work as expected.

Also, from the console, xwmconfig is required to select your DE (KDE5 is the default) before you run startx.

2 members found this post helpful.

No, I booting into run level 4. I have not tried starting at run level 3. I'll give it a go, and report back.

Just did another fresh install this morning using a -current.iso dated 12 December.
It takes 16-17 seconds to be returned to the prompt once "logout" has been selected and confirmed from within kde-5.

I changed inittab to 3 and booted the system. I can run startx, and can run KDE normally. When I log out, it drops me back for tty I logged into, no KDE restart like I see in run level 4.

I'm wondering if SDDM has something to do with it? No idea what to look for.

1 members found this post helpful.

There have been lots of new config files with major changes that need to be dropped into place in order for things to work. Is it possible you have a bunch of .new files in /etc that have not had crucial changes merged in, if not just fully replacing the old config files?

1 members found this post helpful.

Am having the same problem here as well. And I always use runlevel 3

1 members found this post helpful.

Ditto.

Just checked for .new files, there are no .new files.

The problem is now resolved with the Dec 15th update to SDDM.

Thank-you Pat.

2 members found this post helpful.

After the aforementioned updates, it still took 10 to 12 seconds to get back to the command line.

Yes, me too, however it does logout as expected. This is why I marked it solved.

1 members found this post helpful.