You are not logged in.
After updating all of the sudden, I can do ANY command in the terminal. I had to reboot, but pushing the button. Only ls, exit. This ways really weird, my user can't use pacman, sudo, etc. But the root user is fine.
Logged as root, if I move my user, to other name would resolv this problem?
I'm not sure if its because this update, I know is that after updating this package, suddenly can do any command.
I would NOT want to lose any data, so if I login as root and make a backup of my home folder. That would work?
Last edited by lgeek (2012-06-13 21:20:07)
Offline
Your description is vague. Define "can't do any command". What happens exactly when you try to invoke a command as a regular user?
Burninate!
Offline
bash: sudo: command not found
bash: startx: command not found
Only ls and exit works. At my understanding...
Offline
Your user's $PATH is most likely messed up.
Burninate!
Offline
Is there a "easy" way to solve this?
Last edited by lgeek (2012-06-13 15:26:39)
Offline
First check that this is indeed what's going on. Running "echo $PATH" will tell you what's currently in your path.
For more info on where these variables are defined and how to add/fix it; read this wiki article.
Burninate!
Offline
I logged as root, opened terminal. Typed:
[root@hwd-gh0st ~]# su lgeek
[$] ~ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
And when I install a package as root:
[root@hwd-gh0st ~]# pacman -S cheese
to resolve dependencies ...
looking for internal conflicts ...
Targets (2): gnome-video-effects-0.4.0-1-3.4.2-1 cheese
Total Installed Size: 7.18 MiB
Continue installation? [Y / n]
(2/2) to verify the integrity of packages [# # # # # # # # # # # # # # # # # # # # # #] 100%
(2/2) to upload files of packages [# # # # # # # # # # # # # # # # # # # # # #] 100%
(2/2) to check for conflicts on files [# # # # # # # # # # # # # # # # # # # # # #] 100%
(2/2) to check available disk space on [# # # # # # # # # # # # # # # # # # # # # #] 100%
(1/2) to install gnome-video-effects [# # # # # # # # # # # # # # # # # # # # # #] 100%
(2/2) to install cheese [# # # # # # # # # # # # # # # # # # # # # #] 100%
warning: directory permissions differ on usr / bin /
filesystem: 700 package: 755
Last edited by lgeek (2012-06-13 17:15:57)
Offline
Had to reinstall everything again. Thanks for the support.
Offline
Okay. You're kind of fast with reinstalling everything.
# chmod 755 /usr/bin
would have done the trick I think. (BTW thats what pacmans last line told you)
I had the same problem and and least that worked for me.
The strange thing is:
Vidalia, when run as root, seems to change /usr/bin permissions to 700.
Before I could simply run vidalia as normal user.
Now running it as user gives me the following error:
Jun 14 01:10:39.265 [Notice] Tor v0.2.2.36 (git-c1414cf70cbfcbb7). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Jun 14 01:10:39.265 [Notice] Initialized libevent version 2.0.19-stable using method epoll. Good.
Jun 14 01:10:39.265 [Notice] Opening Socks listener on 127.0.0.1:9050
Jun 14 01:10:39.265 [Notice] Opening Control listener on 127.0.0.1:9051
Jun 14 01:10:39.265 [Warning] /usr/bin is not owned by this user (xpumax, 1000) but by root (0). Perhaps you are running Tor as the wrong user?
Jun 14 01:10:39.266 [Warning] Failed to parse/validate config: Couldn't access/create private data directory "/usr/bin"
Jun 14 01:10:39.266 [Error] Reading config failed--see warnings above.
And running it as root leads to /usr/bin having 700-permissions.
Any ideas on that?
Offline
Hi there, I have the same Problem here like lgeek had.
Okay. You're kind of fast with reinstalling everything.
# chmod 755 /usr/bin
would have done the trick I think. (BTW thats what pacmans last line told you)
I had the same problem and and least that worked for me.
Didn't worked for me. KDM doesn't accept my login/pw for my user. I still have to manually login via tty as root.
Any ideas are welcome, thx forward.
Offline
Correction:
# chmod 755 /usr/bin
helped.
Memo to myself: Switching back the login-type into plasma, would do the trick.
Last edited by no1r (2012-06-15 06:39:09)
Offline
Do not running vidalia as root, since that is what screwd my system.
Uninstall vidalia and wget http://schlunix.org/archlinux/community … pkg.tar.xz for 64 bit systems or wget http://schlunix.org/archlinux/community … pkg.tar.xz
After downloading do: pacman -U {name of file}. This worked for me. If you want you could also use the package downgrade from AUR.
I will not upgrading vidalia for a while...
Last edited by lgeek (2012-06-15 23:50:03)
Offline
Just for asking: vidalia 0.2.19-2 is out. It has been corrected?
Offline