newbie > root can log in to a gui, users suddenly can't

dracolich · 10-08-2005, 11:44 AM

Where are you copying it to and why? As you said before you can create a new user but the user can't login. It'll help if you can get the exact bash errors and post them. Maybe the users can't find those executables because they're not in the path. Open /etc/profile and see what the PATH variable is set to.

Influx · 10-08-2005, 07:31 PM

Before anything, I had the problem logging in as a user. So I thought it might have been disk space being a problem again, so I formatted again, and made a new partition, moved the homecomp user to the new partition, then added in fstab the new drive

/dev/hda3 /home ext2 defaults 1 2

Still the same problem, so I login to the console, and it gives these errors:

-bash: id: command not found

-bash: fortune: command not found

-bash: id: command not found

when i echo $PATH it gives me
/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/usr/lib/java/bin:/usr/lib/java/jre/bin:/opt/kde/bin:/bin:.

in /etc/profile:
# Set the default system $PATH:
PATH="/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games"

I'm quite perplexed by this problem... Maybe is it that users can't access the drive? I assume because I copied the fstab entry for my primary partition and changed it accordingly that it would allow all users to access it.

Also here's something from ~/.xsession-errors:

Quote:

/etc/profile: line 22: id: command not found
/etc/profile: line 87: id: command not found
kde-config: error while loading shared libraries: libart_lgpl_2.so.2: cannot open shared object file: Permission denied
/opt/kde/bin/startkde: line 76: tr: command not found
/opt/kde/bin/startkde: line 142: xset: command not found
/opt/kde/bin/startkde: line 145: xset: command not found
/opt/kde/bin/startkde: line 148: xset: command not found
/opt/kde/bin/startkde: line 158: xsetroot: command not found
startkde: Starting up...
kreadconfig: error while loading shared libraries: libart_lgpl_2.so.2: cannot open shared object file: Permission denied
kreadconfig: error while loading shared libraries: libart_lgpl_2.so.2: cannot open shared object file: Permission denied
ksplash: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: Permission denied
kdeinit: error while loading shared libraries: libart_lgpl_2.so.2: cannot open shared object file: Permission denied
startkde: Could not start kdeinit. Check your installation.
/opt/kde/bin/startkde: line 221: xmessage: command not found
Warning: connect() failed: : No such file or directory
ksmserver: error while loading shared libraries: libart_lgpl_2.so.2: cannot open shared object file: Permission denied
dcop: error while loading shared libraries: libqt-mt.so.3: cannot open shared object file: Permission denied
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
artsshell: error while loading shared libraries: libesd.so.0: cannot open shared object file: Permission denied
startkde: Running shutdown scripts...
startkde: Done.

Thanks again for the help

Influx · 10-08-2005, 10:46 PM

i chmod'ed /usr (recursivly) so that owner can rwx, group can rx and others can rx... And it got me working again. is this safe practice? I have no idea if I just opened my door to virii and other bad practices.

dracolich · 10-09-2005, 10:09 AM

Being a permissions problem I would call that a "quick and dirty" fix. Since all the programs and files that the users couldn't access were in various subdirectories of /usr this works. But there's many other subdirectories and files that might've been set at something more like 770, 664 or even 660 - things that only needed to be read like readmes, global configs and libraries. With 755 there's probably not a lot of virus threat (not much exists in the linux world anyway

) since only the files' owner has write permission.