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've been searching the forum after an answer for this. I've just installed Slackware 9.0 in one of my boxes. The installation was way fast and smooth, and so was to use it. The problem is, when I add an user with adduser, this user cannot startx.
There's no problem with root, who can startx without a problem. I've also run xf86config, but it was not much of help. Believing I would need to run xf86config as user would fix, at the end of the configuration I was unable to write to the file (that's ok....).
Question. Do I have to put anything at /home/user to be able to startx? (I'm trying to run KDE, but any desktop would be nice).
This have been discussed loads of times at the forum, but many who got it to work, just said "I figure it out myself, thanks", and don't post how they did it.. (arghhhhh).
Set UID root, any user can run it, but it's as if it's being run by root, so has access to logs, etc/ files and more that a user wouldn't be able to access but are necessary to run X (i'd never heard of it either http://www.linuxquestions.org/questi...threadid=73559 )
Guys thanks a lot for you help. I've finally got it to work. I'm not pretty sure what fixed it (maybe, this is the same reason why many only posted "Thanks, I fixed it".
I've done two things. First I deleted my user, added a new one from kde. I've tried to set UID to 0 (root), but returned me as UID already exists.
I then went to command line again, and did ls -l as suggested. it was only rw-x--x-root. I used the chmod command described above by BigBadPenguin and it change to rwS-x--x-root.
I tried again to run startx, did not work. I've rebooted "ala" winslow and it worked.
If it was the chmod or the kuser, I dunno, but if someone faces the same problem try both.
Thanks again for the help to everybody in this thread. Ufa, for a minute, I almost give up from Slack, first mouse, then keyboard, then monitor, then users... all without a wizard....ghehe... well, up and running. I'm going to format and do everything again till I learn.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.