You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello there.
I've installed oh-my-bash and selected the powerline theme.
All good, everything worked fine.
When I restarted the system though, it was another matter. After logging in I received this error:
Error found when loading /home/[username]/.profile oh-my-bash: Shell is not interactive. As a result the session will not be configured correctly. You should fix the problem as soon as feasible.
It turns out that I don't know how to fix the problem.
I have found a couple of issues on the web talking about the subject,
but they don't seem to be directly related to oh-my-bash, or oh-my-zsh for that matter.
I initially thought that this problem had been resolved.
Is it possible that I did something wrong in the installation process?
I've created this issue to highlight the problem and the solution which, by the way, was already described in an old issue.
Hope it helps someone else.
The text was updated successfully, but these errors were encountered:
Hello there.
I've installed oh-my-bash and selected the powerline theme.
All good, everything worked fine.
When I restarted the system though, it was another matter. After logging in I received this error:
Error found when loading /home/[username]/.profile oh-my-bash: Shell is not interactive. As a result the session will not be configured correctly. You should fix the problem as soon as feasible.
It turns out that I don't know how to fix the problem.
I have found a couple of issues on the web talking about the subject,
but they don't seem to be directly related to oh-my-bash, or oh-my-zsh for that matter.
And then I ran into this issue: #18 .
Replacing the line
with the following
solved my problem.
I initially thought that this problem had been resolved.
Is it possible that I did something wrong in the installation process?
I've created this issue to highlight the problem and the solution which, by the way, was already described in an old issue.
Hope it helps someone else.
The text was updated successfully, but these errors were encountered: