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.
installed my system as root.. everything works (kde3, sound, eth0 etc.)
i created another user with 'kuser' with a home dir, a shell and all.. if i try a 'startx' when i'm logged in as the user.. then i'm not allowed access because of something to do with Xauthority and not being able to write to my home dir.
what have i done wrong.. seeing as i used 'kuser' and added everything.. i rebooted but that didn't work..
what is THE way to add a user and have everything work short of adding the new user to every single group..
thanks slackers,
andy
ps.
i'm impressed with slackware as it's the only distro i can get to play nicely with the wintel nightmare that is the n1015v evo laptop from compaq/hp
I've never had a problem when I use the "adduser" script. Also, you might look at just changing the permissions on the home directory:
chown -R user.users /home/user
Where user is the username AND users is actually kept as users (being the group your users should belong to). If you wish to add this user to more groups, then open up /etc/group and add the name (comma seperated, no space).
There shouldn't be too many groups you need to add a normal user to.
thanks a lot.. i can successfully login now but if i try to edit a test .txt file i can open vim no problem add my text, but when i :wq it comes up with
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Now i tried a "export DISPLAY=:0.0" but that didn't work.. however the test.txt file has been written and does come up in the list when i do a ls.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
maybe your permissions on /tmp are weird.
i've had to do stuff like that, but i can't remember
what all i had to do, but i remember something usefull
find . -type f -exec chown user {} \;
find . -type d -exec chown user {} \;
okay.. even though i was getting that wierd msg when logged in as root.. but su'ing to another user.. i fired up kuser and added my user to sys (for the sound), wheel (i assumed correctly was wheel mouse) and voila.. everything just worked when i logged all the way out and then only logged in with my user.
i think that if you are logged in as root it must protect the xserver somehow and not let other xsessions be started. security feature? anyway on slackware 8.1 you need to add ur user to sys if you want full playin-niceness within kde!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.