-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I get errors after running setup.sh #225
Comments
Hi! Sorry to hear that. I don0t have Kali on hand to test it myself. |
I'm still not sure about the -t option, but I see that it's now complaining about About zhs, I've never really tested it. A friend of mine fixed some bugs a long time ago, so there is still some development to be done. Can you try with bash? Also, if you can, go to the config and disable all or most features of the greeter (like the storage monitors and such), and reenable them one by one to see if there is a specific culprit |
Ah yes i've fixed the problem , well a bit (Honestly this is a learning experience for me so thank you for being patient) i just had to change to the bash shell and then comment out the 60th line in the "bash.bashrc" file. So now the beautiful shell appears for me as "root" but not as the "kali" user. |
No worries, we are getting there! Hmm, I think there was an issue a few weeks ago (it's closed by now) where another user had that same problem: they got it for root but not for their user. Could you reinstall the script but select for your user only? As for zhs, if you manage to identify the problem, feel free to pull request and contribute your fixes :) Also, I just realized. I think you should get the Kali Linux ASCII art logo, not the generic pink-cyan SynthShell logo. If you don't mind, send me a screenshot of what it looks like right now (don't forget to blur your IP) |
Hello I have ran the setup.sh script and followed the prompts to setup synth shell, i also followed the directions and installed fonts-powerline and made sure i was using the "Hack" font and i ended up getting an error when i opened a new terminal.
The text was updated successfully, but these errors were encountered: