[SOLVED] Access denied to home desktop fldr when downloading pkgs in SW13.0/kde
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.
Access denied to home desktop fldr when downloading pkgs in SW13.0/kde
Since 7pm using FF3.5x repeated attempts at downloading pkgs for install from adobe,slackbuilds and sourcforge after clicking download and save to /home/user/Downloads gives me nothing downloaded-no download window opens showing progress. Doing same with Konqueror gives me "access denied" to that folder when I choose save pkg there.
If I switch to Arch on this pc or my imac then email check and downloads work fine(using same internet connection). Tried again at 10pm and same with SW13.0. What gives? Thx.
Make sure that the user ID number for "user" is the same in both Slackware and Arch. It's the number not the name that determines if some account is the owner of the directory. If "user" is 1000 in one Linux system and "user" is 1001 in a different Linux system then you can't give a directory ownership to "user" in both systems. You either set the owner to "1000" or "1001". The same sort of thing applies to groups but predefined groups such as "users" are likely to have the same ID number.
The "passwd" file defines user ID numbers and names. The "group" file defines group ID numbers and names.
If "home" is a separate partition make sure that it is mounted with read/write access and the permissions are set correctly (after it is mounted). Changing permissions on the mount point when home isn't mounted has no effect. You have to change permissions for "home" when the filesystem is mounted on "home". In particular "users" must have execute permission for home in order to access directories under "home". To list the directories (or files) in "home" users must have read access.
I only have root and swap partitions for SW13. No separate/shared home partition. Everything was working fine (since install several days ago)today until about 7PM. Earlier I ran # "nvidia xconfig --composite" to get bad window/terminal setting errors to stop when logging out. Just editing /etc/X11/xorg.conf to add the composite subsection didn't work; and,in fact, 'x' failed until I #'d out the subsection.
The last installs were corefonts and vlc slackbuilds. My /etc/group is same as in Arch. I don't use sudo. What could have changed the permissions? Thx for the replies.
Ran # ls -la /home/user which showed root:root for /home/user/Downloads. Changed it to root:users. /home/user/builds is also root:root which is ok since builds are run as root. It doesn't make sense that the ownership wasn't an issue until today when downloading to the Downloads folder. It's a place to start. Thx.
Changing ownership of /home/user/Downloads from root:root to user:users gave me back the normal downloads. Something else for the notebook. Thx a bunch guys
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.