gnome fails to start after chsh or vipw /usr/bin/zsh or /bin/zsh

  • marc
Posted: Thu, 01/10/2008 - 23:05
I noticed something strange and I dont seem to be able to find an answer to correct it. After sudo chsh /usr/bin/zsh or /bin/zsh gnome fails to start after succesfull login. Also changing /bin/bash to /bin/zsh or /usr/bin/zsh by using sudo vipw results in gnome failing to start after succesfull login. Since this is has never been a problem in Debian Sarge and is not a problem in Debian Etch something is different in 64Studio. I have been readin up on the matter but I haven't found the answer yet. I really would be gratefull for ideas or suggestions leading to a solution.

Changing shell?

  • Quentin Harley
  • 05/24/07
  • Fri, 01/11/2008 - 10:15
What is the advantage of changing to zsh, or what is the disadvantage of using bash? 64studio is only a remix of etch, so if it works on etch it should have worked here as well...

Changing shell!

  • marc
  • 01/10/08
  • Fri, 01/11/2008 - 12:57
For me zsh is the superior shell for a number of reasons. Autocompletion being a major one. The way autocompletion works in zsh is awesome. If you work alot with ssh and or scp and have keybased authentication in place: $ scp -r filename whoever@whateverremote:/ho[Tab] actualy browses and autocompletes on the remote machine. Still since changing the shell causes gnome to fail starting up after succeslfull login leads to the conclusion someting is done differently with gnome compared to etch. Still havent figured out what tho. So i am still open for suggestions on how to change the shell without breaking gnome.