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.
I would like to add to Franklin's comment regarding slow logout and occasional hangup while logging out in sddm. I have been seeing this same issue when choosing to log out back to the sddm screen. When logout hangs up, sddm-auth** and sddm--0:** files remain behind in tmp.
As for causes, I have little to offer. But a few observations; unlike Kde4, graphical login in kd5 has been supplied by sddm. Sddm does not seem to be well tested and integrated compared to prior kde apps. The sddm developers are SystemD** orientated and their work appears to not play well with non-SystemD stuff such as with elogin, pam and other modules. Hence the older version packaged in Slackware.
Sometimes 'fixed' during current updates to KDE, but reappearing once again. Sigh
**I recall an old blog post by Alienbob on his first attempts at creating kde5 packages for current. Issues at the time with sddm not playing well in a non systemD environment. And more telling was the snobby attitude and reply from the sddm developers 'Our SystemD way or the highway' Shades of the Poettering syndrome.
I can confirm that, so far at least, the OP's solution seems to have worked. I know nothing about PAM so I have no idea if there's any downside to this.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
While I don't observe crashes, I am experiencing slow logout issue on the latest Slackware64-current in Plasma.
There is a problem though because I have Slackware64-current installed on the host and as VM client. While host has issue with the slow logout (including shutdown/reboot), VM client does not have this problem. Both systems are identically configured with the exception of simulated hardware in VM of course.
So I don't think that this is going to be a easy fix as it looks like slow logout occurrence is somewhat random.
In my case, I do not use sddm. I boot to runlevel 3 and use startx (as a user, not root) to start the KDE Plasma Desktop. I frequently get slow log outs. When the log out is slow, it almost always results in a hang at this point on logging out:
Code:
startx
xauth: file /home/chris/.serverauth.19603 does not exist
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
Build Operating System: Slackware 15.0 Slackware Linux Project
Current Operating System: Linux racermach.home.arpa 5.13.13 #1 SMP Thu Aug 26 12:49:17 CDT 2021 x86_64
Kernel command line: auto BOOT_IMAGE=Slackware64 ro root=801
Build Date: 30 July 2021 01:10:20PM
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 30 18:10:12 2021
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
No keyboard response, only why to reboot is hard reset (ugly) or log in via ssh from another computer or my cell phone and issue a reboot command.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.