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.
The errors you see in the screenshot are caused because you started sddm as your own user.
The sddm-qt5 package creates a new user account "sddm" on your system and it will run as that user when you start it from runlevel 4.
There is a possibility that the ownership of files created during its startup are incorrect (since you started it manually, some of these files will be owned by you instead of the "sddm" user).
Try removing all these files and then change your computer to runlevel 4 again. Also, check if the "sddm" user is actually created and if its homedirectory "/var/lib/sddm/" exists and is owned by the "sddm" user.
The errors you see in the screenshot are caused because you started sddm as your own user.
The sddm-qt5 package creates a new user account "sddm" on your system and it will run as that user when you start it from runlevel 4. There is a possibility that the ownership of files created during its startup are incorrect (since you started it manually, some of these files will be owned by you instead of the "sddm" user).
Try removing all these files and then change your computer to runlevel 4 again. Also, check if the "sddm" user is actually created and if its homedirectory "/var/lib/sddm/" exists and is owned by the "sddm" user.
Amazing! Then if I will do something like: "init 4" as "root", from the Linux console, I will (possible) frak-up the system, after installing of the next-gen KDE?
BTW. Shocking news for the new KDE5 users! You have one brand-new user account in your system(s)! When you expected to tell us that?
Last edited by Darth Vader; 02-28-2015 at 05:14 PM.
The errors you see in the screenshot are caused because you started sddm as your own user.
The sddm-qt5 package creates a new user account "sddm" on your system and it will run as that user when you start it from runlevel 4.
There is a possibility that the ownership of files created during its startup are incorrect (since you started it manually, some of these files will be owned by you instead of the "sddm" user).
Try removing all these files and then change your computer to runlevel 4 again. Also, check if the "sddm" user is actually created and if its homedirectory "/var/lib/sddm/" exists and is owned by the "sddm" user.
OK, I didn't quite understand what files should I remove.
I backuped some files like: serverauth, xsession, etc.
Restarted the PC with default init 4 but still nothing. What I get is the same blinking cursor on top left corner.
When you try SDDM in runlevel 4 and the screen stays black with a blinking cursor in the upper left, this is probably caused by a missing homedirectory for the “sddm” user.
Solution: Check the output of command, it should return “/var/lib/sddm” and that directory must exist and be owned by the “sddm” user:
$ getent passwd sddm | awk -F ‘:’ ‘{print $6}’
The getent (...) gives /var/lib/sddm but as this dir doesn't exist ao I created (sddm own and user). Now sddm starts but It freezes.
As always, I read your blog, edited xinit but something incredible stupid is happening here...
Thanks
Last edited by eddygrinder; 03-01-2015 at 05:59 AM.
when i try xdm as opposed to sddm it actually works ! i get an x-window a login prompt as opposed to a non-functional sddm,
Starting up X11 session manager...
and then a bash login prompt.
Although i had to edit /etc/rc.d/rc.4 and comment out:
# Look for SDDM as well:
#if [ -x /usr/bin/sddm ]; then
# exec /usr/bin/sddm
#fi
for it to work. Any ideas on how to get sddm to work right would be great.
More functionality is better. And yeah i added sddm to the video group and also
/var/lib/sddm does exist and is owned by sddm. And yes this is slackware 15.
Last edited by SunnyJim; 05-13-2022 at 11:33 AM.
Reason: spelling error
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.