2009-04-30 13:04:27 |
dave_rodgman |
description |
I've experienced very odd behaviour with the login shell:
Initially I had bash installed and no tcsh. Randomly, gnome-terminal locked up. New terminals wouldn't start (xterm or gnome-terminal). I couldn't log in in text-mode because (IIRC) of some error message about tcsh not being present (note: my shell in /etc/passwd is /bin/bash, which is present).
I managed to install tcsh, at which point all my login shells were tcsh, despite my setting in /etc/passwd. typing "bash" launched bash fine.
I then uninstalled tcsh. Now I get a bash login shell, and everything seems OK.
This happened randomly while I was using X, without changing any settings or updating packages.
The only possible clue is that I have a network login, so my /etc/password looks like:
+drodgman::::::/bin/bash
but:
sudo chsh -s /bin/bash drodgman
chsh: drodgman not found in /etc/passwd
maybe some problem with parsing network logins? |
I've experienced very odd behaviour with the login shell:
Initially I had bash installed and no tcsh. Randomly, gnome-terminal locked up. New terminals wouldn't start (xterm or gnome-terminal). I couldn't log in in text-mode because (IIRC) of some error message about tcsh not being present (note: my shell in /etc/passwd is /bin/bash, which is present).
I managed to install tcsh, at which point all my login shells were tcsh, despite my setting in /etc/passwd. typing "bash" launched bash fine.
I then uninstalled tcsh. Now I get a bash login shell, and everything seems OK.
This happened randomly while I was using X, without changing any settings or updating packages.
The only possible clue is that I have a network login, so my /etc/password looks like:
+drodgman::::::/bin/bash
but:
sudo chsh -s /bin/bash drodgman
chsh: drodgman not found in /etc/passwd
maybe some problem with parsing network logins?
----------
Happened again today. I rebooted, and noticed that I was unable to bind to NIS. I was able to log in, though,
and I don't see any other problems (network filesystems mounted OK), so it's not clear why this problem has
affected my shell. |
|