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 updated my Slackware current installation today and upon rebooting, KDM would not display. This is because I overwrote config files. I logged in as root and edited my default runlevel from 3 to 4 in /etc/inittab. Now when I reboot all I see when I should see KDM is a black screen with a gray rectangle on it that is my cursor and in the top left corner is a blinking horizontal line like where you'd type but I can't do anything else.
An update: I tried switching to SLiM and realize the problem is with xorg. I can't even manually start my DEs and WMs. When SLiM tries to launch it repeatedly throws errors then says x1 is respawning too fast and disables it. I have no idea how xorg works or how to fix this.
Last edited by borkerofsystems; 02-14-2020 at 09:52 PM.
Thank you. I updated mesa and changed my default runlevel back to 4 and was able to get SLiM and KDM to work and can once again use my computer. I should've known since I'm running current that it was possibly a buggy updated package that messed up my system before I started messing with it.
You and I, both, borkerofsystems, are going to have some work cut out for us if an when Plasma 5 becomes the default. As much as I like the improvement in KDE I don' like SDDM nearly as much as KDM and mostly because I depend on "Console Login (Alt+N)" that doesn't exist as an option in any other login/display manager of which I'm aware. I suppose there just aren't that many people left who boot to CLI AND use a display manager as opposed to simple startx or booting directly to desktop
I don' like SDDM nearly as much as KDM and mostly because I depend on "Console Login (Alt+N)" that doesn't exist as an option in any other login/display manager of which I'm aware.
I don't understand what you mean here. With SDDM, you can still Ctrl-Alt-F1 to a console if you need that.
I don't understand what you mean here. With SDDM, you can still Ctrl-Alt-F1 to a console if you need that.
I know that of course Alien Bob, but it is not at all the same. Ctrl-Alt-F1 does not take one back to the original login console but to a new one. KDM's "Console Login (Alt-N) does. I realize that isn't a huge difference but in a few operations it does matter, at least to me. I'd love to know how to add that option to SDDM since there is no option I know of to continue using KDM that I've grown used to, but so far I haven't discovered the command that "Alt+N" invoked. How do I do that?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.