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 just installed Slack 9, and everthing went pretty well so far. the problem is i can <startx> as root, but when i change to a user, i get a weird error over and over, with a pause each time:
xauth: timeout in locking authority file //.Xauthority
if i hit control + c a couple times it will get out of that and log into KDE. but then KDE stops right away and can't load because it says it doesn't have write access to $HOME directory (/).
i control+alt+bkspaced and (not really understanding file permissions yet, so just taking a guess) did this:
# chmod +rwx /home
i guess that was wrong, though, because it didn't work.
how come i can't startx as a user? i thought when i made the user linux set up a home directory with all the /home permissions and everything set for it automatically? anyone have any ideas as to what i need to do to get X working as user?
Originally posted by Azmeen Good God, what have you done...
?? was it totally wrong? i just reasoned that the error message said it couldn't write to the home directory, so i thought i was changing the permission so it could read, write and execute from there (+rwx) ? no?
anyway, there is nothing in the /home directory except an empty /ftp and /lost+found directory, so i thought it was no big deal. but that is confusing to me, also, b/c i thought a /home/<USER> directory should have been created when i added the user. ? (edit to add: $ cd <backspace> returns the user to /, not to /home/<user> as it does on my red hat box. as i said, there isn't even a /<user> directory in /home, just /ftp and /l+f. did i forget to switch on an option when setting up the user? )
i changed it back as you suggested, and followed the chown step, but it still does not work. this time it seems to hang w/out doing anything, and then after ctrl+c it says:
cat: //.Xauthority: No such file or directory.
i haven't done anything else except: stock installation, xf86config, useradd, and startx. actually i added the user before xf86config, but xf86config would not run as the user, so i switched back to root to run it. was that wrong?
thanks for your help so far.
Last edited by synaptical; 07-11-2003 at 09:32 PM.
?? was it totally wrong? i just reasoned that the error message said it couldn't write to the home directory, so i thought i was changing the permission so it could read, write and execute from there (+rwx) ? no?
It's not actually wrong, it's more towards dangerous. Why? Because then *anybody* can write/modify/execute files in /home.
You should use adduser instead to create accounts. The script will automate everything regarding user management including creation of home directory.
It's interesting that after creating a user, you don't have a <user> dir in /home. Do you have a separate partition/drive that is mounted as /home? If so, try umount'ing /home, then cd to /home and see if the <user> dir is there. If that's the case, then you'll have to copy/move that <user> dir elsewhere, then re-mount /home, and finally copy/move the <user> dir to /home. I suspect that somehow your /home partition was unmounted when you created the user account.
Originally posted by Cerbere It's interesting that after creating a user, you don't have a <user> dir in /home. Do you have a separate partition/drive that is mounted as /home? If so, try umount'ing /home, then cd to /home and see if the <user> dir is there. If that's the case, then you'll have to copy/move that <user> dir elsewhere, then re-mount /home, and finally copy/move the <user> dir to /home. I suspect that somehow your /home partition was unmounted when you created the user account. Enjoy!
--- Cerbere
thanks! i did not need to unmount the /home directory (which is on its own partition, btw), but it turns out slack was creating the user directory and Desktop in /root. (??) i just moved it all to /home and everything is working now. a few minor things like font adjustments and getting my mouse wheel working and i will be good to go. and thanks also for the tips, Azmeen.
it's not really a big deal at this point, but if anyone would care to take the time to explain why slack is creating the user folders in /root, i would appreciate it. i installed everything by default (~2GB) just to get slack up and running, but after checking it out i plan to start over with a custom install, and i would like to understand what might be going on with that. tia.
xauth: timeout in locking authority file //.Xauthority
ok in your user home, you should have a file called ".Xautority".
The file should be read-write only to your user and be owned by your user and the group users.
to make sure it works, you can also remove the file so your XServer will create a new one. You probably only has a slight right problem.
When I added my user I ended up with one file in my home directory. Looking in /etc/skel, there was just that one file. So I guess Slack wants you to fill out /etc/skel as admin or just do your own files once you get your user account going. Though if user is correctly configured, the various apps will dump their various config files in the right places. Mostly.
As far as why it's writing files to /root, it sounds like you're logged in as root. I have no idea why it would do it otherwise, so that's pretty weird.
And how'd you get a lost+found dir in home?
Oh. My brain finally clicked through what Cerbere was saying. Yeah, if you had your /home directory unmounted at any point, there'd be nowhere to write to, so your account would get screwed. And how did you add that account, anyway? Might try creating another account and seeing if the same stuff happens.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.