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.
With regards to dovecot, I've gone through the config changes in the latest dovecot update... Am I right to presume that only the changes in "auth-system.conf.ext" are required to PAM-ify it? Specifically it seems driver = pam was added, and some passdb and shadow lines are commented out now.
I've upgraded and only replaced auth-system.config.ext and everything seems fine, but just want to make sure I'm not missing anything else that is important.
With regards to dovecot, I've gone through the config changes in the latest dovecot update... Am I right to presume that only the changes in "auth-system.conf.ext" are required to PAM-ify it? Specifically it seems driver = pam was added, and some passdb and shadow lines are commented out now.
I've upgraded and only replaced auth-system.config.ext and everything seems fine, but just want to make sure I'm not missing anything else that is important.
Did you remove PAM, Cracklib from CSB and forgot to reinstall the packages from Slackware?
it works fine here on my vm
Well ok to clarify, I just installed all the packages from csb, I didn't do anything different - did not remove cracklib or things like that sorry for that confusion. All I know is when I finished installing CSB it broke the system .
Quote:
Originally Posted by willysr
Pushed a new set of binaries compiled against latest update in -current per today's update.
So I am curious were you able to replicate my issue by installing all CSB as is?
Weird, I do not know then..... Maybe MATE and CSB conflict. Try installing both , if still nothing happens then I have no idea what the issue could be.
I haven't tried it, so I don't know if it's what you're looking for, but hopefully it's not too little too late.
It didn't work, but I sure thank you for the effort. I'm not sure, but I think that plasma-workspace needs to be rebuilt for support of this. But I'm afraid that support would also allow configuring an autologin for root. I understand why AlienBob would not support this, and that's not what I want. I'm just getting old and lazy. Typing a freaking password is not THAT big a deal........
Looking into how other distros (Arch, debian) dealt with autologin and sddm (KDE5), I could suggest the following modifications to make KDE5 autologin work on Current.
Be aware that I'm only just starting to understand PAM. So try at your own risk.
As root, do the following changes:
Change Autologin section in /etc/sddm.conf
Code:
[Autologin]
# Whether sddm should automatically log back into sessions when they exit
Relogin=false
# Name of session file for autologin session (if empty try last logged in)
Session=plasma.desktop
# Username for autologin session
User=<your username>
Create file /etc/pam.d/sddm-autologin with content:
I used to be a signal officer in the US Army. If I remember correctly, NATO countries also used the same standard.
Over means that you are done speaking and expect a reply from the distant station. Out means that you are done speaking and do not expect a reply from the distant station.
There is no Autologin section in /etc/sddm.conf
In /etc/sddm.conf.d there is a file called kde_settings.conf with an Autologin section. I changed that to reflect the above changes. I tried adding that section to sddm.conf but no go.
There is an /etc/pam.d/sddm-autologin with nearly the same entries as what you have. I have made these changes while making sure that I keep the originals. In every case, I end up at a blank screen with mouse and cursor visible for over 10 minutes before I do a hard reboot. I'm gonna keep trying - something is missing..... I hate not being able to figure this out. I ain't giving up yet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.